[Top][All Lists]

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

Re: reexec and M4sh (Was: bison-1.29c 'configure' problems on Solaris 8)

From: Raja R Harinath
Subject: Re: reexec and M4sh (Was: bison-1.29c 'configure' problems on Solaris 8)
Date: Fri, 05 Oct 2001 08:38:36 -0500
User-agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.0.105


Paul Eggert <address@hidden> writes:
> Unfortunately it's not.  It fails on Solaris 8, with similar symptoms.
> $ sh configure
> configure: test: argument expected
> $ sh -x configure
> + test -n  
> + test -n  
> + echo configure 
> + sed s,\(.*[\/]\+\)\?\([^\/]\+\)[\/]*,\2, 
> as_me=configure
> as_lineno_1=
> as_lineno_2=
> as_lineno_3=
> + test x = x 

No problem so far.  $LINENO detection is working.

> as_save_IFS=  
> IFS=
> IFS=  

I see why this fails: IFS is set to $PATH_SEPARATOR, which hasn't been
initialized at this point.  So, _AS_PATH_WALK can't actually find
'configure' on the path.

I have always been invoking 'configure' as ../../configure.  I hadn't
tested this case.

> + test ! -f 
> configure: test: argument expected

The 'test ! -f $as_myself' isn't safe.

Actually, with this usage (sh configure), _AS_PATH_WALK would find
'configure' only if PATH contains '.'.

We could fix the 'test ! -f' above, and let the script error out.  So,
you won't be able to 'sh configure', but you could 'sh ./configure'.

More desirably, we shouldn't try to support invoking 'configure' from
the PATH, and assume that a bareword in $0 is just a script in the
current directory.

- Hari
Raja R Harinath ------------------------------ address@hidden
"When all else fails, read the instructions."      -- Cahn's Axiom
"Our policy is, when in doubt, do the right thing."   -- Roy L Ash

reply via email to

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