Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 517950

Summary: x11-libs/gtkglext-1.2.0-r2 - ?
Product: Gentoo Linux Reporter: xiando <oyvinds>
Component: [OLD] GNOMEAssignee: Gentoo Linux bug wranglers <bug-wranglers>
Status: RESOLVED NEEDINFO    
Severity: normal    
Priority: Normal    
Version: unspecified   
Hardware: AMD64   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description xiando 2014-07-24 10:31:00 UTC
/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/../../../../x86_64-pc-linux-gnu/bin/ld: skipping incompatible /usr/lib64/libGLU.so when searching for -lGLU
/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/../../../../x86_64-pc-linux-gnu/bin/ld: skipping incompatible /usr/lib64/libGL.so when searching for -lGL
/usr/lib64/libXmu.so: could not read symbols: File in wrong format
collect2: error: ld returned 1 exit status
distcc[26699] ERROR: compile (null) on localhost failed
make[4]: *** [libgdkglext-x11-1.0.la] Error 1
make[4]: Leaving directory `/var/tmp/portage/x11-libs/gtkglext-1.2.0-r2/work/gtkglext-1.2.0-abi_x86_32.x86/gdk'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/var/tmp/portage/x11-libs/gtkglext-1.2.0-r2/work/gtkglext-1.2.0-abi_x86_32.x86/gdk'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/var/tmp/portage/x11-libs/gtkglext-1.2.0-r2/work/gtkglext-1.2.0-abi_x86_32.x86/gdk'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/x11-libs/gtkglext-1.2.0-r2/work/gtkglext-1.2.0-abi_x86_32.x86'
make: *** [all] Error 2   
 * ERROR: x11-libs/gtkglext-1.2.0-r2::gentoo failed (compile phase):


Reproducible: Always

Steps to Reproduce:
1. Try to compile when using ABI_X86="32 64"
2. watch compile fail
3. be sad



I am not sure if I am doing it wrong or the ebuild is broken somehow but it's not supposed to try to link with 64bit libraries when compiling for 32bit now is it?
Comment 1 Jeroen Roovers (RETIRED) gentoo-dev 2014-07-24 10:54:46 UTC
1) Please attach the entire build log to this bug report.
2) Please post your `emerge --info' output in a comment.