GNU bug report logs - #10303
Problems in $(LIBTOOL) definition: wrong shell used

Previous Next

Full log

Message #12 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Marko Lindqvist <cazfi74 <at> gmail.com>
To: Stefano Lattarini <stefano.lattarini <at> gmail.com>
Cc: 10301 <at> debbugs.gnu.org, bug-libtool <at> gnu.org
Subject: Re: Problems in $(LIBTOOL) deifnition (was: Re: automake bug#10301:
	/bin/sh used to execute libtool)
Date: Thu, 15 Dec 2011 12:54:02 +0200

[Message part 1 (text/plain, inline)]

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.


 - ML

[libtool_bash.diff (text/x-patch, attachment)]

Previous Next

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