[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure
From: |
Nicolas Joly |
Subject: |
Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure |
Date: |
Fri, 7 Oct 2005 14:59:29 +0200 |
User-agent: |
Mutt/1.5.8i |
On Wed, Oct 05, 2005 at 03:22:10PM +0200, Nicolas Joly wrote:
> On Wed, Oct 05, 2005 at 10:43:40AM +0200, Ralf Wildenhues wrote:
> > Hi Nicolas,
> >
> > * Nicolas Joly wrote on Tue, Oct 04, 2005 at 03:36:48PM CEST:
> > > On Tue, Oct 04, 2005 at 12:09:26PM +0200, Ralf Wildenhues wrote:
> > > >
> > > > Should've been `lt_ECHO='printf %s\n'; export lt_ECHO'
> > > > Sorry, I believe it was me who posted that wrongly back then.
> > >
> > > I've just restarted with the correct value. configure now pass, but
> > > make aborts with:
> > >
> > > [...]
> > > source='libltdl/loaders/preopen.c'
> > > object='libltdl/loaders/libltdl_libltdl_la-preopen.lo' libtool=yes \
> > > DEPDIR=.deps depmode=tru64 /bin/sh ./libltdl/config/depcomp \
> > > /bin/sh ./libtool --tag=CC --mode=compile cc -DLTDL -DHAVE_CONFIG_H
> > > -DLT_CONFIG_H='<config.h>' -I. -I. -I. -DLTDLOPEN=libltdl -I. -I.
> > > -Ilibltdl -I./libltdl -I./libltdl/libltdl -g -c -o
> > > libltdl/loaders/libltdl_libltdl_la-preopen.lo `test -f
> > > 'libltdl/loaders/preopen.c' || echo './'`libltdl/loaders/preopen.c
> > > ./libtool: bad substitution
> > >
> > > with `set -x', in libtool script:
> > >
> > > [...]
> > > base_compile= cc -DLTDL -DHAVE_CONFIG_H "-DLT_CONFIG_H=<config.h>" -I.
> > > -I. -I. -
> > > DLTDLOPEN=libltdl -I. -I. -Ilibltdl -I./libltdl -I./libltdl/libltdl -g -c
> > > + func_stripname -Wc, -Wc,-MD
> > > func_stripname_result=-Wc,-MD
> > > ./libtool: bad substitution
> >
> > Ahh. Please add another `set -x' at the top of func_stripname to see
> > which of the parameter substitutions fail.
> >
> > Hmm, the Tru64 shell in POSIX mode documents support for ${foo#bar} and
> > ${foo%bar}. I bet there's a shell bug lingering when bar is either
> > double-quoted or bar is another parameter like `${1}'. Can you play
> > around a bit to try this? For example, pdksh fails on
> > ${1%$2}
> > but works if we do
> > arg2=$2
> > ${1%$arg2}
> > instead. Maybe
> > arg1=$1
> > arg2=$2
> > echo ${arg1%$arg2}, ${arg1%"$arg2"}
> > both work instead?
> >
> > We should then either fix func_stripname (and a couple of other ones)
> > to work around this bug or fix _LT_CHECK_XSI_SHELL to expose the bug
> > (and turn off the fast substitution functions).
>
> Will try to have a look and report.
This one is not a real problem, BIN_SH was not set and the shell was
not in POSIX mode ... normal failure.
With all my experiments, i think we need to have `BIN_SH=xpg4'
automatically defined to proceed with libtool on Tru64.
--
Nicolas Joly
Biological Software and Databanks.
Institut Pasteur, Paris.
- Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure, Nicolas Joly, 2005/10/03
- Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure, Ralf Wildenhues, 2005/10/04
- Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure, Nicolas Joly, 2005/10/04
- Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure, Ralf Wildenhues, 2005/10/05
- Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure, Nicolas Joly, 2005/10/05
- FYI: fix simple C++ link code m4 quoting (was: FYI: ksh bug on Tru64 UNIX causes current libtool failure), Ralf Wildenhues, 2005/10/05
- Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure, Ralf Wildenhues, 2005/10/06
- Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure, Nicolas Joly, 2005/10/06
- Tru64 Fortran compiler support (was: FYI: ksh bug on Tru64 UNIX causes current libtool failure), Ralf Wildenhues, 2005/10/06
- Re: Tru64 Fortran compiler support (was: FYI: ksh bug on Tru64 UNIX causes current libtool failure), Nicolas Joly, 2005/10/07
- Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure,
Nicolas Joly <=