On Mar 6, 2000, "Gary V. Vaughan" <[EMAIL PROTECTED]> wrote:
>> Only CVS libtool will implicitly add any necessary -R flags and other
>> dependencies from the .la file. And that's the reason why this file
>> is installed.
> IIRC, the 1.3b release does this too.
Yup. I forget an alpha release
On Mon, Mar 06, 2000 at 10:24:44PM -0300, Alexandre Oliva wrote:
> On Mar 6, 2000, Assar Westerlund <[EMAIL PROTECTED]> wrote:
>
> > I wrote:
> >> "Gary V. Vaughan" <[EMAIL PROTECTED]> writes:
> >> > It has been working forever!
>
> An odd use of the word `forever' :-)
Okay, my bad. I thought
On Mon, Mar 06, 2000 at 10:15:46PM +0100, Assar Westerlund wrote:
> "Gary V. Vaughan" <[EMAIL PROTECTED]> writes:
> > It has been working forever!
> >
> > libtool --mode=link gcc -o foo bar.c -L/usr/local/lib -lbaz
>
> Aha, I did /usr/local/lib/libbaz.la and then I got the
> not-obvious-to-me
On Mar 6, 2000, Assar Westerlund <[EMAIL PROTECTED]> wrote:
> I wrote:
>> "Gary V. Vaughan" <[EMAIL PROTECTED]> writes:
>> > It has been working forever!
An odd use of the word `forever' :-)
> gcc ... -L/usr/local/lib -lbaz
> and does not add the (on this platform) required
> -Wl,-rpath,/usr/
I wrote:
> "Gary V. Vaughan" <[EMAIL PROTECTED]> writes:
> > It has been working forever!
> >
> > libtool --mode=link gcc -o foo bar.c -L/usr/local/lib -lbaz
>
> Aha, I did /usr/local/lib/libbaz.la and then I got the
> not-obvious-to-me error:
>
> /usr/local/lib/.libs/libbaz.a not found
But,
"Gary V. Vaughan" <[EMAIL PROTECTED]> writes:
> It has been working forever!
>
> libtool --mode=link gcc -o foo bar.c -L/usr/local/lib -lbaz
Aha, I did /usr/local/lib/libbaz.la and then I got the
not-obvious-to-me error:
/usr/local/lib/.libs/libbaz.a not found
Thanks.
/assar
On Mon, Mar 06, 2000 at 07:09:28PM +0100, Assar Westerlund wrote:
> Hi. Two questions:
>
> 1. Why are the *.la files installed? The comment says:
>
> # Install the pseudo-library for information purposes.
They are installed so that you can link against them with libtool:
libtool --mo
Hi. Two questions:
1. Why are the *.la files installed? The comment says:
# Install the pseudo-library for information purposes.
2. How do you link against an installed library?
As far as I can tell, there's no support of doing that. And it would
seem to me that libtool is the ideal
I notice that AC_CANONICAL_BUILD is now considered to be an internal
macro (CVS autoconf) and is renamed _AC_CANONICAL_BUILD. CVS libtool
is still requiring AC_CANONICAL_BUILD so it does not work with CVS
autoconf. Will this be fixed soon?
Bob
==
Bob Friesenh
