<div dir="ltr"><div><div><div>Need to use CentOS 5.10 for work. libX11-devel is installed for both 32 and 64 bit. Wrote a hello world program and compiled:<br></div><br>$ gcc -L/usr/lib64 hello.c -lX11<br>/usr/bin/ld: skipping incompatible /usr/lib/libX11.so when searching for -lX11<br>
/usr/bin/ld: cannot find -lX11<br>collect2: ld returned 1 exit status<br><br></div>Took me a second to figure out why:<br><br>$ ll /usr/lib/libX11.so*<br>lrwxrwxrwx 1 root root 15 Apr 17 18:52 /usr/lib/libX11.so -> libX11.so.6.2.0<br>
lrwxrwxrwx 1 root root 15 Apr 12 13:59 /usr/lib/libX11.so.6 -> libX11.so.6.2.0<br>-rwxr-xr-x 1 root root 1062108 Oct 5 2011 /usr/lib/libX11.so.6.2.0<br><br>$ ll /usr/lib64/libX11*<br>lrwxrwxrwx 1 root root 15 Apr 12 13:59 /usr/lib64/libX11.so.6 -> libX11.so.6.2.0<br>
-rwxr-xr-x 1 root root 1099816 Oct 5 2011 /usr/lib64/libX11.so.6.2.0<br><br><br></div><div>Of course, after making the appropriate symbolic link in /usr/lib64, my little hello world program compiled and linked.<br><br>I'm curious. Why does CentOS (and presumably rhel, fedora) make the libX11.so -> libX11.so.6.2.0 link in /usr/lib but not /usr/lib64?<br>
<br></div></div>