[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: libtool-1.15.23b (amd64-unknown-freebsd6.2) check results
From: |
Ralf Wildenhues |
Subject: |
Re: libtool-1.15.23b (amd64-unknown-freebsd6.2) check results |
Date: |
Thu, 22 Feb 2007 10:21:57 +0100 |
User-agent: |
Mutt/1.5.13 (2007-02-12) |
Hello David,
* David Fang wrote on Thu, Feb 22, 2007 at 12:25:47AM CET:
>
> Below is an excerpt from [g]make check of libtool-1.15.23b on
> amd64-unknown-freebsd6.2 (most PASSes omitted):
> FAIL: hardcode.test
> FAIL: pdemo-make.test
> SKIP: pdemo-exec.test
> SKIP: pdemo-inst.test
[...]
> PASS: tagdemo-conf.test
> PASS: tagdemo-make.test
> FAIL: tagdemo-exec.test
> PASS: tagdemo-shared.test
> PASS: tagdemo-make.test
> FAIL: tagdemo-exec.test
Please show verbose output for these test groups (see README for how to
do that). Thanks.
> (Are these failures serious?)
> Let me know if you need any more information about any of these test
> cases, or my configuration.
Probably. I'll ask when I see the verbose output.
> I've been chasing a problem with libtool installing shared-lib executables
> referring to libraries in the build-dir (FreeBSD only), so I'm hoping that
> the upcoming release fixes things. I'm seeing post-install errors:
>
> /libexec/ld-elf.so.1: Cannot open "./.libs/libhello.so"
>
> on a hello-world shared library demo project.
> Was this resolved since 1.15.22?
Please post the hello-world shared library demo project. You can
exclude generated files. Then I should be able to tell whether there
is a bug in Libtool or the project. Is this on FreeBSD 6.2 and 4.3?
(An often-seen glitch is to refer to uninstalled libtool libraries as
-L../lib -lfoo
rather than
../lib/libfoo.la
which can cause the issue you mentioned on some systems.)
Cheers, and thanks for the feedback,
Ralf