Re: [libtool 2.1a] testsuite: 25 49 failed (cockpit error)
* Lynn Ten Eyck wrote on Fri, Feb 16, 2007 at 03:53:29PM CET: > On Fri, 2007-02-16 at 14:11 +0100, Ralf Wildenhues wrote: > > > The failure of 25 is new to me. Do you have a libltdl.so.7 installed in > > a place where the link editor finds it by default? If yes, is there a > > libltdl.la file installed alongside with it? If not, why not, who > > removed it? It should be present. > > This was a cockpit error. I did ./configure && make && make install, > which installed the new system in /usr/local/. My path was set to pick > up the new versions of the excutables, but the linker was not told where > to find the libraries. But that shouldn't be necessary. If the libltdl.la file exists, then libtool should hard-code the path to the library into the ltdldemo program. > lynn> ls -l /usr/local/lib/libltd* > -rw-r--r-- 1 root root 189678 Feb 15 21:55 /usr/local/lib/libltdl.a > -rwxr-xr-x 1 root root950 Feb 15 21:55 /usr/local/lib/libltdl.la* > lrwxrwxrwx 1 root root 16 Feb 15 21:55 /usr/local/lib/libltdl.so -> > libltdl.so.7.0.0* > lrwxrwxrwx 1 root root 16 Feb 15 21:55 /usr/local/lib/libltdl.so.7 -> > libltdl.so.7.0.0* > -rwxr-xr-x 1 root root 113165 Feb 15 21:55 /usr/local/lib/libltdl.so.7.0.0* > > /usr/local/lib64 is empty. > > I re-ran the tests with the LD_LIBRARY_PATH set to explicitly include > /usr/local/lib. Test 25 passed, and test 49 gave the known failure. > If you would like the log, I can send it, but I doubt if there is any > new information in it. I turned on the -v flag for verbose output. Yes, please do not set LD_LIBRARY_PATH, then run make check-local TESTSUITEFLAGS='-v -d -x 25' cd tests/testsuite.dir and send tests/testsuite.dir/25/config.log. Thanks, Ralf ___ Bug-libtool mailing list Bug-libtool@gnu.org http://lists.gnu.org/mailman/listinfo/bug-libtool
Re: [libtool 2.1a] testsuite: 25 49 failed (cockpit error)
Hello, Ralf - On Fri, 2007-02-16 at 14:11 +0100, Ralf Wildenhues wrote: > The failure of 25 is new to me. Do you have a libltdl.so.7 installed in > a place where the link editor finds it by default? If yes, is there a > libltdl.la file installed alongside with it? If not, why not, who > removed it? It should be present. This was a cockpit error. I did ./configure && make && make install, which installed the new system in /usr/local/. My path was set to pick up the new versions of the excutables, but the linker was not told where to find the libraries. lynn> ls -l /usr/local/lib/libltd* -rw-r--r-- 1 root root 189678 Feb 15 21:55 /usr/local/lib/libltdl.a -rwxr-xr-x 1 root root950 Feb 15 21:55 /usr/local/lib/libltdl.la* lrwxrwxrwx 1 root root 16 Feb 15 21:55 /usr/local/lib/libltdl.so -> libltdl.so.7.0.0* lrwxrwxrwx 1 root root 16 Feb 15 21:55 /usr/local/lib/libltdl.so.7 -> libltdl.so.7.0.0* -rwxr-xr-x 1 root root 113165 Feb 15 21:55 /usr/local/lib/libltdl.so.7.0.0* /usr/local/lib64 is empty. I re-ran the tests with the LD_LIBRARY_PATH set to explicitly include /usr/local/lib. Test 25 passed, and test 49 gave the known failure. If you would like the log, I can send it, but I doubt if there is any new information in it. I turned on the -v flag for verbose output. I suspect that when the support for this system is fully worked out, the $prefix variables should expand to /usr/local/lib64 instead of /usr/local/lib -- but that is incompatible with a whole lot of existing configuration scripts. (Boy, do I hope autoreconf works on this one.) Thank you again, and I apologize for taking up your time on what is obviously going to be a very busy weekend. Best regards, Lynn -- Lynn F. Ten Eyck <[EMAIL PROTECTED]> E. T. S. Walton Visiting Professor UCD Conway Institute Belfield Dublin 4 Office: S055 Tel: +353 1 716 6845 ___ Bug-libtool mailing list Bug-libtool@gnu.org http://lists.gnu.org/mailman/listinfo/bug-libtool
