Xorg port problem?

Kris Kennaway kris at obsecurity.org
Tue May 29 18:44:53 UTC 2007

On Tue, May 29, 2007 at 12:07:44AM -0700, Doug Barton wrote:
> Alex Dupre wrote:
> > Doug Barton wrote:
> >>> (Over 2GBs of RAM + Swap being used). It does this consistently when it
> >>> tries to compile xf86PciScan.c (hope thats the right file).
> >> May not be the answer you want to hear, but I built all the xorg stuff
> >> multiple times on -current systems both pre and post the gcc + symver
> >> + version bump eras, and didn't have the problems you're seeing.
> > 
> > It's the well-known problem of new gcc 4.2 optimizations (bug). Simply
> > compile with -O0 instead of -O2.
> Not disputing your answer, but I'm curious. Why would it cause
> problems on some systems but not others? I haven't done anything with
> my cflags ...

It wants to use ${BIGNUM} amount of memory to optimize a huge C file,
so that might be fatal (or just terminally irritating) on smaller

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20070529/778ec22d/attachment.pgp

More information about the freebsd-current mailing list