public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/40699] [4.5 Regression] All sparcv9 libjava execution tests fail on Solaris 11/SPARC Date: Sat, 11 Jul 2009 06:44:00 -0000 [thread overview] Message-ID: <20090711064413.25031.qmail@sourceware.org> (raw) In-Reply-To: <bug-40699-279@http.gcc.gnu.org/bugzilla/> ------- Comment #7 from rsandifo at gcc dot gnu dot org 2009-07-11 06:44 ------- "ro at techfak dot uni-bielefeld dot de" <gcc-bugzilla@gcc.gnu.org> writes: > Unfortunately, the same thing happens when I invoke runtest manually in the > 20090522 tree where the 64-bit tests still worked correctly. Ah! Thanks, that explains it. So the --print-multi-lib command failed before the patch too, but adding the directories for all multilibs masked this problem. (I was wrongly assuming it was the --print-multi-lib invocation itself that I'd broken.) > What I find, though, are two different invocations of gcj (found with truss): > > * one like this > > /vol/gccsrc/obj/gcc-4.5.0-20090522/11-gcc/gcc/gcj > -B/vol/gccsrc/obj/gcc-4.5.0-20090522/11-gcc/gcc/ > -B/vol/gccsrc/obj/gcc-4.5.0-20090522/11-gcc/sparc-sun-solaris2.11/libjava/testsuite/../ > -v > > which finds libgcj.spec, and > > * another one like this > > /vol/gccsrc/obj/gcc-4.5.0-20090522/11-gcc/gcc/gcj > -B/vol/gccsrc/obj/gcc-4.5.0-20090522/11-gcc/gcc/ --encoding=UTF-8 -m64 > --print-multi-directory > > which doesn't (and lacks the second -B above, since libgcj.spec is only > located in the libjava tree). > > Maybe this helps to get this resolved? It does, thanks. I agree that the missing -B option is the problem here. However, the patch has already called a lot of fallout, so the best thing seemed to be to revert it. Thanks a lot for the help though: it shows what needs to be fixed if I or someone else comes back to this at a later date. -- rsandifo at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40699
prev parent reply other threads:[~2009-07-11 6:44 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-07-09 17:46 [Bug testsuite/40699] New: " ro at gcc dot gnu dot org 2009-07-09 18:08 ` [Bug testsuite/40699] " ro at gcc dot gnu dot org 2009-07-09 19:12 ` rsandifo at gcc dot gnu dot org 2009-07-09 19:17 ` ro at techfak dot uni-bielefeld dot de 2009-07-09 19:23 ` rsandifo at gcc dot gnu dot org 2009-07-09 20:18 ` ro at techfak dot uni-bielefeld dot de 2009-07-11 6:11 ` rsandifo at gcc dot gnu dot org 2009-07-11 6:44 ` rsandifo at gcc dot gnu dot org [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=20090711064413.25031.qmail@sourceware.org \ --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).