From: Aubrey Jaffer <agj@alum.mit.edu>
To: Andy Wingo <wingo@pobox.com>
Cc: bug-guile@gnu.org, ludo@gnu.org
Subject: Re: slib with guile 1.9.7
Date: Sun, 14 Feb 2010 21:00:38 -0500 (EST) [thread overview]
Message-ID: <20100215020038.7A83151D89E@voluntocracy.org> (raw)
In-Reply-To: <m3r5ooaygc.fsf@pobox.com> (message from Andy Wingo on Sun, 14 Feb 2010 11:44:35 +0100)
| From: Andy Wingo <wingo@pobox.com>
| Date: Sun, 14 Feb 2010 11:44:35 +0100
|
| On Sat 13 Feb 2010 20:38, Aubrey Jaffer <agj@alum.mit.edu> writes:
| ...
| > Now its stuck (over 17.min) on:
| >
| > GUILE_AUTO_COMPILE=0 \
| > ../meta/uninstalled-env \
| > guile-tools compile -Wunbound-variable -Warity-mismatch -o "ice-9/boot-9.go" "ice-9/boot-9.scm"
| >
| > Then my computer shut down because the CPU overheated!
|
| !!!
|
| Often compiling these first couple files takes some time, but not
| usually that long. (For example, on this laptop, compiling
| psyntax-pp takes about 4 minutes, then successively less for
| subsequent files, eventually ending up at a fraction of a second
| per file.)
|
| Out of curiousity, what OS and architecture are you running?
Fedora 11
bash-4.0$ uname -a
Linux localhost.localdomain 2.6.30.10-105.2.23.fc11.i586 #1 SMP Thu Feb 11 06:51:26 UTC 2010 i686 i686 i386 GNU/Linux
bash-4.0$ free
total used free shared buffers cached
Mem: 2062356 1353572 708784 0 217420 647308
-/+ buffers/cache: 488844 1573512
Swap: 1048568 740 1047828
bash-4.0$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Pentium(R) 4 CPU 3.00GHz
stepping : 9
cpu MHz : 2992.429
cache size : 512 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 1
apicid : 0
initial apicid : 0
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe pebs bts cid xtpr
bogomips : 5984.85
clflush size : 64
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Pentium(R) 4 CPU 3.00GHz
stepping : 9
cpu MHz : 2992.429
cache size : 512 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 1
apicid : 1
initial apicid : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe pebs bts cid xtpr
bogomips : 6000.28
clflush size : 64
power management:
next prev parent reply other threads:[~2010-02-15 2:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100128165908.GD2540@laura.suse.cz>
[not found] ` <20100128183620.4689351D89E@voluntocracy.org>
[not found] ` <87636lsysm.fsf@gnu.org>
[not found] ` <20100129015934.1E9DE51D89E@voluntocracy.org>
[not found] ` <20100201163750.GB1290@laura.suse.cz>
[not found] ` <20100202183126.1544C51D86D@voluntocracy.org>
2010-02-02 22:17 ` slib with guile 1.9.7 Ludovic Courtès
2010-02-03 16:30 ` Aubrey Jaffer
2010-02-11 21:58 ` Aubrey Jaffer
2010-02-12 9:14 ` Ludovic Courtès
2010-02-13 19:38 ` Aubrey Jaffer
2010-02-14 10:44 ` Andy Wingo
2010-02-15 2:00 ` Aubrey Jaffer [this message]
2010-02-11 22:01 ` Aubrey Jaffer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100215020038.7A83151D89E@voluntocracy.org \
--to=agj@alum.mit.edu \
--cc=bug-guile@gnu.org \
--cc=ludo@gnu.org \
--cc=wingo@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).