This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [JAVA] /bin/sh portability issues in gen-classlist.sh.in
- From: Eric Botcazou <ebotcazou at libertysurf dot fr>
- To: Roger Sayle <roger at eyesopen dot com>
- Cc: gcc-patches at gcc dot gnu dot org, java-patches at gcc dot gnu dot org
- Date: Fri, 7 Jul 2006 15:49:21 +0200
- Subject: Re: [JAVA] /bin/sh portability issues in gen-classlist.sh.in
- References: <Pine.LNX.4.44.0607070644550.14880-100000@www.eyesopen.com>
> I'm reminded that the GCC Development Mission Statement, explicitly
> states "to ensure that GCC ... works on multiple architectures and
> diverse environments". http://gcc.gnu.org/gccmission.html
Sure, GCC works just fine on Solaris with /bin/ksh.
> However, knowing that /bin/sh has been a bane of the GCC build system
> for many years, I was surprised at how easy the port was. GCC 3.4.3 built
> out of the box, and mainline three stage bootstrapped the compilers and
> built most of the runtime libraries only to fail in multilibed boehmgc
> and libjava.
On how many versions of Solaris?
> Running "what /bin/sh" on my Solaris/x86 box shows that the executable
> is dated 1st October 2005. Perhaps after nearly/over? ten years of
> brokeness SUN's code is now stable enough for GCC to meet them half
> way?
AFAIK Sun has essentially pledged to keep /bin/sh bug-compatible with earlier
releases so I wouldn't depend on that.
--
Eric Botcazou