[Top][All Lists]

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

Re: libtool 1.5.10 fails nopic test on Solaris

From: Ralf Menzel
Subject: Re: libtool 1.5.10 fails nopic test on Solaris
Date: Mon, 20 Dec 2004 18:39:11 +0100
User-agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Reasonable Discussion, usg-unix-v)

Ralf Wildenhues <address@hidden> writes:
> I guess, the shell's `read' does not understand `-r'.  Can you confirm
> this?  Does your shell documentation match this?

Here is the relevant section of the man page for the Solaris 9 sh:

--- snip ---
     read name ...
           One line is read from the standard  input  and,  using
           the  internal  field separator, IFS (normally space or
           tab), to delimit word boundaries, the  first  word  is
           assigned  to  the  first  name, the second word to the
           second  name,  and  so  forth,  with  leftover   words
           assigned  to  the  last  name.  Lines can be continued
           using \newline. Characters other than newline  can  be
           quoted  by  preceding  them  with  a  backslash. These
           backslashes are removed before words are  assigned  to
           names,  and no interpretation is done on the character
           that follows the backslash.  The  return  code  is  0,
           unless an EOF is encountered.
--- snip ---

So: yes, no '-r' option for the read command of /bin/sh.

> Please try the patch
> in attachment #1 (against branch-1-5; branch-2-0 should be similar, but
> against config/ltmain.m4sh).  I don't think we need -r here.

Good, this seems to fix the problem:

--- snip ---
$ make check TESTS='func_extract_archives.test'
PASS: func_extract_archives.test
All 1 tests passed
--- snip ---

> [ regarding quote.test failure ]
> | = trying: \\ quoting
> | = failed:  gcc -c "-DVAR=       est\" foo.c  -fPIC -DPIC -o .libs/foo.o
> |  gcc -c "-DVAR= est\" foo.c -o foo.o >/dev/null 2>&1
> This is the "$echo computed for the wrong shell" bug for which I have
> yet to contemplate a bug.

Or - even better - a fix?

> Try again with
>   CONFIG_SHELL=$FOO $FOO configure [...]
> with $FOO the shell that configure would've chosen.

OK, I tried (for branch-1-5)

$ CONFIG_SHELL=/bin/sh /bin/sh ./configure
$ make
$ make check TESTS='quote.test'

which gave me

--- snip ---
PASS: quote.test
All 1 tests passed
$ ./libtool --config | grep echo=
$ sed 1q libtool
#! /bin/sh
--- snip ---

Ralf Menzel

reply via email to

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