public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug libgcj/44341] [4.6 Regression] libjava cross build fails when configured with --with-gmp= Date: Wed, 22 Dec 2010 13:23:00 -0000 [thread overview] Message-ID: <bug-44341-8172-aDa5F1TZpP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-44341-8172@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44341 --- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> 2010-12-22 13:23:22 UTC --- Another alternative would be to make the behavior different between cross and native builds. In native builds, --with-gmp{,-lib,-include} would be passed through to both gcc configury and libjava/classpath (of course, if present, --with-target-gmp* would override it for libjava/classpath), and for crosses it would do what the patch does right now (for the patch it means that for native it wouldn't add --with-gmp=$with_target_gmp to ac_configure_args if $with_target_gmp is empty (and similarly for -lib and -include).
next prev parent reply other threads:[~2010-12-22 13:23 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-44341-8172@http.gcc.gnu.org/bugzilla/> 2010-12-21 10:43 ` jakub at gcc dot gnu.org 2010-12-21 13:12 ` gnu_andrew at member dot fsf.org 2010-12-22 13:20 ` kkojima at gcc dot gnu.org 2010-12-22 13:23 ` jakub at gcc dot gnu.org [this message] 2011-01-06 21:52 ` aoliva at gcc dot gnu.org 2011-01-14 0:12 ` kkojima at gcc dot gnu.org 2011-01-14 9:55 ` aoliva at gcc dot gnu.org 2011-01-31 5:20 ` aoliva at gcc dot gnu.org 2011-01-31 5:22 ` aoliva at gcc dot gnu.org 2011-02-02 18:23 ` dnovillo at gcc dot gnu.org 2010-05-31 1:02 [Bug libgcj/44341] New: " kkojima at gcc dot gnu dot org 2010-06-24 21:33 ` [Bug libgcj/44341] " rguenth at gcc dot gnu dot org 2010-09-02 10:48 ` rguenth 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=bug-44341-8172-aDa5F1TZpP@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).