This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Documenting tools necessary for GCC [draft]
- From: Zack Weinberg <zack at codesourcery dot com>
- To: obrien at FreeBSD dot org
- Cc: gcc at gcc dot gnu dot org
- Date: Sun, 01 Jun 2003 13:39:25 -0700
- Subject: Re: Documenting tools necessary for GCC [draft]
- References: <200305291727.NAA06347@caip.rutgers.edu><20030530171122.GA90937@dragon.nuxi.com><87llwmi8jb.fsf@egil.codesourcery.com><20030601203640.GA79431@dragon.nuxi.com>
"David O'Brien" <obrien@FreeBSD.org> writes:
> On Sun, Jun 01, 2003 at 12:03:36AM -0700, Zack Weinberg wrote:
>> "David O'Brien" <obrien@FreeBSD.org> writes:
>>
>> > I'd really like this to state a POSIX compliant shell, and list the exact
>> > POSIX spec (and year) that OS's must adhere to.
>>
>> Not good enough. The POSIX shell and make specifications were not
>> written with the aim of making it possible to write portable shell
>> scripts or makefiles.
>
> The I would like to have the FreeBSD /bin/sh explicitly stated as a shell
> that GCC must bootstrap using. Bash'isms & Linux'isms should be kept out
> of the bourne code. I was hoping we could simply say "POSIX shell", but
> if that won't do, then I'd like to see some shell implementations
> explicitly listed as supported.
I'd be fine with that.
zw