Hallo Ralf,
Ralf Wildenhues wrote:
> This patch restores the environment for mode=execute. Unfortunately,
> it also means more overhead for every libtool invocation. :-(
> (At least no fork&exec.)
Negligible time overhead... but an unfortunate ugliness all the same.
> OK to apply?
Yes, nice f
* Eric Blake wrote on Fri, Feb 24, 2006 at 02:51:07PM CET:
> According to Christopher Hulbert on 2/22/2006 5:56 AM:
> >
> > Actually it seems the problem is that a unix-style path is passed to
> > lib as the library name. This is probably not the correct fix, but
> > what I did was add the followi
Hi Gary,
* Gary V. Vaughan wrote on Thu, Feb 23, 2006 at 11:53:39PM CET:
> Ralf Wildenhues wrote:
> > This patch restores the environment for mode=execute. Unfortunately,
> > it also means more overhead for every libtool invocation. :-(
> > (At least no fork&exec.)
>
> Negligible time overhead.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Christopher Hulbert on 2/22/2006 5:56 AM:
>
> Actually it seems the problem is that a unix-style path is passed to
> lib as the library name. This is probably not the correct fix, but
> what I did was add the following to the func_extract
On 2/24/06, Eric Blake <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> According to Christopher Hulbert on 2/22/2006 5:56 AM:
> >
> > Actually it seems the problem is that a unix-style path is passed to
> > lib as the library name. This is probably not the correct f
On 2/18/06, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> Hi Christopher,
>
> * Christopher Hulbert wrote on Wed, Feb 15, 2006 at 04:08:33PM CET:
> > The attached patch fixes the empty wl variable and the MS toolchain
> > assumption of -link -dll.
>
> The patch is ok, could you be bothered to run th
