public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bernhard Auzinger <e0026053@student.tuwien.ac.at>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] eselect opengl set xorg-x11 keeps breaking my headers
Date: Wed, 28 Jun 2006 20:18:01 +0200	[thread overview]
Message-ID: <200606282018.01478.e0026053@student.tuwien.ac.at> (raw)
In-Reply-To: <1151449927.10564.2.camel@malory>

Am Mittwoch 28 Juni 2006 01:12 schrieb Alex Bennee:
> 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.
>
> 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.
>
> --
> Alex, homepage: http://www.bennee.com/~alex/
> Declared guilty... of displaying feelings of an almost human nature. --
> Pink Floyd, "The Wall"

Try to delete the gl-headers located in the "emul" directory. 
Usually /usr/include/GL contains symlinks to /usr/lib, but sometimes things 
go wrong with "early versions" of the emul stuff (they don't disappear by 
upgrading or unmerging) and eselect places a symlink which points 
to /usr/lib32 instead of /usr/lib or /usr/lib64. /usr/lib32 again is a 
symlink to the /emul directory. Delete gl-headers in the /emul directory to 
which the symlinks in /usr/include/GL point to.

rgds

Bernhard
-- 
gentoo-amd64@gentoo.org mailing list



  parent reply	other threads:[~2006-06-28 18:04 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
2006-06-30 20:18     ` [gentoo-amd64] " Duncan
2006-06-28 18:18 ` Bernhard Auzinger [this message]
2006-06-29  9:06 ` [gentoo-amd64] " 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=200606282018.01478.e0026053@student.tuwien.ac.at \
    --to=e0026053@student.tuwien.ac.at \
    --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