public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug java/48512] [4.6] gcj spec files references incorrectly crtmt.o on i686-w64-mingw32 target Date: Thu, 02 Feb 2012 18:38:00 -0000 [thread overview] Message-ID: <bug-48512-8172-7drA67o4Sa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48512-8172@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48512 Kai Tietz <ktietz at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2012-02-02 CC| |ktietz at gcc dot gnu.org Ever Confirmed|0 |1 --- Comment #1 from Kai Tietz <ktietz at gcc dot gnu.org> 2012-02-02 18:37:41 UTC --- Confirmed. Following patch should solve this Index: gcc/libjava/configure.ac =================================================================== --- gcc.orig/libjava/configure.ac +++ gcc/libjava/configure.ac @@ -1150,8 +1150,13 @@ case "$THREADS" in # FIXME: In Java we are able to detect thread death at the end of # Thread.run() so we should be able to clean up the exception handling # contexts ourselves. - THREADSTARTFILESPEC='crtmt%O%s' - ;; + case "$host" in + *-w64-mingw*) + ;; + *) + THREADSTARTFILESPEC='crtmt%O%s' + ;; + esac none) THREADH=no-threads.h
next prev parent reply other threads:[~2012-02-02 18:38 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-08 8:17 [Bug java/48512] New: " blakawk at gentooist dot com 2012-02-02 18:38 ` ktietz at gcc dot gnu.org [this message] 2012-02-03 9:43 ` [Bug java/48512] " ktietz at gcc dot gnu.org 2012-02-03 10:35 ` ktietz at gcc dot gnu.org 2012-02-03 10:36 ` ktietz at gcc dot gnu.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=bug-48512-8172-7drA67o4Sa@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: 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).