From: Andreas Jaeger <aj@suse.de>
To: tromey@redhat.com
Cc: GCJ Hackers <java@gcc.gnu.org>, GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: Big Classpath Merge warning
Date: Sat, 16 Jul 2005 15:56:00 -0000 [thread overview]
Message-ID: <m3ek9yn3rk.fsf@gromit.moeb> (raw)
In-Reply-To: <m3oe95mayu.fsf@localhost.localdomain> (Tom Tromey's message of "14 Jul 2005 13:41:45 -0600")
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
I know have a problem building gcc mainline with a parallel build on Linux/x86-64:
/usr/include/java/net/URL.h:25: error: global qualification of class name is inva
lid before ':' token
/usr/include/java/security/ProtectionDomain.h:24: error: global qualification of
class name is invalid before ':' token
make[5]: *** [gij.lo] Error 1
Are there some missing dependendencies? Running a normal make in
libjava seems to work.
Btw. I now see a lot of these:
mkdir gnu/java/rmi/ > /dev/null 2>&1
make[3]: [gnu/java/rmi/server.lo] Error 1 (ignored)
This is rather unfortunate, it makes it difficult to grep for errors.
Can't we use something like?
@test -z gnu/java/rmi || mkdir gnu/java/rmi
Andreas
--
Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj
SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2005-07-16 15:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 19:45 Tom Tromey
2005-07-16 15:56 ` Andreas Jaeger [this message]
2005-07-16 16:28 ` Andreas Schwab
2005-07-16 17:40 ` Andreas Schwab
2005-07-17 10:14 ` Andreas Jaeger
2005-07-18 17:44 ` Tom Tromey
2005-07-18 19:01 ` Andreas Jaeger
2005-07-17 14:10 ` Thorsten Glaser
2005-07-18 15:26 ` Bryce McKinlay
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=m3ek9yn3rk.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=java@gcc.gnu.org \
--cc=tromey@redhat.com \
/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).