On Fri, Dec 14, 2007 at 01:59:34AM +0000, Colin Watson wrote:
> libtool used it. The _LT_CHECK_SHELL_FEATURES macro checks a number of
> shell features and determines accurately that the currently-running
> shell supports +=. Unfortunately, the currently-running shell is bash at
> this point, not dash. The reason for this is that configure has
> different logic for re-execing itself under a different shell from that
> used by libtool. libtool seems to try to account for this using:
>
> : ${SHELL="${CONFIG_SHELL-/bin/sh}"}
>
> ... but at this point CONFIG_SHELL is not set, and so libtool ends up
> running under a different shell than the one that configure
> feature-tested.
>
> I've had this mail postponed for several days in the hope of finding
> time to dig into this further, but I haven't found such time and I think
> it's better to send an incomplete report than none at all. Please let me
> know if there's anything you'd like me to investigate further.
It looks as though I filed
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=447022
and then completely forgot about it.
I suppose the easiest workaround is to explicitly set CONFIG_SHELL
since I don't particularly want to regress to libtool 1.5.
_______________________________________________
Bug-libtool mailing list
Bug-libtool@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-libtool
