Gentoo Archives: gentoo-amd64

From: Duncan <1i5t5.duncan@×××.net>
To: gentoo-amd64@l.g.o
Subject: [gentoo-amd64] Re: Xorg-server-1.14.1.901 Fails Emerge
Date: Wed, 05 Jun 2013 06:00:33
Message-Id: pan$c5ac6$930fe3ea$643e4f57$2a677991@cox.net
In Reply to: [gentoo-amd64] Xorg-server-1.14.1.901 Fails Emerge by Frank Peters
1 Frank Peters posted on Tue, 04 Jun 2013 22:17:15 -0400 as excerpted:
2
3 > On my system, emerge wants to update xorg-server to 1.14.1.901 but the
4 > compile phase always fails.
5 >
6 > There is no obvious error recorded in the log file, but based on a
7 > gentoo bug report (Bug 472058) it seems that a -Werror compile flag
8 > could be causing the problem.
9 >
10 > My emerge log only reports this:
11 >
12 > cc1: some warnings being treated as errors
13 > make[5]: *** [xf86Events.lo] Error 1
14 > make[5]: *** Waiting for unfinished jobs....
15 > ...
16 > [snip a lot of stuff until the end of log]
17
18 The actual error will be printed above that. Depending on how many
19 make-jobs you are running and some other things, it could actually be
20 QUITE far above that. Doing a search for "error:" (without the quotes,
21 preferably case insensitive) in the log generally finds it pretty fast,
22 and I tested on the log attached to the mentioned bug and found the
23 error there pretty fast, so it should work for this package.
24
25 >
26 >
27 > The bug report (#472058) mentions a failure occurring at a different point,
28 > but -Werror seems to be the cause.
29 >
30 > I waited a few days to see if there were any other reports about a similar
31 > compile failure but so far there are none. I can only assume that xorg-server
32 > is compiling without problem on other systems. Why is it failing on mine?
33 >
34 > Has anyone on the list experienced this failure?
35 >
36 > I would like to remove the -Werror compile flag but without patching
37 > the source I don't see how this could be done.
38
39 The guy in that bug is using pretty radical CFLAGS (-Ofast and those
40 -floop flags), and apparently using gcc 4.8 as well, which is still masked.
41 And one of the problems with upstreams using -Werror by default is that
42 it's hard telling just /what/ a new gcc is going to warn about next, so
43 doing -Werror in a release (as opposed to an internal testing version,
44 which is what the flag is designed for) is pretty much /begging/ for
45 trouble with some gcc version or other, often the newer ones.
46
47 But of course xorg-server-1.14.1.901 isn't a full release, but rather a
48 pre-release version, so upstream /does/ get some leeway with it, tho
49 even then it's really asking for trouble unless you /want/ people
50 testing with all sorts of gcc versions and reporting the -Werror
51 stoppages that come up, as opposed to wanting people's run-time
52 testing. And I don't think that's what they had in mind so I don't
53 know why they're doing -Werror, but anyway...
54
55 I believe I read, I think in flameyes' blog (where this specific error
56 was being used as a reason NOT to do -Werror, IIRC), that that specific
57 error is a known issue with -Werror, due to a new warning in gcc 4.8.
58
59
60 Which means... if you're trying to build with gcc 4.8, try again with
61 4.7.x. If you're not using gcc 4.8, then your error is likely a
62 different bug.
63
64 And also... USE=kdrive? In the bug, the log says USE=kdrive, even
65 tho the reported package settings said USE=-kdrive. So I'm not
66 sure what's up there. But certainly, unless you have a reason
67 to run USE=kdrive, please ensure that you're running USE=-kdrive.
68
69
70 Meanwhile, I don't have 4.8 installed here, but I can confirm
71 that xorg-server-1.14.1.901 built here just fine, with gcc
72 4.7.3. I should mention, however, that I'm running live-git
73 -9999 version ebuilds from the x11 overlay for mesa and my
74 two drivers (xf86-video-ati and xf86-input-evdev), among other
75 things. It's possible that there's some issue with the non-git
76 versions.
77
78 But xorg-server-1.14.1.901 is definitely built/installed/running
79 fine here!
80
81 [ebuild R ] x11-base/xorg-server-1.14.1.901:0/1.14.1.901
82 USE="nptl udev xorg -dmx -doc -ipv6 -kdrive -minimal
83 (-selinux) -static-libs -suid -tslib -xnest -xvfb" 0 kB
84
85 CFLAGS="-march=native -pipe -O2 -frename-registers -fweb
86 -fmerge-all-constants -fgcse-sm -fgcse-las -fgcse-after-reload
87 -ftree-vectorize -freorder-blocks-and-partition"
88
89 gcc-4.7.3
90
91 cat /etc/portage/package.unmask/live
92 # live packages I want to test
93
94 ~media-libs/mesa-9999
95 ~x11-drivers/xf86-video-ati-9999
96 ~x11-drivers/xf86-input-evdev-9999
97
98 (Those -9999 builds are from the x11 overlay,
99 as I mentioned above.)
100
101 --
102 Duncan - List replies preferred. No HTML msgs.
103 "Every nonfree program has a lord, a master --
104 and if you use the program, he is your master." Richard Stallman

Replies

Subject Author
Re: [gentoo-amd64] Re: Xorg-server-1.14.1.901 Fails Emerge Frank Peters <frank.peters@×××××××.net>
Re: [gentoo-amd64] Re: Xorg-server-1.14.1.901 Fails Emerge Frank Peters <frank.peters@×××××××.net>