public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "jojelino at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/51498] make dejagnu work in libjava testsuite with cross-build
Date: Wed, 22 Aug 2012 17:05:00 -0000 [thread overview]
Message-ID: <bug-51498-8172-kpRBFNjFmB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51498-8172@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51498
gee <jojelino at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution| |WONTFIX
--- Comment #11 from gee <jojelino at gmail dot com> 2012-08-22 17:04:43 UTC ---
(In reply to comment #8)
> Oh, and why is this a regression?
dejagnu failed to detect the built gcj compiler in canadian cross. and
dejagnu.am of automake is responsible for not exporting makefile variables CC,
CXX, GCJ,... etc to shell. so the cause is not gcc. and this bug isn't
applicable to gcc bugzilla.
so i'm closing the bug.
prev parent reply other threads:[~2012-08-22 17:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-10 17:54 [Bug libgcj/51498] New: [4.7 regression] temporary hack to make dejagnu work in libjava jojelino at gmail dot com
2011-12-12 10:13 ` [Bug libgcj/51498] " rguenth at gcc dot gnu.org
2011-12-12 10:41 ` jojelino at gmail dot com
2011-12-12 11:22 ` rguenth at gcc dot gnu.org
2011-12-13 8:36 ` jakub at gcc dot gnu.org
2011-12-13 10:49 ` jojelino at gmail dot com
2011-12-15 12:42 ` jakub at gcc dot gnu.org
2011-12-15 13:01 ` jojelino at gmail dot com
2012-01-04 13:41 ` rguenth at gcc dot gnu.org
2012-01-16 3:31 ` [Bug libgcj/51498] make dejagnu work in libjava testsuite with cross-build jojelino at gmail dot com
2012-03-22 9:25 ` rguenth at gcc dot gnu.org
2012-07-02 13:09 ` rguenth at gcc dot gnu.org
2012-08-22 17:05 ` jojelino at gmail dot com [this message]
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=bug-51498-8172-kpRBFNjFmB@http.gcc.gnu.org/bugzilla/ \
--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).