public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Cc: bkoz@redhat.com, gcc@gcc.gnu.org, shebs@apple.com
Subject: Re: 64-bit configure hell
Date: Thu, 25 Nov 2004 20:45:00 -0000	[thread overview]
Message-ID: <ydd3byxbr5n.fsf@xayide.TechFak.Uni-Bielefeld.DE> (raw)
In-Reply-To: Ulrich Weigand's message of "Thu, 25 Nov 2004 19:12:03 +0100"

Ulrich Weigand <Ulrich.Weigand@de.ibm.com> writes:

> I guess one way to fix this problem would be to only build those
> multilibs where the required system dependencies are in fact installed;
> this could be verified by attempting to build a 'hello world' using
> the multilib flags.  If this already fails, there's no point in
> attempting to build the library.
> 
> Something like that is actually attempted in config-ml.in, at least
> for some platforms.  However this doesn't work, as those checks are
> not applied for libgcc (and thus we fail already there).  I think I
> pointed this out already some time in the past, and was told that
> this is difficult to fix with the current make process ...

Indeed: libgcc would have to be moved to the toplevel, since you need the
stage 1 compiler to perform this test.  The bootstrap compiler may not be
gcc (so require multilib flags different from gcc's) or not be
multilib-aware.

	Rainer

  reply	other threads:[~2004-11-25 20:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-25 19:14 Ulrich Weigand
2004-11-25 20:45 ` Rainer Orth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-26  7:16 Bill Northcott
2004-11-27 23:57 ` Mike Stump
2004-11-25 16:32 Benjamin Kosnik
2004-11-25 20:56 ` Stan Shebs
2004-11-26  3:26   ` Peter O'Gorman
2004-11-26  4:20     ` Peter O'Gorman
2004-11-24 23:24 Stan Shebs
2004-11-24 23:39 ` David Edelsohn
2004-11-25  0:48   ` Kaveh R. Ghazi
2004-11-25  2:42     ` Joe Buck
2004-11-26 14:06   ` Alexandre Oliva
2004-11-25  3:59 ` Tom Tromey
2004-11-25  5:04   ` Stan Shebs
2004-11-25  9:44 ` Andrew Pinski
2004-11-28  7:58 ` Daniel Jacobowitz
2004-11-28 12:50   ` Eric Botcazou

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=ydd3byxbr5n.fsf@xayide.TechFak.Uni-Bielefeld.DE \
    --to=ro@techfak.uni-bielefeld.de \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=bkoz@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=shebs@apple.com \
    /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).