Re: python support in CVS.

[Scott Klement <klemscot@xxxxxxxxxxxx>]

On 27 Nov 2000, Carey Evans wrote:

> Michael Madore <mmadore@turbolinux.com> writes:
> 
> > In my experience, ash is really not sufficiently bash compatible to use
> > automake/autoconf/libtool.
> 
> Autoconf is supposed to work on every Unix system out there, including
> FreeBSD, which uses ash, as well as others with their own POSIX
> compatible shells like SunOS 4, AIX, Solaris and Unixware.  I've never
> had trouble using ash with autoconf, etc. before.

Hmmm...  I seem to have missed part of this thread...  

I run automake/autoconf/libtool on FreeBSD (which is the main OS I use)
all the time, never had a problem.

I can't say that I've ever heard of "ash", though.  FreeBSD comes with
sh, csh and tcsh in the base os.  You can install bash, ksh, zsh, etc
if you like as a package.  I personally prefer tcsh to bash, anyway :)
But I've never heard of ash...

> 
> In my (limited) experience, you'll find bash used as /bin/sh on most
> Linux systems, but not much else.  Admittedly, pdksh and zsh both
> manage the `... <<EOF` properly; but I don't see it used in any of the
> other autoconf macros installed on my system.
> 
> -- 
>        Carey Evans  http://home.clear.net.nz/pages/c.evans/

True, /bin/sh is not bash on FreeBSD.   However, I wasn't having the
problem that Carey was describing....

Seems silly to me that you would assume /bin/sh to be bash... if you need
bash, refer to it as "bash" not "sh". :)


+---
| This is the LINUX5250 Mailing List!
| To submit a new message, send your mail to LINUX5250@midrange.com.
| To subscribe to this list send email to LINUX5250-SUB@midrange.com.
| To unsubscribe from this list send email to LINUX5250-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---