Derek Taylor wrote:
On Fri, Feb 29, 2008 09:50 PM Sean <[EMAIL PROTECTED]> wrote:
Check /etc/make.conf for CFLAGS, and if present remove it.
This fixed the problem.
Thank you.
-Derek.
I can confirm a failure in the same spot. What concerns me is in both
my failure, and Derek's, the malloc is failing well below what limit
says should be allowed.
bin/cc/cc_int/../cc_tools
-I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc
-I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config
-I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/include
-I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/libcpp/include
-I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/libdecnumber
-I/usr/obj/usr/src/tmp/legacy/usr/include -c ../cc_tools/insn-attrtab.c
cc1: out of memory allocating 136475392 bytes
*** Error code 1
Stop in /usr/src/gnu/usr.bin/cc/cc_int.
*** Error code 1
cyrix-dlc# limit
cputime unlimited
filesize unlimited
datasize 524288 kbytes
stacksize 65536 kbytes
coredumpsize unlimited
memoryuse unlimited
vmemoryuse unlimited
descriptors 957
memorylocked unlimited
maxproc 478
sbsize unlimited
cc1 was only trying to request 130MB, my datasize is 512MB, why did it fail?
Not to mention the additional question of why is cc1 ballooning up so
badly on that file, when leading up to it it's using on average 12MB per
instance? Prior versions of FreeBSD never took anywhere NEAR this much
RAM to build.
(I also don't like the 'remove all CFLAGS' "fix" suggestion, something
is broken if a buildworld can't complete on a stock kernel with sane
CFLAGS. In my case, I run -Os -pipe, am I now to understand that any
CFLAGS setting is inappropriate?)
Joshua Coombs
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
