From: "David Eisner" <deisner@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: gen-classlist.sh problem while building gcc 4.2.4
Date: Fri, 01 Aug 2008 14:38:00 -0000 [thread overview]
Message-ID: <5ef8ba410808010737mda3709r496a828176016d53@mail.gmail.com> (raw)
Still trying to build gcc-4.2.4 on a Solaris 9 box. During stage 3, I
run into this problem:
cannes [lib]$ make
true
top_builddir=..
top_srcdir=../../../../../../gcc-4.2.4/libjava/classpath /bin/sh
./gen-classlist.sh standard
Adding java source files from srcdir
'../../../../../../gcc-4.2.4/libjava/classpath'.
Adding java source files from VM directory
/export/data/software/cradle/build/gcc/gcc-4.2.4/libjava
Adding java source files from VM directory
/export/data/software/cradle/build/gcc/objdir/sparc-sun-solaris2.9/sparcv9/libjava
./gen-classlist.sh: test: unknown operator -ef
make: *** [genclasses] Error 1
The problem appears to be that the built-in 'test' operator in the
/bin/sh Bourne shell that ships with Solaris 9 doesn't understand the
-ef operator, though bash does:
cannes [lib]$ /bin/sh -c 'test foo -ef bar && echo same'
/bin/sh: test: unknown operator -ef
cannes [lib]$ /usr/bin/bash -c 'test foo -ef bar && echo same'
cannes [lib]$
I couldn't find this in the bug database. Should I report it?
Workaround: in gen-classlist.sh, change
if test ! "${top_builddir}" -ef
"../../../../../../gcc-4.2.4/libjava/classpath"; then
to
if /usr/bin/test ! "${top_builddir}" -ef
"../../../../../../gcc-4.2.4/libjava/classpath"; then
By the way, I'm not sure why it's even building java. I didn't
include java in the enabled languages when I ran configure. I guess
it knows best.
-David
--
David Eisner http://cradle.brokenglass.com
next reply other threads:[~2008-08-01 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 14:38 David Eisner [this message]
2008-08-02 12:30 ` Ralf Wildenhues
2008-08-06 16:52 ` David Eisner
2008-08-06 17:34 ` David Eisner
2008-08-07 3:15 ` David Eisner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5ef8ba410808010737mda3709r496a828176016d53@mail.gmail.com \
--to=deisner@gmail.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).