Re: Problems updating from 6.2-STABLE to -CURRENT

From: Peter Jeremy <peterjeremy_at_optushome.com.au>
Date: Wed, 12 Sep 2007 05:12:43 +1000
On 2007-Sep-11 18:37:21 +0200, TooMany Secrets <toomany_at_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

Received on Tue Sep 11 2007 - 17:12:46 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:17 UTC