public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "r dot emrich at de dot tecosim dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/30071] make install fails for libjava
Date: Tue, 17 Apr 2007 06:54:00 -0000 [thread overview]
Message-ID: <20070417065405.9043.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30071-11564@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from r dot emrich at de dot tecosim dot com 2007-04-17 07:54 -------
Created an attachment (id=13377)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13377&action=view)
Patch
Proposed patch. I added a new target (install-exec-am) to Makefile.am to
enforce the right installation sequence.
Tested on hppa2.0w-hp-hpux11.00 and i686-pc-linux-gnu.
I hope somebody is able to verify and submit the patch.
In general there is the question, if we need a regular testing of 'make
install, to detect these kind of problems, which only give warnings on linux
but prevend successful installation on different targets.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30071
next prev parent reply other threads:[~2007-04-17 6:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 9:18 [Bug libgcj/30071] New: " r dot emrich at de dot tecosim dot com
2007-01-29 20:00 ` [Bug libgcj/30071] " tromey at gcc dot gnu dot org
2007-01-30 8:55 ` r dot emrich at de dot tecosim dot com
2007-02-19 16:16 ` r dot emrich at de dot tecosim dot com
2007-04-17 6:54 ` r dot emrich at de dot tecosim dot com [this message]
2007-07-27 20:11 ` tromey at gcc dot gnu dot org
2007-07-29 21:24 ` andreast at gcc dot gnu dot org
2008-02-03 20:54 ` andreast at gcc dot gnu dot org
2008-02-03 20:56 ` andreast at gcc dot gnu dot org
2008-02-06 20:46 ` andreast at gcc dot gnu dot org
2008-02-06 20:46 ` andreast at gcc dot gnu dot org
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=20070417065405.9043.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).