Re: [gentoo-user] emerge troubles

2006-02-15 Thread Zac Slade
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

[gentoo-user] emerge troubles

2006-02-14 Thread Jorge Almeida
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

Re: [gentoo-user] emerge troubles

2006-02-14 Thread Benno Schulenberg
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

2006-02-14 Thread Jorge Almeida
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,

Re: [gentoo-user] emerge troubles

2006-02-14 Thread Benno Schulenberg
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

Re: [gentoo-user] emerge troubles

2006-02-14 Thread Zac Slade
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,

Re: [gentoo-user] emerge troubles

2006-02-14 Thread Jorge Almeida
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

Re: [gentoo-user] emerge troubles

2006-02-14 Thread Zac Slade
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.

Re: [gentoo-user] emerge troubles

2006-02-14 Thread Richard Fish
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

Re: [gentoo-user] emerge troubles

2006-02-14 Thread Jorge Almeida
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%

Re: [gentoo-user] emerge troubles

2006-02-14 Thread Jorge Almeida
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

Re: [gentoo-user] emerge troubles

2006-02-14 Thread Richard Fish
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

Re: [gentoo-user] emerge troubles

2006-02-14 Thread Richard Fish
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

2006-02-14 Thread Jorge Almeida
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

2006-02-14 Thread Jorge Almeida
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

Re: [gentoo-user] emerge troubles

2006-02-14 Thread Richard Fish
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

Re: [gentoo-user] emerge troubles

2006-02-14 Thread Jorge Almeida
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