Frank Peters posted on Tue, 04 Jun 2013 22:17:15 -0400 as excerpted: > On my system, emerge wants to update xorg-server to 1.14.1.901 but the > compile phase always fails. > > There is no obvious error recorded in the log file, but based on a > gentoo bug report (Bug 472058) it seems that a -Werror compile flag > could be causing the problem. > > My emerge log only reports this: > > cc1: some warnings being treated as errors > make[5]: *** [xf86Events.lo] Error 1 > make[5]: *** Waiting for unfinished jobs.... > ... > [snip a lot of stuff until the end of log]
The actual error will be printed above that. Depending on how many make-jobs you are running and some other things, it could actually be QUITE far above that. Doing a search for "error:" (without the quotes, preferably case insensitive) in the log generally finds it pretty fast, and I tested on the log attached to the mentioned bug and found the error there pretty fast, so it should work for this package. > > > The bug report (#472058) mentions a failure occurring at a different point, > but -Werror seems to be the cause. > > I waited a few days to see if there were any other reports about a similar > compile failure but so far there are none. I can only assume that xorg-server > is compiling without problem on other systems. Why is it failing on mine? > > Has anyone on the list experienced this failure? > > I would like to remove the -Werror compile flag but without patching > the source I don't see how this could be done. The guy in that bug is using pretty radical CFLAGS (-Ofast and those -floop flags), and apparently using gcc 4.8 as well, which is still masked. And one of the problems with upstreams using -Werror by default is that it's hard telling just /what/ a new gcc is going to warn about next, so doing -Werror in a release (as opposed to an internal testing version, which is what the flag is designed for) is pretty much /begging/ for trouble with some gcc version or other, often the newer ones. But of course xorg-server-1.14.1.901 isn't a full release, but rather a pre-release version, so upstream /does/ get some leeway with it, tho even then it's really asking for trouble unless you /want/ people testing with all sorts of gcc versions and reporting the -Werror stoppages that come up, as opposed to wanting people's run-time testing. And I don't think that's what they had in mind so I don't know why they're doing -Werror, but anyway... I believe I read, I think in flameyes' blog (where this specific error was being used as a reason NOT to do -Werror, IIRC), that that specific error is a known issue with -Werror, due to a new warning in gcc 4.8. Which means... if you're trying to build with gcc 4.8, try again with 4.7.x. If you're not using gcc 4.8, then your error is likely a different bug. And also... USE=kdrive? In the bug, the log says USE=kdrive, even tho the reported package settings said USE=-kdrive. So I'm not sure what's up there. But certainly, unless you have a reason to run USE=kdrive, please ensure that you're running USE=-kdrive. Meanwhile, I don't have 4.8 installed here, but I can confirm that xorg-server-1.14.1.901 built here just fine, with gcc 4.7.3. I should mention, however, that I'm running live-git -9999 version ebuilds from the x11 overlay for mesa and my two drivers (xf86-video-ati and xf86-input-evdev), among other things. It's possible that there's some issue with the non-git versions. But xorg-server-1.14.1.901 is definitely built/installed/running fine here! [ebuild R ] x11-base/xorg-server-1.14.1.901:0/1.14.1.901 USE="nptl udev xorg -dmx -doc -ipv6 -kdrive -minimal (-selinux) -static-libs -suid -tslib -xnest -xvfb" 0 kB CFLAGS="-march=native -pipe -O2 -frename-registers -fweb -fmerge-all-constants -fgcse-sm -fgcse-las -fgcse-after-reload -ftree-vectorize -freorder-blocks-and-partition" gcc-4.7.3 cat /etc/portage/package.unmask/live # live packages I want to test ~media-libs/mesa-9999 ~x11-drivers/xf86-video-ati-9999 ~x11-drivers/xf86-input-evdev-9999 (Those -9999 builds are from the x11 overlay, as I mentioned above.) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
