Re: Xorg port problem?
- From: Doug Barton <dougb@xxxxxxxxxxx>
- Date: Tue, 29 May 2007 00:07:44 -0700
Alex Dupre wrote:
Doug Barton wrote:
(Over 2GBs of RAM + Swap being used). It does this consistently when itMay not be the answer you want to hear, but I built all the xorg stuff
tries to compile xf86PciScan.c (hope thats the right file).
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 ...
Doug
--
This .signature sanitized for your protection
_______________________________________________
freebsd-hackers@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: Xorg port problem?
- From: Kris Kennaway
- Re: Xorg port problem?
- From: Alex Dupre
- Re: Xorg port problem?
- From: Eric Masson
- Re: Xorg port problem?
- References:
- Xorg port problem?
- From: Ali Mashtizadeh
- Re: Xorg port problem?
- From: Doug Barton
- Re: Xorg port problem?
- From: Alex Dupre
- Xorg port problem?
- Prev by Date: Re: Xorg port problem?
- Next by Date: Re: Xorg port problem?
- Previous by thread: Re: Xorg port problem?
- Next by thread: Re: Xorg port problem?
- Index(es):
Relevant Pages
|
|