Date: Tue, 14 May 2013 17:35:00 -0400 From: "Mikhail T." <mi+thun@aldan.algebra.com> To: Niclas Zeising <zeising@freebsd.org> Cc: x11@FreeBSD.org Subject: Re: solved, kinda (Re: Can't start Xorg after upgrade -- radeon R200) Message-ID: <5192AE04.3010105@aldan.algebra.com> In-Reply-To: <5192A2B3.5020701@freebsd.org> References: <5192935E.9070409@aldan.algebra.com> <5192A14E.3030603@aldan.algebra.com> <5192A2B3.5020701@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
14.05.2013 16:46, Niclas Zeising написав(ла):
> xorg, and especially the old xorg-server used by default in FreeBSD
> ports is riddled with weird code and undefined behavior. A change of
> compiler will trigger different optimizations which might break
> assumptions about things. I've seen it before, especially when
> switching between gcc and clang. You might want to test using clang
> instead, or rebuild all xorg ports with WITH_NEW_XORG= to get a more
> recent xorg version. Otherwise, I suggest you keep running with your
> gcc based xorg-server, unless you have the time and ability to debug the
> issue further.
Oh... What else will the WITH_NEW_XORG enable/disable and how could I
have known about the option, if I did not ask here? I do wish I knew
earlier...
Thanks!
-mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5192AE04.3010105>