"Gary V. Vaughan" <[EMAIL PROTECTED]> writes:
>
> The problem is that libtool.m4 jumps through a bunch if hoops to
> find an echo that doesn't interpret backslashes, since it is quite a
> common problem, which causes libtool a lot of headaches.
Sorry I'm a bit thick, I've not been addressing the
On Sunday 22 April 2001 1:40 am, Kevin Ryde wrote:
> "Gary V. Vaughan" <[EMAIL PROTECTED]> writes:
> > Have either of you had any success with my workaround?
> >
> >make ECHO="/bin/sh `pwd`/libtool --fallback-echo"
> >
> > Or something equivalent...
>
> Not quite sure I understand. Should t
"Gary V. Vaughan" <[EMAIL PROTECTED]> writes:
>
> Have either of you had any success with my workaround?
>
>make ECHO="/bin/sh `pwd`/libtool --fallback-echo"
>
> Or something equivalent...
Not quite sure I understand. Should that be ECHO=/bin/echo on the
configure command? Doesn't seem t
On Friday 20 April 2001 4:50 am, Chris Leishman wrote:
> 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
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
>> when NSCreateObjectFileImageFromFile return
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
> when NSCreateObjectFileImageFromFile returns
> NSObjectFileImageInapproriateFile).
Perhaps the backtick quot
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 application to load the libshared.a file
>> as
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 application to load the libshared.a file
> as a dynamic module (not unsurprising). Even if I specify -dlopen on
> the c
Hi,
I've been playing with the latest alpha release of libtool and have come
across this issue.
When linking a shared library (for a dynamically loaded module), the
project I'm working on uses code from a subdirectory that has been
compiled into an archive library (.a).
So the link line is so