libtool-1.3.5, ltmain.sh, line 1606:
# How the heck are we supposed to write a wrapper for a shared library?
if test -n "$link_against_libtool_libs"; then
$echo "$modename: error: cannot link shared libraries into libtool libraries"
1>&2
exit 1
fi
Can I suggest that you don't
On Wed, Jan 03, 2001 at 07:42:57AM -0200, Alexandre Oliva wrote:
> On Jan 3, 2001, Chris Leishman <[EMAIL PROTECTED]> wrote:
>
> > Can I suggest that you don't actually link in libtool shared libraries - but
> > you DO add them to the libraries dependancy list (and
encies when module loading -
which doesn't seem to be supported?? (And besides, I don't want to have
to distribute a second library file).
Any suggestions or comments. Is this a bug?
Thanks,
Chris Leishman
___
Libtool mailing list
[EMAIL PR
On Tuesday, April 17, 2001, at 01:50 PM, Alexandre Oliva wrote:
> On Apr 17, 2001, Chris Leishman <[EMAIL PROTECTED]> wrote:
>
>> *** Warning: This library needs some functionality provided by
>> extra/libextra.a.
>
>> Unfortunately I can't get the ap
On Friday, April 20, 2001, at 08:05 AM, Kevin Ryde wrote:
> Chris Leishman <[EMAIL PROTECTED]> writes:
>>
>> Everything compiles ok, but the dlopen fails with the error "not a
>> Mach-O MH_BUNDLE file type" (this error message is output by dlcompat
&g
