public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcj/51498] [4.7 regression] temporary hack to make dejagnu work in libjava Date: Tue, 13 Dec 2011 08:42:00 -0000 [thread overview] Message-ID: <bug-51498-4-Jesisnuchm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51498-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51498 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-12-13 08:36:16 UTC --- None of the testsuite Makefiles for other libraries do anything similar (libgomp, libstdc++-v3, ..., so why is libjava so special that it needs it?). make check definitely works just fine for me and uses the newly built gcj etc. rather than the system gcj. So please expand on what exact errors you saw, details from the libjava.log where it shows etc.
next prev parent reply other threads:[~2011-12-13 8:36 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-10 18:14 [Bug libgcj/51498] New: " jojelino at gmail dot com 2011-12-12 10:14 ` [Bug libgcj/51498] " rguenth at gcc dot gnu.org 2011-12-12 10:42 ` jojelino at gmail dot com 2011-12-12 11:24 ` rguenth at gcc dot gnu.org 2011-12-13 8:42 ` jakub at gcc dot gnu.org [this message] 2011-12-13 11:03 ` jojelino at gmail dot com 2011-12-15 12:44 ` jakub at gcc dot gnu.org 2011-12-15 13:16 ` jojelino at gmail dot com 2012-01-04 13:40 ` rguenth at gcc dot gnu.org 2012-01-16 4:47 ` [Bug libgcj/51498] make dejagnu work in libjava testsuite with cross-build jojelino at gmail dot com 2012-03-22 9:26 ` 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
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-4-Jesisnuchm@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).