I am building gnome on AMD64. It seems libtool is looking for libGLU in /usr/lib/ when in fact it should be looking in /usr/lib64? Reproducible: Always Steps to Reproduce:
Created attachment 183563 [details] Build log
Created attachment 183564 [details] Environment
Created attachment 183566 [details] emerge --info
media-libs/ftgl-2.1.3_rc5 also suffers the same problem. Actually this appears to be a libtool issue, the more I think about it. I am using libtool-1.5.26. Attempting the same again updating to libtool-2.2.6a.
(In reply to comment #4) Okay, updating libtool made no difference. I also tried re-emerging mesa (which creates libGLU) and this made no difference, either. Both packages still fail to build.
are you using nvidia closed source drivers ?
(In reply to comment #6) > are you using nvidia closed source drivers ? > If by this you mean "Am I using x11-drivers/nvidia-drivers", then yes. I also get the nVidia logo when X starts, so I assume so.
then that's either an eselect or a nvidia bug. Reassigning to proper maintainers.
(In reply to comment #8) > then that's either an eselect or a nvidia bug. Reassigning to proper > maintainers. > Are you sure? I'm thinking that it is a libtool or pygtkglext bug. The problem is that it is looking for libGLU in the wrong place, not that libGLU has been installed in the wrong place.
Temporary workaround. I symlinked /usr/lib64/libGLU.* to /usr/lib. Merge was successful after that. Not a proper fix though.
(In reply to comment #10) > Temporary workaround. I symlinked /usr/lib64/libGLU.* to /usr/lib. Merge was > successful after that. Not a proper fix though. > Sorry. It seems that this bug was probably caused my own error at some point. I did not know that /usr/lib was supposed to be a symlink to /usr/lib64, and somehow I had two separate directories. I have now remedied this problem. This bug is a non-bug.
