[Top][All Lists]

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

Tru64/OSF: BIN_SH revisited

From: Ralf Wildenhues
Subject: Tru64/OSF: BIN_SH revisited
Date: Thu, 16 Mar 2006 22:02:08 +0100
User-agent: Mutt/1.5.9i

This started out here and here:
and led to (CVS) Autoconf exporting BIN_SH=xpg4 (don't be fooled by the
patches posted; they do not fully reflect what was committed :-/ ).

Given a package using CVS Autoconf and (1.5.x or HEAD) Libtool.  On OSF,
the configure script will restart itself with /bin/sh, but with
BIN_SH=xpg4 in the environment.  So 'sh' starts the posix shell,
/usr/bin/posix/sh[1].  There is no good `echo' on the system, but that
posix shell understands `print -r', so this is what $ECHO gets set to in

But then building fails: `libtool' is executed but not with $BIN_SH set
in its environment, so the Bourne shell is invoked, which does not know
`print'.  The next time config.status is started by `make', BIN_SH won't
be set beforehand either, so it will barf heavily, too.

I see several ways out of this:

0a) Revert the change to set BIN_SH in Autoconf, in order to be

0b) Additionally, prepend /usr/bin/posix/ to the path walk of
_AS_DETECT_BETTER_SHELL, to choose the right shell right away, inside

1) Always restart with BIN_SH set in both config.status and libtool.

2) Document that the user please do
    BIN_SH=xpg4; export BIN_SH

in his environment (or set CONFIG_SHELL).  Not so nice, but possible.

3) Get the right shell, but only in Libtool:
We could try to choose /usr/bin/posix/sh before testing whether `print
-r' works.  That we this gets us the right shell, sets SHELL accordingly
in Makefile, and thus all should be well.

The first patch below does (0b), the second (3).  I'm tending toward
(0b), unsure whether to add (0a) for good measure.  What do you think?

Note HP-UX and AIX also have /usr/bin/posix/sh.  With (0b), we still
choose /bin/sh on AIX; and /usr/bin/posix/sh on HP-UX 10.20, which seems
ok.  Did I forget any relevant systems[1]?

It should be noted that so far, no stable Autoconf release exists which
forces Libtool to support this issue; it would thus be good to be fixed
before the release.

Please note that the Posix shell understands `print -r -' as well; but
since the separator is an orthogonal issue, I don't want to attack it in
Libtool ATM.


[1] To see what /usr/bin/posix/sh is on some systems:

        * lib/m4sugar/m4sh.m4 (_AS_DETECT_BETTER_SHELL): Prepend
        the directory `/usr/bin/posix' in the shell search, to prefer
        the Posix shell not only in subsequent spawns as with `$BIN_SH'
        on Tru64.

Index: lib/m4sugar/m4sh.m4
RCS file: /cvsroot/autoconf/autoconf/lib/m4sugar/m4sh.m4,v
retrieving revision 1.162
diff -u -r1.162 m4sh.m4
--- lib/m4sugar/m4sh.m4 16 Mar 2006 13:33:18 -0000      1.162
+++ lib/m4sugar/m4sh.m4 16 Mar 2006 21:00:53 -0000
@@ -226,7 +226,7 @@
         _AS_RUN([_AS_DETECT_SUGGESTED_BODY]) 2> /dev/null],
       [case $as_dir in
           for as_base in sh bash ksh sh5; do

        * libltdl/m4/libtool.m4 (_LT_PROG_ECHO_BACKSLASH): If we could
        not find a working `echo' program, try whether /usr/bin/posix/sh
        exists before trying `print -r'; /usr/bin/posix/sh gets us the
        Posix shell whether or not BIN_SH was set before.  Allows to
        build libtool on OSF.

Index: libltdl/m4/libtool.m4
RCS file: /cvsroot/libtool/libtool/libltdl/m4/libtool.m4,v
retrieving revision 1.60
diff -u -r1.60 libtool.m4
--- libltdl/m4/libtool.m4       9 Feb 2006 16:04:01 -0000       1.60
+++ libltdl/m4/libtool.m4       16 Mar 2006 21:00:45 -0000
@@ -997,7 +997,18 @@
     if test "X$ECHO" = Xecho; then
       # We didn't find a better echo, so look for alternatives.
-      if test "X`{ print -r '\t'; } 2>/dev/null`" = 'X\t' &&
+      # We have to test Tru64 /usr/bin/posix/sh before testing
+      # `print -r', because a restart with BIN_SH=xpg4 would have
+      # given us this shell, but we then need this reflected in $SHELL.
+      if test -f /usr/bin/posix/sh &&
+       test "X$CONFIG_SHELL" != X/usr/bin/posix/sh; then
+        # If we have posix/sh, try running configure again with it.
+        CONFIG_SHELL=/usr/bin/posix/sh
+        export CONFIG_SHELL
+        exec $CONFIG_SHELL "[$]0" --no-reexec ${1+"[$]@"}
+      elif test "X`{ print -r '\t'; } 2>/dev/null`" = 'X\t' &&
          echo_testing_string=`{ print -r "$echo_test_string"; } 2>/dev/null` &&
          test "X$echo_testing_string" = "X$echo_test_string"; then
         # This shell has a builtin print -r that does the trick.

reply via email to

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