"Bill McEnaney" <bill@xxxxxxxxxxxx> 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
