Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure
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='' -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=" -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: more useful installcheck
Hi Gary, * Gary V. Vaughan wrote on Fri, Oct 07, 2005 at 10:41:56AM CEST: > > Ralf Wildenhues wrote: > >OK to apply? > > Nice patch. Yes, please :-) Done. Thanks! Cheers, Ralf > >* configure.ac (abs_top_builddir, abs_top_srcdir): always > >substitute. > >* Makefile.am (BUILDCHECK_ENVIRONMENT) > >(INSTALLCHECK_ENVIRONMENT): New macros. Set _lt_pkgdatadir, > >LIBTOOL, LIBTOOLIZE accordingly, by using above, and > >program_transform_name. > >* tests/testsuite.at (TESTS_PREPARE): Do not set them anymore. > >Set $unset. > >(LT_AT_MAKE): Use to unset LIBTOOL and LIBTOOLIZE.
Re: more useful installcheck
Hallo Ralf, Ralf Wildenhues wrote: OK to apply? Nice patch. Yes, please :-) * configure.ac (abs_top_builddir, abs_top_srcdir): always substitute. * Makefile.am (BUILDCHECK_ENVIRONMENT) (INSTALLCHECK_ENVIRONMENT): New macros. Set _lt_pkgdatadir, LIBTOOL, LIBTOOLIZE accordingly, by using above, and program_transform_name. * tests/testsuite.at (TESTS_PREPARE): Do not set them anymore. Set $unset. (LT_AT_MAKE): Use to unset LIBTOOL and LIBTOOLIZE. Cheers, Gary. -- Gary V. Vaughan ())_. [EMAIL PROTECTED],gnu.org} Research Scientist ( '/ http://tkd.kicks-ass.net GNU Hacker / )= http://www.gnu.org/software/libtool Technical Author `(_~)_ http://sources.redhat.com/autobook signature.asc Description: OpenPGP digital signature
Re: Tru64 Fortran compiler support (was: FYI: ksh bug on Tru64 UNIX causes current libtool failure)
On Thu, Oct 06, 2005 at 06:27:32PM +0200, Ralf Wildenhues wrote:
> Hi Nicolas,
>
> * Nicolas Joly wrote on Thu, Oct 06, 2005 at 03:00:51PM CEST:
> > On Thu, Oct 06, 2005 at 02:27:26PM +0200, Ralf Wildenhues wrote:
> > > * Nicolas Joly wrote on Wed, Oct 05, 2005 at 03:22:10PM CEST:
> > > >
> > > > Got 3 failures; log attached.
[...]
> > > This suggests that it should be possible to write archive_cmds (and
> > > possibly archive_expsyms_cmds) in libltdl/m4/libtool.m4:_LT_LINKER_SHLIBS
> > > like a mixture of the $GCC and the non-$GCC case, using $cc_basename and
> > > $GCC as decision criteria. Would you be willing to work on this?
> >
> > I'll try, even if i'm not a fortran programmer myself.
> >
> > > Should I create a preliminary patch you could test?
> >
> > Yes, please.
>
> See below. If all the C compiler does is pass `-expect_unresolved pattern'
> through to the linker anyway, we could also just skip the `case' thingy
> and add the `${wl}' every time..
I just checked that both `-expect_unresolved \*' and
`-Wl,-expect_unresolved -Wl,\*' give the same ld(1) command line.
With your patch the 2 fortran tests now pass :
9: F77 convenience archives ok
10: FC convenience archives ok
And the testsuite looks good :
29 tests behaved as expected.
1 test was skipped.
To summarize, libtool HEAD now works on Tru64 with `BIN_SH=xpg4' set
in the environement.
--
Nicolas Joly
Biological Software and Databanks.
Institut Pasteur, Paris.
