Gentoo Archives: gentoo-user

From: Mark Knecht <markknecht@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] mesa build failure
Date: Sat, 27 Jun 2009 17:25:09
Message-Id: 5bdc1c8b0906271025t5fe9e190j860f94e8e59508f8@mail.gmail.com
In Reply to: Re: [gentoo-user] mesa build failure by Alan McKinnon
1 On Sat, Jun 27, 2009 at 10:18 AM, Alan McKinnon<alan.mckinnon@×××××.com> wrote:
2 > On Saturday 27 June 2009 19:10:43 Mark Knecht wrote:
3 >> On Sat, Jun 27, 2009 at 2:34 AM, Alan McKinnon<alan.mckinnon@×××××.com>
4 > wrote:
5 >> > On Saturday 27 June 2009 06:24:12 Mark Knecht wrote:
6 >> >> On Fri, Jun 26, 2009 at 12:30 PM, Alan McKinnon<alan.mckinnon@×××××.com>
7 >> >
8 >> > wrote:
9 >> >> > On Friday 26 June 2009 21:05:01 Mark Knecht wrote:
10 >> >> >> So the weirdness continues. mesa built but then xorg-server failed
11 >> >> >> with the same failure:
12 >> >> >>
13 >> >> >>
14 >> >> >>  * >>> SetUID: [chmod go-r] /usr/bin/Xorg ...
15 >> >> >>                        [ ok ]
16 >> >> >>
17 >> >> >> Switching to xorg-x11 OpenGL interface...ln: creating symbolic link
18 >> >> >> `./libglx.so': File exists
19 >> >> >> !!! Error: Failed to create /lib/libglx.so
20 >> >> >
21 >> >> > Looks like you have a file collision between xorg-server and mesa,
22 >> >> > which is odd as those packages get a lot of testing.
23 >> >> >
24 >> >> > Anything on bugs.gentoo.org?
25 >> >>
26 >> >> Unfortunately it seem that there are bug reports on this and more
27 >> >> unfortunately they have apparently been going on nearly a year now.
28 >> >> It's not a Gentoo thing specifically as there are Ubuntu, Debian and
29 >> >> other distros with reports in their forums.
30 >> >>
31 >> >> There was a possible by hand fix for it but I'll need to look at that
32 >> >> over the weekend to see if it makes sense on this machine.
33 >> >>
34 >> >> Bummer. I hate banging my head up against a wall made of problems no
35 >> >> one seems to be fixing.
36 >> >>
37 >> >> http://bugs.gentoo.org/247685
38 >> >
39 >> > The fix seems (in principle at least) to be brain-dead easy:
40 >> >
41 >> > - all ebuilds that merge opengl files should put them in distinct
42 >> > locations by name to avoid collisions
43 >> > - the contents of /usr/lib64/opengl/xorg-x11/extensions/ should be
44 >> > symlinks with a sane default put there by xorg-server and modified by
45 >> > eselect
46 >> >
47 >> > Nikos's comments are especially sane in that thread. Perhaps he'll come
48 >> > along, see this thread and help you out further.
49 >> >
50 >> > I suspect that the temporary workaround will be to delete a symlink and
51 >> > emerge stuff, then remember to always do this on every future re-emerge
52 >> >
53 >> > --
54 >> > alan dot mckinnon at gmail dot com
55 >>
56 >> In concept it does seem fairly straight forward, but to some extent
57 >> I'm not clear why my previous attempts didn't work, unless the
58 >> questionable files remained behind. What I attempted to do was
59 >> completely remove everything X, but I probably didn't specifically
60 >> remove the stuff in /usr/lib/opengl/xorg-x11/extensions. I was
61 >> expecting the emerge to do that.
62 >
63 > According to the bug report you mentioned earlier, the ebuild is attempting to
64 > perform eselect too late in the process, which fails, and the ebuild
65 > immediately exits.
66 >
67 > So it's not surprising that dodgy files are left behind which you must remove
68 > manually.
69 >
70 > --
71 > alan dot mckinnon at gmail dot com
72 >
73 >
74 So I'm little confused by a couple of the postings in that report. I
75 did emerge -C glproto/eselect/mesa/xorg-server and then made sure
76 there was nothing left in those directories at all. Should I emerge
77 eselect, manually do a select, and then emerge the rest of the files?
78
79 Or emerge eselect and maybe mesa, do the eselect, then xorg-server?
80
81 mesa is currently building. glproto created
82 /usr/lib/opengl/xorg-x11/include, but the other two directories are
83 there yet.
84
85 Cheers,
86 Mark

Replies

Subject Author
Re: [gentoo-user] mesa build failure Mark Knecht <markknecht@×××××.com>