When I try to emerge metisse 0.3.3 (which has been marked stable for x86?) I get: /usr/lib/libNucleo.so: undefined reference to `glXDestroyContext@LIBGL' /usr/lib/libNucleo.so: undefined reference to `glTexGenfv@LIBGL' /usr/lib/libNucleo.so: undefined reference to `glGetString@LIBGL' /usr/lib/libNucleo.so: undefined reference to `glOrtho@LIBGL' /usr/lib/libNucleo.so: undefined reference to `glGetFloatv@LIBGL' /usr/lib/libNucleo.so: undefined reference to `glPixelStorei@LIBGL' collect2: ld returned 1 exit status make[3]: *** [FvwmAmetista] Error 1 make[3]: Leaving directory `/var/tmp/portage/metisse-0.3.3/work/metisse-0.3.3/FvwmAmetista/main' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/metisse-0.3.3/work/metisse-0.3.3/FvwmAmetista' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/metisse-0.3.3/work/metisse-0.3.3' make: *** [all] Error 2 !!! ERROR: x11-wm/metisse-0.3.3 failed. !!! Function src_compile, Line 34, Exitcode 2 !!! make failed I'm on a p4 with smp enabled so MAKEOPTS="-j3". Reproducible: Always Steps to Reproduce: Portage 2.0.50-r11 (default-x86-2004.2, gcc-3.3.4, glibc-2.3.3.20040420-r1, 2.6.8-gentoo-r3) ================================================================= System uname: 2.6.8-gentoo-r3 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz Gentoo Base System version 1.5.3 Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1
Please give us full `emerge info`. Which version of xorg-x11 (or xfree) are you using? Did you run opengl-update if you had switched one from the other?
Portage 2.0.50-r11 (default-x86-2004.2, gcc-3.3.4, glibc-2.3.3.20040420-r1, 2.6.8-gentoo-r3) ================================================================= System uname: 2.6.8-gentoo-r3 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz Gentoo Base System version 1.5.3 Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=pentium4 -O2 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=pentium4 -O2 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="ftp:///ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ ftp://vlaai.snt.ipv6.utwente.nl/pub/os/linux/gentoo/ ftp://ftp6.uni-erlangen.de/pub/mirrors/gentoo ftp://ftp.ipv6.uni-muenster.de/pub/linux/distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aalib acpi aim alsa apache2 apm arts avi berkdb bitmap-fonts cdr crypt cups divx4linux dvd encode esd fbcon flashfoomaticdb freetype gdbm gif gimp gnome gpm gtk gtk2 imlib ipv6 java jikes jpeg kde ldap libg++ libwww mad mikmod mmx motif mpeg msn ncurses nls oggvorbis opengl oscar oss pam pcmcia pcre pdflib perl php png postgres python qt quicktime readline samba scanner sdl slang spell sse sse2 ssl svga tcltk tcpd tiff truetype usb videos wifi x86 xinerama xml2 xmms xprint xv zlib" x11-base/xorg-x11: 6.7.0-r2 I have ran opengl-update. media-video/nvidia-glx: 1.0.6111
This problem never went away and continues to bug me. I recently installed version 6.8.0-r1 of xorg-x11 and with it recompiled nvidia-glx. I ran `opengl-update nvidia` after that. It still fails at the exact same place... Any help would be appreciated.
Please attach a full log of `emerge nucleo` and `emerge metisse`. I cannot reproduce the bug on any of my machines.
Can you tell me how to do this? I'm not sure exactly what you mean by full log. Thank you, Diego
No worries, just set PORT_LOGDIR=/var/log/portage in /etc/make.conf and run `emerge nuculeo metisse`, then you will get /var/log/portage/????-nucleo-0.1-r1.log and /var/log/portage/????-metisse-0.3.3.log. (If you have more than one log files, please attach all of them)
Hmm...this is odd. Apparently metisse blocks fvwm, yet I had fvwm and metisse (0.3.2) installed. Upon typing emerge nucleo metisse it now said that there was a blocking issue with fvwm, so I removed fvwm and now it all works fine. Why did this not happen when 1) I first installed fvwm after metisse or 2) I tried emerge --update world? Maybe someone recently made a change to the ebuild?
I see. fvwm and metisse should block each other. metisse blocks fvwm but fvwm didn't block metisse, so you could emerge fvwm even though you had metisse-0.3.2. I made fvwm block metisse, so this should be fixed now. Thanks for the bug report.
Thank you. I wasn't sure if this was worthy of a bug report at first (I really don't like wasting developers' time and had never started a bug report here before) but apparently some good came out of it. Thanks for handling this report with professionalism and treating it as important, and then of course fixing the problem.
