public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "brian at dessent dot net" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/38438] build error in x86_64-unknown-linux-gnu/32/libjava
Date: Sun, 07 Dec 2008 22:48:00 -0000 [thread overview]
Message-ID: <20081207224832.23906.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38438-3511@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from brian at dessent dot net 2008-12-07 22:48 -------
Subject: Re: New: build error in
x86_64-unknown-linux-gnu/32/libjava
It looks like somehow a rule is being run that isn't intended to ever
actually be built. In libjava/Makefile.am there are these dummy rules
copied and pasted for all the various tools.
## This is a dummy definition.
grmiregistry_SOURCES =
grmiregistry_LDFLAGS = --main=gnu.classpath.tools.rmiregistry.Main \
-rpath $(toolexeclibdir) -shared-libgcc $(THREADLDFLAGS)
$(extra_ldflags)
grmiregistry_LINK = $(GCJLINK)
## See jv_convert_LDADD.
grmiregistry_LDADD = -L$(here)/.libs libgcj-tools.la
grmiregistry_DEPENDENCIES = libgcj-tools.la
Note that the _SOURCES is empty, which is why the link fails I guess.
But these rules aren't supposed to be run as far as I can tell, because
instead the binary .class files are checked into the tree and there are
wrapper scripts that invoke the JVM with them. See
libjava/classpath/tools/*.in. These wrappers should all have been
created at the end of the classpath configure script execution. Are
those wrappers not created for you?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38438
next prev parent reply other threads:[~2008-12-07 22:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-07 21:01 [Bug libgcj/38438] New: " felix-gcc at fefe dot de
2008-12-07 21:46 ` [Bug libgcj/38438] " felix-gcc at fefe dot de
2008-12-07 22:48 ` brian at dessent dot net [this message]
2008-12-07 23:38 ` felix-gcc at fefe dot de
2008-12-08 0:17 ` felix-gcc at fefe dot de
2008-12-08 0:30 ` brian at dessent dot net
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=20081207224832.23906.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=java-prs@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).