[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: libtool-2.2.10: print vs. printf

From: Markus Duft
Subject: Re: libtool-2.2.10: print vs. printf
Date: Thu, 28 Oct 2010 10:42:46 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20100913 Lightning/1.0b3pre Thunderbird/3.1.3

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).

otherwise, thanks for the docs ;)


> Thanks,
> Ralf
>     docs: mention shell requirement for libtool script.
>     * doc/libtool.texi (Invoking libtool): Document that the shell
>     used to invoke libtool needs to be the same used to configure
>     it.
>     * THANKS: Update.
>     Report by Markus Duft.
> diff --git a/doc/libtool.texi b/doc/libtool.texi
> index 076b67b..c84b92a 100644
> --- a/doc/libtool.texi
> +++ b/doc/libtool.texi
> @@ -1326,6 +1326,12 @@ can be achieved using either option @option{-v} or 
> option
>  Print libtool version information and exit.
>  @end table
> +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 @var{mode-args} are a variable number of arguments, depending on the
>  selected operation mode.  In general, each @var{mode-arg} is interpreted
>  by programs libtool invokes, rather than libtool itself.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]