[Top][All Lists]

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

Re: Running ./config.status

From: Noah Misch
Subject: Re: Running ./config.status
Date: Fri, 4 Feb 2005 06:32:01 -0800
User-agent: Mutt/1.5.6i

On Fri, Feb 04, 2005 at 02:49:29PM +0100, Ralf Corsepius wrote:
> On Fri, 2005-02-04 at 05:10 -0800, Noah Misch wrote:
> > If you believe `man perlrun', some systems do not respect #! and start all
> > scripts under csh.
> I assume, the systems they refer to, actually are victim to the length
> limitations some systems impose on "!# " lines.

These appear to be two distinct issues.  The document does talk about systems
truncating the #! line, but it discusses separately (in the documentation for
`-S') systems that always run scripts with csh.  As a solution, it quotes a
fragment of sh and csh and Perl code that re-executes the script under Perl.

> >   $(SHELL) ./script defends against that.
> Theoretically, the "#!" limitations also could hit autoconf scripts,
> esp. if autoconf is heading towards choosing "suitable shells on $PATH"
> instead of using standard shells. 
> So adding $(SHELL) might not be wrong.

Good point.  I suspect more systems still in use truncate #! than execute
scripts by running them through csh.

reply via email to

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