public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/33764] [4.2/4.3 regression] gij is built as 32-bit binary when building multilib gcc
Date: Wed, 09 Jan 2008 22:14:00 -0000	[thread overview]
Message-ID: <20080109221404.23204.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33764-5606@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from rguenther at suse dot de  2008-01-09 22:14 -------
Subject: Re:  [4.2/4.3 regression] gij is built as 32-bit
 binary when building multilib gcc

On Wed, 9 Jan 2008, tromey at gcc dot gnu dot org wrote:

> ------- Comment #3 from tromey at gcc dot gnu dot org  2008-01-09 22:03 -------
> What should we do here?
> I think the problem is that we have a single bindir, but we are
> building multiple executables -- one per multilib.

Well, usually you don't multi-"lib" binaries - which is why it is
called multilibbing, not multibinaring ;)  No idea how easy that is
to implement, though.

Richard.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33764


  parent reply	other threads:[~2008-01-09 22:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-13 19:35 [Bug java/33764] New: [4.3 " bero at arklinux dot org
2007-10-14 14:59 ` [Bug java/33764] [4.2/4.3 " hjl at lucon dot org
2007-10-22  8:43 ` [Bug libgcj/33764] " pinskia at gcc dot gnu dot org
2008-01-09 22:03 ` tromey at gcc dot gnu dot org
2008-01-09 22:14 ` rguenther at suse dot de [this message]
2008-01-09 22:17 ` tromey at gcc dot gnu dot org
2008-01-12 17:53 ` rguenth at gcc dot gnu dot org
2008-01-26 22:20 ` rguenth at gcc dot gnu dot org
2008-02-01 16:59 ` jsm28 at gcc dot gnu dot org
2008-05-19 20:28 ` [Bug libgcj/33764] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org
2008-11-12 20:56 ` jakub at gcc dot gnu dot org
2008-11-12 21:04 ` [Bug libgcj/33764] [4.2/4.3 " jakub at gcc dot gnu dot org
2009-03-31 20:13 ` [Bug libgcj/33764] [4.3 " jsm28 at gcc dot gnu dot org
2009-08-04 12:36 ` rguenth at gcc dot gnu dot org
2010-05-22 18:19 ` 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=20080109221404.23204.qmail@sourceware.org \
    --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).