First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 135643
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo X packagers <x11@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Robert Führicht <the_master_of_disaster@gmx.at>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 135643 depends on: Show dependency tree
Show dependency graph
Bug 135643 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2006-06-05 09:25 0000
From the ebuild:

        amd64? (
                app-emulation/emul-linux-x86-xlibs
                || (
                        >=media-video/nvidia-glx-1.0.6629-r3
                        >=x11-drivers/ati-drivers-8.8.25-r1 ) )"

I'm using the r300 mesa driver, which I pull from CVS with an ebuild. When
updating world, portage pulls either nvidia-glx or ati-drivers, and I want
neither of those packages.

Possible solution(?):

- Update mesa (produce 32 bit libs on an amd64 multilib system) and x11-drm
(include a CVS snapshot of the r300 driver).
- Introduce a new virtual like "virtual/opengl32" which these (and future)
packages can provide.

------- Comment #1 From Chris Gianelloni (RETIRED) 2006-06-05 09:44:41 0000 -------
This totally does not belong to us.  The ebuild is 100% correct for the current
state of the tree.  This really needs to be assigned to the X folks.  Also,
there's another bug somewhere (I can't find it right now) about r300 and 32-bit
MESA.  Once there actually *is* a multilib-friendly mesa ebuild, then this can
be changed by us.

------- Comment #2 From Stefan Schweizer 2006-06-05 09:51:35 0000 -------
The other bug for reference:

http://bugs.gentoo.org/show_bug.cgi?id=133727

------- Comment #3 From Joshua Baergen (RETIRED) 2006-06-05 20:36:37 0000 -------
If this is a mesa problem then it belongs to x11.

------- Comment #4 From Donnie Berkholz 2006-06-05 22:00:17 0000 -------
Chris, see below. Clientside dri modules means the 3d drivers, including r300.

*emul-linux-x86-xlibs-7.0 (17 Mar 2006)

  17 Mar 2006; Herbie Hopkins <herbs@gentoo.org>
  -emul-linux-x86-xlibs-2.2.1.ebuild, -emul-linux-x86-xlibs-2.2.1-r1.ebuild,
  +emul-linux-x86-xlibs-7.0.ebuild:
  Bump with libs from xorg-7.0, include clientside dri modules (bug 115605) to
  better support 32bit opengl apps with oss drivers. Don't install opengl
  header files so as not to confuse eselect-opengl (bug 109922).

------- Comment #5 From Chris Gianelloni (RETIRED) 2006-06-06 05:49:28 0000 -------
$ cvs diff
Index: quake3-bin-1.32c.ebuild
===================================================================
RCS file:
/var/cvsroot/gentoo-x86/games-fps/quake3-bin/quake3-bin-1.32c.ebuild,vretrieving
revision 1.1
diff -u -b -B -r1.1 quake3-bin-1.32c.ebuild
--- quake3-bin-1.32c.ebuild     9 May 2006 14:23:01 -0000       1.1
+++ quake3-bin-1.32c.ebuild     6 Jun 2006 12:47:13 -0000
@@ -27,6 +27,7 @@
        amd64? (
                app-emulation/emul-linux-x86-xlibs
                || (
+                       >=app-emulation/emul-linux-x86-xlibs-7.0
                        >=media-video/nvidia-glx-1.0.6629-r3
                        >=x11-drivers/ati-drivers-8.8.25-r1 ) )"

I have "fixed" this in CVS.  The only problem that I see now is that I have no
way of guaranteeing that someone has a compatible video card anymore.  I guess
I'll just have to wait for the flood of bugs from people with cards that don't
have 32-bit support yet.  ;]

------- Comment #6 From Donnie Berkholz 2006-06-06 08:07:49 0000 -------
Feel free to point bugs about this at me, I don't mind supporting the use of
open-source drivers. =)

------- Comment #7 From Chris Gianelloni (RETIRED) 2006-06-06 11:36:03 0000 -------
I don't have a problem with it, either.  It was just that before it was pretty
simple.  You either had an ATI or NVIDIA card, and you used the binary drivers,
or it didn't work.  Now it'll just be a bit more ambiguous.

I'm sure there's aprobably a couple other ebuilds in the tree that need this
sort of working over, too.

First Last Prev Next    No search results available      Search page      Enter new bug