public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Duncan" <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: eselect opengl set xorg-x11 keeps breaking my headers
Date: Wed, 28 Jun 2006 17:33:41 +0000 (UTC)	[thread overview]
Message-ID: <e7uehk$hd4$1@sea.gmane.org> (raw)
In-Reply-To: 1151449927.10564.2.camel@malory

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?

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.

> 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, then redigest and merge them.  I
routinely do this with some packages, say to strip out a filterflags call
that was thrown in by the Gentoo maintainer due to some problem with some
subarchs of x86, where the flags in question work just fine on at least my
amd64, for instance.  That's the beauty of having ebuilds that are
basically bash scripts -- they are easily modified by anyone who knows
bash -- the portage system was deliberately set up to allow this, and a
lot of work has gone into and will continue to go into ensuring that this
easy modifiability remains the case.



-- 
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

-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2006-06-28 17:36 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 ` Duncan [this message]
2006-06-30  8:18   ` [gentoo-amd64] " Alex Bennee
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='e7uehk$hd4$1@sea.gmane.org' \
    --to=1i5t5.duncan@cox.net \
    --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