GNU bug report logs - #10301
/bin/sh used to execute libtool

Previous Next

Full log

View this message in rfc822 format

From: Stefano Lattarini <stefano.lattarini <at> gmail.com>
To: Marko Lindqvist <cazfi74 <at> gmail.com>
Cc: 10301 <at> debbugs.gnu.org
Subject: bug#10301: Problems in $(LIBTOOL) deifnition
Date: Wed, 21 Dec 2011 19:44:33 +0100

tags 10301 notabug
close 10301
thanks

Hi Marko.

Sorry for the delay, but this thread had fallen outside my radar.

On 12/15/2011 11:54 AM, Marko Lindqvist wrote:
> On 15 December 2011 11:54, Stefano Lattarini
> <stefano.lattarini <at> gmail.com> wrote:
>>>
>>> I'm cross-compiling gettext to mingw32-target in linux system. I have
>>> to regenerate build system (so it's not the one distributed with
>>> gettext 0.18.1.1). I end with libtool-script that has /bin/bash as
>>> shebang. Yet when doing the build, it's run through /bin/sh ("/bin/sh
>>> ../libtool"). This work in one of my systems where /bin/sh is bash,
>>> and fails in another where /bin/sh is dash.
>>>
>> The issue you are experiencing is probably due to the fact that the
>> automake-generated makefiles use $(LIBTOOL) to issue libtool invocations,
>> and that explicitly runs the libtool script through the shell given by
>> $(SHELL).
> 
>  Yes, everything works when libtool is built with attached patch that
> makes $(LIBTOOL) to run libtool-script directly instead of feeding it
> to (possibly wrong) shell.
> 
Thanks for the confirmation; I'm closing this bug report for what
concerns automake then (the issues should still remain open in the
libtool tracker).

Regards,
 Stefano

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.