This is the mail archive of the
mailing list for the GCC project.
Re: [JAVA] /bin/sh portability issues in scripts/check_jni_methods.sh
- From: Tom Tromey <tromey at redhat dot com>
- To: Roger Sayle <roger at eyesopen dot com>
- Cc: java-patches at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org, GNU Classpath Patches <classpath-patches at gnu dot org>
- Date: 18 Aug 2006 13:48:50 -0600
- Subject: Re: [JAVA] /bin/sh portability issues in scripts/check_jni_methods.sh
- References: <Pine.LNX.firstname.lastname@example.org>
- Reply-to: tromey at redhat dot com
>>>>> "Roger" == Roger Sayle <email@example.com> writes:
Roger> This patch, or more likely request for help, is the fourth and final
Roger> in the series to enable mainline GCC to be bootstrapped with the native
Roger> /bin/sh on Solaris/x86.
Roger> Now for the admission. This final patch, to
Roger> scripts/check_jni_methods.sh is more of a workaround (hack?)
Roger> than a solution to the portability issues. The problem is that
Roger> this shell script contains the command "set -C" which isn't
Roger> supported by Solaris' sh.
I don't think we need 'set -C' in this script. I think plenty of
other scripts run during the build create temporary files using a
similar approach. I'm just going to completely remove the 'set'.
I'll put this in classpath and svn head libjava.