Date: Wed, 12 Sep 2007 05:12:43 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: TooMany Secrets <toomany@toomany.net> Cc: freebsd-current@freebsd.org Subject: Re: Problems updating from 6.2-STABLE to -CURRENT Message-ID: <20070911191243.GJ3585@turion.vk2pj.dyndns.org> In-Reply-To: <e8b5dfd50709110937s6dac3178l8d6d1d450d90e366@mail.gmail.com> References: <e8b5dfd50709110937s6dac3178l8d6d1d450d90e366@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On 2007-Sep-11 18:37:21 +0200, TooMany Secrets <toomany@toomany.net> wrote: >/usr/local/libexec/ccache/world-cc -Os -fno-strict-aliasing -pipe >-DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr/obj/usr/src/tmp/usr\" ... >../cc_tools/insn-attrtab.c > >cc1: out of memory allocating 136475392 bytes ... >Well, I'm using "ccache", and I don't know if this is convenient to >this type of upgrade or not. As a general recommendation, if a buildworld fails when using a non- standard configuraton (-j N, -Ox or something like ccache), you should confirm that the failure still exists with the standard configuration (as I note you are doing). In this case I suspect you are running foul of gcc 4.2.1's larger memory footprint rather than ccache. What is the data segment size limit on your system (reported by ulimit)? Are you able to increase it (probably by several hundred MB)? -- Peter Jeremy [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFG5uir/opHv/APuIcRAip6AKCtmbLXDUNU8MYC/ejBMUuK7bldDwCgicDF G3//JbDnWLJMWNTl1pACvMs= =1sVv -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070911191243.GJ3585>