On my system, the autoreconf command is breaking the libtool installation of libdrm.so. The final installed libraries do not have the .so suffix, so they can't be found at link time. Fortunately, nothing has broken because I had the static library installed. Is anyone else seeing this behavior?
With autoreconf: $ ls -l dest/usr/lib/ total 84 lrwxrwxrwx 1 dan users 12 2006-05-19 12:44 libdrm -> libdrm.2.0.0 lrwxrwxrwx 1 dan users 12 2006-05-19 12:44 libdrm.2 -> libdrm.2.0.0 -rwxr-xr-x 1 dan users 72795 2006-05-19 12:44 libdrm.2.0.0 -rwxr-xr-x 1 dan users 757 2006-05-19 12:44 libdrm.la drwxr-xr-x 2 dan users 4096 2006-05-19 12:44 pkgconfig Without autoreconf: $ ls -l dest/usr/lib/ total 84 -rwxr-xr-x 1 dan users 769 2006-05-19 12:33 libdrm.la lrwxrwxrwx 1 dan users 15 2006-05-19 12:33 libdrm.so -> libdrm.so.2.0.0 lrwxrwxrwx 1 dan users 15 2006-05-19 12:33 libdrm.so.2 -> libdrm.so.2.0.0 -rwxr-xr-x 1 dan users 72807 2006-05-19 12:33 libdrm.so.2.0.0 drwxr-xr-x 2 dan users 4096 2006-05-19 12:33 pkgconfig The culprit seems to be libtool because this is what's in libdrm.la in the build tree in each case. With autoreconf: $ grep name libdrm/libdrm.la # The name that we can dlopen(3). dlname='libdrm.2' library_names='libdrm.2.0.0 libdrm.2 libdrm' # The name of the static archive. Without autoreconf: $ grep name libdrm/libdrm.la # The name that we can dlopen(3). dlname='libdrm.so.2' library_names='libdrm.so.2.0.0 libdrm.so.2 libdrm.so' # The name of the static archive. The autoreconf command isn't needed in my testing. Can anyone confirm this? -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
