From: Gabriel Dos Reis <gdr@codesourcery.com>
To: David Edelsohn <dje@watson.ibm.com>
Cc: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>,
gcc@gcc.gnu.org, libstdc++@gcc.gnu.org,
Alexandre Oliva <aoliva@redhat.com>, Jan Hubicka <jh@suse.cz>,
Gabriel Dos Reis <gdr@codesourcery.com>
Subject: Re: libstdc++ bootstrap failures on sparc-sun-solaris2.8 (analyzed)
Date: Tue, 31 Jul 2001 14:23:00 -0000 [thread overview]
Message-ID: <flsnfcdc80.fsf@jambon.cmla.ens-cachan.fr> (raw)
In-Reply-To: <200107312116.RAA26308@makai.watson.ibm.com>
David Edelsohn <dje@watson.ibm.com> writes:
| Again, V3 needs to go into a "cross-compiling" mode for
| std_limits.h when generating a 64-bit library on a 32-bit host. I have
| proposed that the build fall back to using the generic std_limits.h file
| if gen-num-limits fails.
Because we're going to try to run a 64-bit app on a system running
32-bit, can't we predict it will fail? If so, why should we try to run
it in the first place?
Apart from that, I agree with the generic std_limits.h stuff.
-- Gaby
next prev parent reply other threads:[~2001-07-31 14:23 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-25 9:34 Trunk frustration Jan Hubicka
2001-07-25 12:01 ` Stan Shebs
2001-07-25 22:12 ` Andreas Jaeger
2001-07-26 1:24 ` Gerald Pfeifer
2001-07-26 5:40 ` Daniel Berlin
2001-07-26 6:29 ` Gerald Pfeifer
2001-07-26 7:03 ` Gabriel Dos Reis
2001-07-26 14:14 ` Gerald Pfeifer
2001-07-26 14:34 ` Gabriel Dos Reis
2001-07-27 6:45 ` Jan Hubicka
2001-07-27 6:57 ` Gerald Pfeifer
2001-07-27 7:00 ` Jan Hubicka
2001-07-27 7:29 ` Jan Hubicka
2001-07-27 7:33 ` Gerald Pfeifer
2001-07-27 7:40 ` Jan Hubicka
2001-07-27 8:47 ` Fergus Henderson
2001-07-27 8:18 ` Jan Hubicka
2001-07-27 8:50 ` Jan Hubicka
2001-07-30 10:00 ` Gerald Pfeifer
2001-07-30 19:11 ` Alexandre Oliva
2001-07-31 4:07 ` Jan Hubicka
2001-07-31 14:05 ` libstdc++ bootstrap failures on sparc-sun-solaris2.8 (analyzed) Gerald Pfeifer
2001-07-31 14:16 ` Gabriel Dos Reis
2001-07-31 14:31 ` David Edelsohn
2001-07-31 14:53 ` Gabriel Dos Reis
2001-07-31 15:16 ` David Edelsohn
2001-07-31 15:24 ` Gabriel Dos Reis
2001-07-31 15:32 ` David Edelsohn
2001-07-31 22:57 ` Mark Mitchell
2001-07-31 23:05 ` Benjamin Kosnik
2001-07-31 23:16 ` Mark Mitchell
2001-08-01 0:20 ` Gabriel Dos Reis
2001-08-01 7:49 ` Mark Mitchell
2001-08-01 0:18 ` Gabriel Dos Reis
2001-07-31 23:01 ` Benjamin Kosnik
2001-07-31 14:16 ` David Edelsohn
2001-07-31 14:23 ` Gabriel Dos Reis [this message]
2001-07-31 17:08 ` Richard Henderson
2001-07-31 17:19 ` Phil Edwards
2001-07-31 17:24 ` Richard Henderson
2001-07-31 17:58 ` David Edelsohn
2001-07-31 18:06 ` Richard Henderson
2001-08-01 6:26 ` Alexandre Oliva
2001-08-01 10:22 ` David Edelsohn
2001-08-01 10:37 ` Mark Mitchell
2001-08-01 18:44 ` Joern Rennecke
2001-08-01 18:57 ` Mark Mitchell
2001-08-01 11:07 ` Alexandre Oliva
2001-07-31 20:40 ` Gabriel Dos Reis
2001-07-26 8:20 ` Trunk frustration Jan Hubicka
2001-07-26 14:11 ` Gerald Pfeifer
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=flsnfcdc80.fsf@jambon.cmla.ens-cachan.fr \
--to=gdr@codesourcery.com \
--cc=aoliva@redhat.com \
--cc=dje@watson.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=jh@suse.cz \
--cc=libstdc++@gcc.gnu.org \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).