[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: |
Tue, 7 Jun 2005 12:10:47 +0200 |
User-agent: |
Mutt/1.5.8i |
On Sun, Jun 05, 2005 at 07:38:59PM +0200, Ralf Wildenhues wrote:
> * Nicolas Joly wrote on Thu, Jun 02, 2005 at 09:00:16PM CEST:
> > On Thu, Jun 02, 2005 at 10:37:27AM +0200, Ralf Wildenhues wrote:
> > > * Nicolas Joly wrote on Thu, Jun 02, 2005 at 01:02:32AM CEST:
> > > > On Wed, May 25, 2005 at 06:22:37PM +0200, Ralf Wildenhues wrote:
> > > > >
> > > > > OK to apply this patch to branch-2-0 and HEAD, and then backport to
> > > > > branch-1-5?
>
> > Ok, with the patch applied, both libtool-1.5.18 and branch-1-5 are
> > fine: All 112 tests passed.
>
> Applied the first patch below to HEAD, branch-2-0, the second to
> branch-1-5.
Thanks a lot.
> > > > Unfortunately, i was unable to bootstrap libtool HEAD on my Tru64 unix
> > > > workstation. Next step was to bootstrap it on another machine
> > > > (NetBSD/amd64); back to the Tru64 machine ... another failure.
> > >
> > > that just helped us find more HEAD bug(s). :-/
> > >
> > > First, could you post the exact output of `bootstrap' on Tru64?
> >
> > I must have done something weird; `./boostrap' now works ... and
> > `./configure' too. But print problems arise with the make command :
>
> Since this is not fixed yet, here's at least a workaround: specify
> either one (or both) of CONFIG_SHELL and ECHO resp. lt_ECHO (branch-1-5
> resp. branch-2-0/HEAD) while configuring. CONFIG_SHELL needs to be done
> like so:
>
> CONFIG_SHELL=/bin/foosh /bin/foosh path/to/configure [OPTIONS..]
>
> and you should provide an echo which does not interpret backslashes
> (one of `echo', `/bin/echo', `print -r', `printf %s\\n' should usually
> do).
In the mean time, i tested the solution where `print -r' and `ksh'
tests are swapped (attached patch). It seems to go a little further
(no more `print' error messages), but seems to fail in another ksh
problem/bug :
[...]
libtool: compile: cc "-DHAVE_CONFIG_H=<config.h>" -DLTDL -I. -I. -I.. -I. -I.
-I./libltdl -g -c -MD loaders/dlopen.c -o dlopen.o >/dev/null 2>&1
/bin/ksh ../libtool --tag=CC --mode=link cc -g -module -avoid-version -o
dlopen.la dlopen.lo
../libtool[24]: invalid multibyte character
../libtool[6]: invalid multibyte character
../libtool[2312]: invalid multibyte character
libtool: link: invalid operation mode `link'
libtool: link: Try `libtool --help --mode=link' for more information.
../libtool[7679]: invalid multibyte character
../libtool[7679]: invalid multibyte character
../libtool[7679]: invalid multibyte character
[...]
../libtool[7679]: invalid multibyte character
../libtool[7679]: invalid multibyte character
gmake[3]: *** [dlopen.la] Segmentation fault
gmake[3]: Leaving directory `/home/njoly/temp/libtool/libltdl'
gmake[2]: *** [all] Error 2
--
Nicolas Joly
Biological Software and Databanks.
Institut Pasteur, Paris.
- Re: ksh bug on Tru64 UNIX causes current libtool failure, Nicolas Joly, 2005/06/01
- Re: ksh bug on Tru64 UNIX causes current libtool failure, Nicolas Joly, 2005/06/02
- FYI: ksh bug on Tru64 UNIX causes current libtool failure, Ralf Wildenhues, 2005/06/05
- Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure,
Nicolas Joly <=
- Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure, Ralf Wildenhues, 2005/06/07
- Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure, Nicolas Joly, 2005/06/07
- Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure, Ralf Wildenhues, 2005/06/07
- Re: FYI: ksh bug on Tru64 UNIX causes current libtool failure, Nicolas Joly, 2005/06/07