[AMD64] X.org build eats all the memory when compiled with GCC 4.2

Michiel Boland michiel at boland.org
Mon Jun 18 12:32:03 UTC 2007


On Sat, 16 Jun 2007, Garrett Cooper wrote:

> Claus Guttesen wrote:
>>> I recompiled X.org yesterday and hit the following problem
>>> (1 week old -current, yesterdays packages, AMD64) -- when compiling
>>> files in
>>> /usr/ports/x11-servers/xorg-server/work/xorg-server-1.2.0/hw/xfree86/scanpci 
>>> directory, there are huge .h files - about 4mb. when compiler uses -O2
>>> or -O option it eats all available memory and then gets killed by the
>>> system.
>>> Without -O/O2 option compile works just as expected.
>>> 
>>> Now -- should I file a PR or it's known bug?
>> 
>> No, but you  should read the archives. Requires more than 1 GB of swap.
>> 
> It's a known bug that isn't going to be fixed until gcc 4.2.1.
> -Garrett
>

Well, until then, is it not possible to at least put the following 
patch in ports/x11-servers/xorg-server/files:

--- hw/xfree86/scanpci/Makefile.in.orig	2007-06-18 13:57:05.000000000 +0200
+++ hw/xfree86/scanpci/Makefile.in	2007-06-18 13:57:58.000000000 +0200
@@ -132,7 +132,7 @@
  CCDEPMODE = @CCDEPMODE@
  CFB_FALSE = @CFB_FALSE@
  CFB_TRUE = @CFB_TRUE@
-CFLAGS = @CFLAGS@
+CFLAGS = @CFLAGS@ -O0
  COMPILEDDEFAULTFONTPATH = @COMPILEDDEFAULTFONTPATH@
  COMPOSITE_FALSE = @COMPOSITE_FALSE@
  COMPOSITE_TRUE = @COMPOSITE_TRUE@

That would make a lot of people very happy. In particular those running 
amd64.


More information about the freebsd-current mailing list