From: Alex Bennee <kernel-hacker@bennee.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: eselect opengl set xorg-x11 keeps breaking my headers
Date: Fri, 30 Jun 2006 09:18:17 +0100 [thread overview]
Message-ID: <1151655497.26625.3.camel@malory> (raw)
In-Reply-To: <e7uehk$hd4$1@sea.gmane.org>
On Wed, 2006-06-28 at 17:33 +0000, Duncan wrote:
> Alex Bennee <kernel-hacker@bennee.com> posted
> 1151449927.10564.2.camel@malory, excerpted below, on Wed, 28 Jun 2006
> 00:12:06 +0100:
>
> > Despite no longer having the emulation libraries installed eselect
keep
> > screwing up my headers to point at 32 bit glx stuff. This obviously
breaks
> > various X related compiles.
>
> What does equery belongs </path/to/32-bit-file> return? What video
> drivers are you running?
Ahh the emul-libs keep getting pulled in. Probably because of OO. Some
of the files actually belong to eselect:
malory GL # equery b /usr/lib32/opengl/global/include/glxext.h
[ Searching for file(s) /usr/lib32/opengl/global/include/glxext.h in
*... ]
app-admin/eselect-opengl-1.0.3
(/usr/lib32/opengl/global/include/glxext.h)
> If you are running slaveryware video drivers, equery belongs will
probably
> return them (assuming you merged them using portage, anyway). If it
> returns nothing and you didn't manually (not using portage, so it
doesn't
> know about the file) install something using that file, it's likely
safe to
> delete it. Just to be safe, however, I'd rename it to
*.2006.07.28.remove
> (a month later) or something similar. Then after that date, if you've
not
> found anything broken, go ahead and remove it, as even if it /does/
break
> something it can't be too critical if you've not used it once in 30
days.
No just plain OS drivers (I will be experimenting with the OS r300
drivers when I get a chance).
> > Does anyone know how I can stop it doing this? Unfortunately its
called
> > during the ebuild so I can't manually fix them and re-run the build.
>
> Actually, that isn't entirely the case. See the Gentoo Handbook,
Working
> with Portage section, and the ebuild (1 and 5) manpages for some
details,
> but many Gentoo users have their own local overlays, where they copy
> ebuilds and modify them as desired,
> <snip>
I agree. I do actually run my own overlay for some bits and pieces.
However reading through the Xorg stuff I'd rather leave it to people
more qualified than me :-)
I think the behaviour I'm seeing may be related to
http://bugs.gentoo.org/show_bug.cgi?id=109922
>
>
>
> --
> 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
>
--
Alex, homepage: http://www.bennee.com/~alex/
Mal: "Nice shot." Jayne: "I was aiming for his head."
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2006-06-30 8:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 23:12 [gentoo-amd64] eselect opengl set xorg-x11 keeps breaking my headers Alex Bennee
2006-06-28 17:33 ` [gentoo-amd64] " Duncan
2006-06-30 8:18 ` Alex Bennee [this message]
2006-06-30 20:18 ` [gentoo-amd64] " Duncan
2006-06-28 18:18 ` [gentoo-amd64] " Bernhard Auzinger
2006-06-29 9:06 ` Bernhard Auzinger
2006-06-30 8:17 ` Alex Bennee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1151655497.26625.3.camel@malory \
--to=kernel-hacker@bennee.com \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox