[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: libtool-2.2.10: print vs. printf
From: |
Ralf Wildenhues |
Subject: |
Re: libtool-2.2.10: print vs. printf |
Date: |
Sat, 30 Oct 2010 09:28:00 +0200 |
User-agent: |
Mutt/1.5.20 (2010-08-04) |
[ dropping libtool@ ]
Hi Markus,
* Markus Duft wrote on Thu, Oct 28, 2010 at 10:42:46AM CEST:
> On 10/27/2010 08:13 PM, Ralf Wildenhues wrote:
> >> oh, well - good to know that ;) is there some documentation i can
> >> refer to wrt to this requirement? it seems we need to adapt some
> >> things, as this was not the case with previous versions - and i
> >> need to argue the need to do the work ;)
> >
> > Good point actually. We don't currently have such documentation.
> > The Autoconf manual has some bits on $CONFIG_SHELL, but nothing
> > about the libtool script of course.
> >
> > OK to fix that with the patch below, and add Markus to THANKS?
>
> i'd additionally mention, that a shell mismatch can make libtool fail,
> because of the print/printf mismatch. this is (AFAICT) the only thing
> that really _breaks_ when the configure shell was a ksh, and the make
> shell is a bash (at least for me).
No, that is not the only thing that breaks. Actually, for example on
Solaris, *lots* of other things will break as well. And we don't really
guarantee what breaks on what system and with which combination of
shells. So let me make the statement a wee bit stronger by squashing in
this diff. Hope that is enough.
I've pushed the combined patch now, since there were no more comments.
Thanks,
Ralf
--- a/doc/libtool.texi
+++ b/doc/libtool.texi
@@ -1330,7 +1330,8 @@ The current @command{libtool} implementation is done with
a shell script
that needs to be invoked by the shell which @command{configure} chose for
configuring @command{libtool} (@pxref{config.status Invocation, , The
Autoconf Manual, autoconf, The Autoconf Manual}). This shell is set in
-the she-bang (@samp{#!}) line of the @command{libtool} script.
+the she-bang (@samp{#!}) line of the @command{libtool} script. Using a
+different shell may cause undefined behavior.
The @var{mode-args} are a variable number of arguments, depending on the
selected operation mode. In general, each @var{mode-arg} is interpreted