unknown directives

unknown directives

[Bill McEnaney]

Hi,

Here are some messages that my Sun workstation printed when it tried to
build gcc-4.2.3.  If "test" is an sh command, do I need a new version of
sh?   What's wrong?  Thanks a lot.

Bill

./gen-classlist.sh: test: unknown operator -ef
make[6]: Leaving directory
`/usr/share/src/gc/sparc-sun-solaris2.8/sparcv9/libja
va/classpath/lib'
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory
`/usr/share/src/gc/sparc-sun-solaris2.8/sparcv9/libja
va/classpath'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory
`/usr/share/src/gc/sparc-sun-solaris2.8/sparcv9/libja
va'
make[3]: *** [multi-do] Error 1
make[3]: Leaving directory `/usr/share/src/gc/sparc-sun-solaris2.8/libjava'
make[2]: *** [all-multi] Error 2
make[2]: Leaving directory `/usr/share/src/gc/sparc-sun-solaris2.8/libjava'
make[1]: *** [all-target-libjava] Error 2
make[1]: Leaving directory `/usr/share/src/gc'
make: *** [all] Error 2



________________________________________________________________
Please visit a saintly hero:
http://www.jakemoore.org

And a boy with a wonderful wish:
http://shaneswish.com/

Re: unknown directives

[Ian Lance Taylor]

"Bill McEnaney" <bill@rkirkpat.net> writes:

> Here are some messages that my Sun workstation printed when it tried to
> build gcc-4.2.3.  If "test" is an sh command, do I need a new version of
> sh?   What's wrong?  Thanks a lot.

It's a portability bug.  The script was using the nonportable -ef
option to test.  This has been fixed in gcc 4.3.

The fix seems to be to change this line in
libjava/classpath/lib/gen-classlist.sh.in:

if test ! "${top_builddir}" -ef "@top_srcdir@"; then

to this:

abs_top_builddir=`cd "${top_builddir}"; pwd`
abs_top_srcdir=`cd "@top_srcdir@"; pwd`
if test "$abs_top_builddir" != "$abs_top_srcdir"; then

Ian

Re: unknown directives

[Bill McEnaney]

Thanks, Ian.  I've built gcc-4.2.3 and installed it.

Ian Lance Taylor wrote:

> "Bill McEnaney" <bill@rkirkpat.net> writes:
> 
> > Here are some messages that my Sun workstation printed when it tried to
> > build gcc-4.2.3.  If "test" is an sh command, do I need a new version of
> > sh?   What's wrong?  Thanks a lot.
> 
> It's a portability bug.  The script was using the nonportable -ef
> option to test.  This has been fixed in gcc 4.3.
> 
> The fix seems to be to change this line in
> libjava/classpath/lib/gen-classlist.sh.in:
> 
> if test ! "${top_builddir}" -ef "@top_srcdir@"; then
> 
> to this:
> 
> abs_top_builddir=`cd "${top_builddir}"; pwd`
> abs_top_srcdir=`cd "@top_srcdir@"; pwd`
> if test "$abs_top_builddir" != "$abs_top_srcdir"; then
> 
> Ian
> 
> 

________________________________________________________________
Please visit a saintly hero:
http://www.jakemoore.org

And a boy with a wonderful wish:
http://shaneswish.com/