Re: [gentoo-user] emerge troubles
On Tuesday 14 February 2006 21:14, Jorge Almeida wrote: Well, so that was it! I just finished compiling gcc. I wonder why those limits were set for user root?! My home computer didn't have such restriction, and I recently made a new install on the computer that had all this problem, so I'm sure I didn't do it myself and forgot it... Check /etc/limits to see what the defaults are. I'd also look at any shell scripts that are being sourced during login (/etc/profile ~/.bashrc, etc.). It's a relief to know it's not hw problem! Memory allocation is one of those things that usually isn't. Normally you'd see physical memory errors as programs randomly crashing (like the kernel, with no PANIC). You also might notice when you start the system up that it is reporting less memory than you have installed. Thank you, and thanks also to Benno and Zac. Very appreciated. -- Zac Slade -- gentoo-user@gentoo.org mailing list
[gentoo-user] emerge troubles
I'm unable to emerge gcc: 17012 all allocated states, 101385 all allocated arcs 20258 all allocated alternative states 4765 all transition comb vector els, 13107 all trans table els 4765 all state alts comb vector els, 13107 all state alts table els 13107 all min delay table els 0 locked states num transformation: 0.016001, building DFA: 7.968497 DFA minimization: 0.468029, making insn equivalence: 0.00 all automaton generation: 8.536533, output: 0.144009 /bin/sh /var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/gcc/move-if-change tmp-attrtab.c insn-attrtab.c echo timestamp s-attrtab stage1/xgcc -Bstage1/ -B/usr/i686-pc-linux-gnu/bin/-O2 -march=pentium4 -pipe -fprofile-generate -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wold-style-definition -DHAVE_CONFIG_H-I. -I. -I/var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/gcc -I/var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/gcc/. -I/var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/gcc/../include -c insn-attrtab.c \ -o insn-attrtab.o cc1: out of memory allocating 8579592 bytes after a total of 7716864 bytes make[2]: *** [insn-attrtab.o] Error 1 make[2]: Leaving directory `/var/tmp/portage/gcc-3.4.4-r1/work/build/gcc' make[1]: *** [stageprofile_build] Error 2 make[1]: Leaving directory `/var/tmp/portage/gcc-3.4.4-r1/work/build/gcc' make: *** [profiledbootstrap] Error 2 !!! ERROR: sys-devel/gcc-3.4.4-r1 failed. !!! Function gcc_do_make, Line 1339, Exitcode 2 !!! emake failed with profiledbootstrap !!! If you need support, post the topmost build error, NOT this status message. The problem appeared when emerging -DNu world. It failed with kpdf. Then I tried to emerge binutils glibc gcc and it failed at gcc. Assuming a hardware problem, I tried a script I read about on a recent thread: http://people.redhat.com/dledford/memtest.html The script executed without a whisper. The box has 1GB RAM, P4 3GHz, no overclocking. The system is up to date. revdep-rebuild seems happy, except for wanting to re-emerge openoffice-bin, always. What else can I do? Is there some other test for hw failure? I can't try memtest now (I'm away from the box) but it didn't report errors last time I checked, not too long ago. -- Jorge Almeida -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge troubles
Jorge Almeida wrote: cc1: out of memory allocating 8579592 bytes after a total of 7716864 bytes Swap not enabled? Also, emerge --info output would be helpful. Benno -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge troubles
On Tue, 14 Feb 2006, Benno Schulenberg wrote: Jorge Almeida wrote: cc1: out of memory allocating 8579592 bytes after a total of 7716864 bytes Swap not enabled? Also, emerge --info output would be helpful. Swap was enabled. $ emerge info Portage 2.0.54 (default-linux/x86/2005.1, gcc-3.4.4, glibc-2.3.5-r2, 2.6.14-gentoo-r2 i686) = System uname: 2.6.14-gentoo-r2 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz Gentoo Base System version 1.6.14 dev-lang/python: 2.3.5, 2.4.2 sys-apps/sandbox:1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS=x86 AUTOCLEAN=yes CBUILD=i686-pc-linux-gnu CFLAGS=-O2 -march=pentium4 -pipe -fomit-frame-pointer CHOST=i686-pc-linux-gnu CONFIG_PROTECT=/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control CONFIG_PROTECT_MASK=/etc/gconf /etc/terminfo /etc/env.d CXXFLAGS=-O2 -march=pentium4 -pipe -fomit-frame-pointer DISTDIR=/usr/portage/distfiles FEATURES=autoconfig distlocks sandbox sfperms strict GENTOO_MIRRORS=ftp://ftp.rnl.ist.utl.pt/pub/gentoo http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/distributions/gentoo; LANG=en_US MAKEOPTS=-j1 PKGDIR=/usr/portage/packages PORTAGE_TMPDIR=/var/tmp PORTDIR=/usr/portage SYNC=rsync://rsync.europe.gentoo.org/gentoo-portage USE=x86 X aalib acpi bash-completion bitmap-fonts bzip2 cdb cdparanoia cdr crypt cups curl gif gtk gtk2 imap imlib java jpeg jpeg2k kde maildir motif ncurses nls nptl nsplugin opengl pam pdflib perl pic png posix python qt readline recode ssl tiff truetype truetype-fonts type1-fonts xml zlib userland_GNU kernel_linux elibc_glibc Unset: ASFLAGS, CTARGET, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY -- Jorge Almeida -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge troubles
Jorge Almeida wrote: Swap was enabled. $ emerge info [...] Looks fine. Have you tried emerging gcc again, a few times, and does it fail every time in the same spot with the same error? What error does kpdf give? Does it too fail every time at the same place? Have you tried closing memory-hungry apps like Firefox? Have you maybe changed the memory timings in the BIOS lately? Perhaps it is time to dust off the computer on the inside and reseat the mem chips? Benno -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge troubles
On Tuesday 14 February 2006 17:43, Benno Schulenberg wrote: Jorge Almeida wrote: parser error : out of memory error /bin/sh: line 1: 3831 Segmentation fault Doesn't look good. :( No it doesn't, but there has to be a reason why he's out of memory... What is the output of free, before emerge? How about after it fails? Can you give the output of the following commands: cat /proc/sys/vm/swappiness cat /proc/sys/vm/overcommit_memory cat /proc/sys/vm/overcommit_ratio Also try using vmstat 5 in one window and attempting the emerge in another window. What process is using the most memory right now? (Check top sorted by memory). Is this box always on? Have you tried rebooting? Maybe loads of memory have leaked away. WHOA! Stop right there. Perhaps we should help him diagnose his problem before using a shotgun. If the RAM has gone bad, to replace it you will have to touch it anyway. So, no harm in trying to wriggle it a bit first. Touch and hold the case before touching the RAM strips. There is nothing in the information he has presented thus far to show that there are memory errors of any type. He very well may be just running out of memory. It happens. Send back the extra information and let's get to the bottom of the issue. -- Zac Slade -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge troubles
On Tue, 14 Feb 2006, Zac Slade wrote: On Tuesday 14 February 2006 17:43, Benno Schulenberg wrote: Jorge Almeida wrote: parser error : out of memory error /bin/sh: line 1: 3831 Segmentation fault Doesn't look good. :( No it doesn't, but there has to be a reason why he's out of memory... What is the output of free, before emerge? How about after it fails? Can you give the output of the following commands: cat /proc/sys/vm/swappiness cat /proc/sys/vm/overcommit_memory cat /proc/sys/vm/overcommit_ratio $ cat /proc/sys/vm/swappiness 60 $ cat /proc/sys/vm/overcommit_memory 0 $ cat /proc/sys/vm/overcommit_ratio 50 $ free total used free sharedbuffers cached Mem: 1035204 968140 67064 0 270248 538412 -/+ buffers/cache: 159480 875724 Swap: 996020300 995720 Of course, this is the output of free _after_ the previous failed emerge attempts. It seems RAM really was caught and not released... I can try rebooting, but there is the possibility that the box won't boot, and I'm away... Is there some way to find what's eating RAM? Also try using vmstat 5 in one window and attempting the emerge in another window. What process is using the most memory right now? (Check top sorted by memory). $ top top - 01:21:23 up 22 days, 17:29, 2 users, load average: 0.00, 0.00, 0.00 Tasks: 120 total, 2 running, 118 sleeping, 0 stopped, 0 zombie Cpu(s): 0.0% us, 0.0% sy, 0.0% ni, 99.7% id, 0.0% wa, 0.3% hi, 0.0% si Mem: 1035204k total, 968760k used,66444k free, 270684k buffers Swap: 996020k total, 300k used, 995720k free, 538452k cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 8291 root 15 0 159m 29m 3056 S 0.0 3.0 5:05.74 X 24756 jorge 15 0 30592 25m 2576 S 0.0 2.5 0:06.52 pine 28731 jorge 16 0 20016 14m 14m S 0.0 1.4 0:19.34 imap 26923 root 15 0 21236 12m 9704 S 0.0 1.2 0:00.39 kdm_greet 24757 jorge 16 0 8436 6292 5984 S 0.0 0.6 0:01.85 imap 21961 jorge 16 0 8044 3992 2684 S 0.0 0.4 0:00.15 vim 8259 root 16 0 5756 2852 1356 S 0.0 0.3 0:50.69 cupsd 24734 root 16 0 5944 1764 1440 S 0.0 0.2 0:00.01 sshd 24767 root 16 0 5948 1764 1440 S 0.0 0.2 0:00.01 sshd 3588 root 15 0 2644 1560 1172 S 0.0 0.2 0:00.11 bash 24746 jorge 15 0 2924 1472 1164 S 0.0 0.1 0:00.02 bash 6396 privoxy 15 0 36028 1464 784 S 0.0 0.1 0:07.90 privoxy 24785 jorge 15 0 2796 1456 1156 S 0.0 0.1 0:00.01 bash 24799 root 16 0 2664 1456 1156 S 0.0 0.1 0:00.00 bash Jorge Almeida -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge troubles
On Tuesday 14 February 2006 19:25, Jorge Almeida wrote: $ cat /proc/sys/vm/swappiness 60 $ cat /proc/sys/vm/overcommit_memory 0 $ cat /proc/sys/vm/overcommit_ratio 50 That was a long shot, but just wanted to make sure the system was allowing overcommit. $ free total used free sharedbuffers cached Mem: 1035204 968140 67064 0 270248 538412 -/+ buffers/cache: 159480 875724 Swap: 996020300 995720 This seems within spec. You have plenty of memory free. Of course, this is the output of free _after_ the previous failed emerge attempts. It seems RAM really was caught and not released... I can try rebooting, but there is the possibility that the box won't boot, and I'm away... Is there some way to find what's eating RAM? If you don't have physical access to the system, don't reboot it. It's not just a good rule of thumb, it's one you should live by (whenever possible). What process is using the most memory right now? (Check top sorted by memory). $ top top - 01:21:23 up 22 days, 17:29, 2 users, load average: 0.00, 0.00, 0.00 Tasks: 120 total, 2 running, 118 sleeping, 0 stopped, 0 zombie Cpu(s): 0.0% us, 0.0% sy, 0.0% ni, 99.7% id, 0.0% wa, 0.3% hi, 0.0% si Mem: 1035204k total, 968760k used,66444k free, 270684k buffers Swap: 996020k total, 300k used, 995720k free, 538452k cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 8291 root 15 0 159m 29m 3056 S 0.0 3.0 5:05.74 X 24756 jorge 15 0 30592 25m 2576 S 0.0 2.5 0:06.52 pine 28731 jorge 16 0 20016 14m 14m S 0.0 1.4 0:19.34 imap 26923 root 15 0 21236 12m 9704 S 0.0 1.2 0:00.39 kdm_greet 24757 jorge 16 0 8436 6292 5984 S 0.0 0.6 0:01.85 imap 21961 jorge 16 0 8044 3992 2684 S 0.0 0.4 0:00.15 vim 8259 root 16 0 5756 2852 1356 S 0.0 0.3 0:50.69 cupsd 24734 root 16 0 5944 1764 1440 S 0.0 0.2 0:00.01 sshd 24767 root 16 0 5948 1764 1440 S 0.0 0.2 0:00.01 sshd 3588 root 15 0 2644 1560 1172 S 0.0 0.2 0:00.11 bash 24746 jorge 15 0 2924 1472 1164 S 0.0 0.1 0:00.02 bash 6396 privoxy 15 0 36028 1464 784 S 0.0 0.1 0:07.90 privoxy 24785 jorge 15 0 2796 1456 1156 S 0.0 0.1 0:00.01 bash 24799 root 16 0 2664 1456 1156 S 0.0 0.1 0:00.00 bash Well nothing really stands out here There are multiple imap processes open, but really you have plenty of memory. Just an absolute blind stab in the dark. what does df -h give you? Anything interesting in dmesg? And just to make sure we have PLENTY of information here, can we get the end of emerge.log (some context prior to the error message). -- Zac Slade -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge troubles
On 2/14/06, Jorge Almeida [EMAIL PROTECTED] wrote: $ free total used free sharedbuffers cached Mem: 1035204 968140 67064 0 270248 538412 -/+ buffers/cache: 159480 875724 Swap: 996020300 995720 Of course, this is the output of free _after_ the previous failed emerge attempts. It seems RAM really was caught and not released... I can try rebooting, No, it wasn't. The important line is the +/- buffers/cache, which shows you have 850M free. The rest of your used memory is buffers or cached programs, all of which can be swapped back out. -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge troubles
On Tue, 14 Feb 2006, Zac Slade wrote:
Just an absolute blind stab in the dark. what does df -h give you?
$ df -h
FilesystemSize Used Avail Use% Mounted on
/dev/hda3 2.0G 281M 1.7G 15% /
udev 506M 300K 506M 1% /dev
/dev/hda5 2.0G 338M 1.6G 18% /var
/dev/hda6 9.9G 3.6G 5.8G 39% /usr
/dev/hdb2 7.6G 3.0G 4.2G 42% /home
/dev/hdb6 23G 6.3G 16G 30% /home/jorge/bulk
/dev/hdb1 7.8G 1.6G 5.9G 21% /home/jorge/bulk/backup
/dev/hda7 2.0G 392M 1.5G 21% /local
/dev/hda8 10G 1.4G 8.6G 15% /local/mail
/dev/hdb3 7.6G 5.8G 1.4G 81% /local/port
/local/port/portage 7.6G 5.8G 1.4G 81% /usr/portage
/local/port/var_tmp 7.6G 5.8G 1.4G 81% /var/tmp/portage
/local/run/qmail/varqmail
2.0G 392M 1.5G 21% /var/qmail
/local/usr2.0G 392M 1.5G 21% /usr/local
shm 506M 0 506M 0% /dev/shm
Anything interesting in dmesg? And just to make sure we have PLENTY of
the bottom of dmesg seems strange:
EXT3-fs: mounted filesystem with ordered data mode.
hw_random: RNG not detected
r8169: eth0: link up
ip_tables: (C) 2000-2002 Netfilter core team
ip_conntrack version 2.3 (8191 buckets, 65528 max) - 216 bytes per
conntrack
ipt_recent v0.3.1: Stephen Frost [EMAIL PROTECTED].
http://snowman.net/projects/ipt_recent/
ipt_owner: pid, sid and command matching not supported anymore
spurious 8259A interrupt: IRQ7.
ipt_owner: pid, sid and command matching not supported anymore
ipt_owner: pid, sid and command matching not supported anymore
ipt_owner: pid, sid and command matching not supported anymore
ipt_owner: pid, sid and command matching not supported anymore
(Many repeated lines like the latter.)
information here, can we get the end of emerge.log (some context prior to the
error message).
I suppose you mean the output of emerge? The contents of
/var/log/emerge.log are laconic. Here it goes:
In file included from
/var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/gcc/libgcov.c:37:
/var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/gcc/tsystem.h:40:1:
warning: this is the location of the previous definition
/var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/gcc/doc//cppopts.texi:137:
warning: @strong{Note...} produces a spurious cross-reference in Info; reword
to avoid that.
/var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/gcc/doc//cppopts.texi:345:
warning: @strong{Note...} produces a spurious cross-reference in Info; reword
to avoid that.
mv: cannot stat `libgcc/*.os': No such file or directory
mv: cannot stat `s-crt0': No such file or directory
mv: cannot stat `crtbegin.o': No such file or directory
mv: cannot stat `crtbeginS.o': No such file or directory
mv: cannot stat `crtbeginT.o': No such file or directory
mv: cannot stat `crtend.o': No such file or directory
mv: cannot stat `crtendS.o': No such file or directory
mv: cannot stat `gcc-cross': No such file or directory
mv: cannot stat `protoize': No such file or directory
mv: cannot stat `unprotoize': No such file or directory
mv: cannot stat `specs': No such file or directory
mv: cannot stat `collect2': No such file or directory
mv: cannot stat `gcov': No such file or directory
mv: cannot stat `gcov-dump': No such file or directory
mv: cannot stat `*.[0-9][0-9].*': No such file or directory
mv: cannot stat `*.[si]': No such file or directory
mv: cannot stat `g++-cross': No such file or directory
mv: cannot stat `cc1plus': No such file or directory
make[2]: [stage1-start] Error 1 (ignored)
cp: cannot stat `libunwind.a': No such file or directory
cp: cannot stat `libunwind*.so': No such file or directory
make[2]: [stage1-start] Error 1 (ignored)
mv: cannot stat `cp/*.o': No such file or directory
make[2]: [c++.stage1] Error 1 (ignored)
gengtype-lex.c: In function `yy_get_next_buffer':
gengtype-lex.c:2412: warning: old-style parameter declaration
gengtype-lex.c: In function `yy_get_previous_state':
gengtype-lex.c:2544: warning: old-style parameter declaration
gengtype-lex.c: In function `input':
gengtype-lex.c:2657: warning: old-style parameter declaration
/usr/share/bison/bison.simple: In function `yyparse':
/usr/share/bison/bison.simple:379: warning: old-style parameter
declaration
warning: structure `reg_info_def' used but not defined
warning: structure `basic_block_def' used but not defined
warning:
Re: [gentoo-user] emerge troubles
On Tue, 14 Feb 2006, Richard Fish wrote: Also, to test whether your system can make large memory allocations, you can do: python -c s='x'*(4*(1024*1024)) python -c s='x'*(8*(1024*1024)) python -c s='x'*(16*(1024*1024)) python -c s='x'*(32*(1024*1024)) python -c s='x'*(64*(1024*1024)) python -c s='x'*(128*(1024*1024)) python -c s='x'*(256*(1024*1024)) The above commands will try to allocate memory from 4M to 256M. -Richard [EMAIL PROTECTED] ~ $ python -c s='x'*(4*(1024*1024)) ~ [EMAIL PROTECTED] ~ $ python -c s='x'*(8*(1024*1024)) ~ [EMAIL PROTECTED] ~ $ python -c s='x'*(16*(1024*1024)) ~ [EMAIL PROTECTED] ~ $ python -c s='x'*(32*(1024*1024)) ~ [EMAIL PROTECTED] ~ $ python -c s='x'*(64*(1024*1024)) Traceback (most recent call last): File string, line 1, in ? MemoryError ~ [EMAIL PROTECTED] ~ $ python -c s='x'*(128*(1024*1024)) Traceback (most recent call last): File string, line 1, in ? MemoryError ~ [EMAIL PROTECTED] ~ $ python -c s='x'*(256*(1024*1024)) Traceback (most recent call last): File string, line 1, in ? MemoryError SIGH Thanks, Jorge -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge troubles
On 2/14/06, Jorge Almeida [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] ~ $ python -c s='x'*(4*(1024*1024)) ~ [EMAIL PROTECTED] ~ $ python -c s='x'*(8*(1024*1024)) ~ [EMAIL PROTECTED] ~ $ python -c s='x'*(16*(1024*1024)) ~ [EMAIL PROTECTED] ~ $ python -c s='x'*(32*(1024*1024)) ~ [EMAIL PROTECTED] ~ $ python -c s='x'*(64*(1024*1024)) Traceback (most recent call last): File string, line 1, in ? MemoryError Any chance this is a resource limit issue? ulimit -l -m -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge troubles
On 2/14/06, Richard Fish [EMAIL PROTECTED] wrote: ulimit -l -m Or better: ulimit -a -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge troubles
On Tue, 14 Feb 2006, Richard Fish wrote: Any chance this is a resource limit issue? ulimit -l -m Nope... $ ulimit -l -m max locked memory (kbytes, -l) 32 max memory size (kbytes, -m) unlimited Jorge -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge troubles
On Tue, 14 Feb 2006, Richard Fish wrote: Or better: ulimit -a $ ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) 58593 file size (blocks, -f) unlimited pending signals (-i) 8191 max locked memory (kbytes, -l) 32 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 stack size (kbytes, -s) 58593 cpu time (seconds, -t) unlimited max user processes (-u) 8191 virtual memory (kbytes, -v) 58593 file locks (-x) unlimited Jorge -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge troubles
On 2/14/06, Jorge Almeida [EMAIL PROTECTED] wrote: On Tue, 14 Feb 2006, Richard Fish wrote: data seg size (kbytes, -d) 58593 virtual memory (kbytes, -v) 58593 These are preventing any process spawned by this user from allocating more than 58593 bytes of memory (which is why 32M works, and 64M fails) Try: ulimit -d unlimited ulimit -v unlimited -Richard -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] emerge troubles
On Tue, 14 Feb 2006, Richard Fish wrote: On 2/14/06, Jorge Almeida [EMAIL PROTECTED] wrote: On Tue, 14 Feb 2006, Richard Fish wrote: data seg size (kbytes, -d) 58593 virtual memory (kbytes, -v) 58593 These are preventing any process spawned by this user from allocating more than 58593 bytes of memory (which is why 32M works, and 64M fails) Try: ulimit -d unlimited ulimit -v unlimited -Richard Well, so that was it! I just finished compiling gcc. I wonder why those limits were set for user root?! My home computer didn't have such restriction, and I recently made a new install on the computer that had all this problem, so I'm sure I didn't do it myself and forgot it... It's a relief to know it's not hw problem! Thank you, and thanks also to Benno and Zac. Jorge -- gentoo-user@gentoo.org mailing list
