Re: Problems with libtool 2.2.2 and /bin/sh pointing to dash

[Gary V. Vaughan]

Hi Ross,

On 22 Apr 2008, at 05:39, Ross Burton wrote:
> Gary V. Vaughan <gary <at> gnu.org> writes:
> > If you are upgrading projects
> > that used this idiom to libtool 2.0 or newer, you should replace  
> > those
> > calls with direct references to the equivalent Autoconf shell  
> > variables
> > that are set by the configure time tests before being passed to
> > `config.status' for inclusion in the generated libtool script.
>
> At the moment, GTK+ does this in configure:
>
> deplibs_check_method=`(./libtool --config; echo 'eval echo
> $deplibs_check_method') | sh`
> if test "x$deplibs_check_method" '!=' xpass_all || test "x 
> $enable_static" = xyes
> ; then
> ...
>
> Am I right in thinking that the first line can be removed, as  
> initialising
> libtool will have created and set the variable "deplibs_check_method"?

Yes, exactly.  Running the expansion of LT_INIT (or AC_PROG_LIBTOOL if  
you didn't run autoupdate yet) in configure includes a call to  
_LT_CHECK_MAGIC_METHOD, which does indeed set deplibs_check_method at  
configure time.

> Was this behaviour present in libtool 1.5?

No it wasn't, because libtool was generated in a two stage process  
which required
calling ./libtool --config directly.

Cheers,
        Gary
--
  ())_.              Email me: address@hidden
  ( '/           Read my blog: http://blog.azazil.net
  / )=         ...and my book: http://sources.redhat.com/autobook
`(_~)_

PGP.sig
Description: This is a digitally signed message part