From: Christian Biesinger
It seems to me that this is a bug in any case. Not only is
-version-number inconsistent with -version-info here. Even if BeOS has a
versioning system for libraries and libtool gets support for that, this
would still leave -version-number broken for other platforms wher
Hi Olly,
* Olly Betts wrote on Wed, May 10, 2006 at 04:38:08PM CEST:
> On 2006-05-10, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> > - there was actually a regression in 1.5.22 over 1.5.20 which caused
> > some paths to be incorrectly removed on FreeBSD and some other BSD
> > variants. Has si
On 2006-05-10, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> - there was actually a regression in 1.5.22 over 1.5.20 which caused
> some paths to be incorrectly removed on FreeBSD and some other BSD
> variants. Has since been fixed in CVS branch-1-5 (and HEAD).
Is there likely to be a 1.5.24 r
Hi,
Please ignore. The space between the "-L" and the "/usr/local/lib" was
the culprit.
With friendly regards,
Takis
___
http://lists.gnu.org/mailman/listinfo/libtool
Hello Ralf,
Here is a revised patch. I changed the recognition of the Sun compilers,
and the whole_archive_flag_spec and postdeps, so that now all 112 tests PASS.
> > With this patch, the FAILs are turned into PASS; all tests PASS or SKIP.
>
> Which ones skip?
Good question. I had many SKIPs, bu
Hi Panagiotis,
* Panagiotis Issaris wrote on Wed, May 10, 2006 at 01:05:50PM CEST:
>
> I encountered a problem while trying to build a softwarepackage (JRTPLib
> [1]) which uses libtool on FreeBSD 6.0. The library path (-L /usr/local/lib)
> added on the libtool commandline, seems to be removed a
Hi,
I encountered a problem while trying to build a softwarepackage (JRTPLib
[1]) which uses libtool on FreeBSD 6.0. The library path (-L /usr/local/lib)
added on the libtool commandline, seems to be removed and not passed on
to GCC. I will try with more recent versions, but I did not find anyt
