This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: libstdc++ bootstrap failures on sparc-sun-solaris2.8 (analyzed)
- To: Gabriel Dos Reis <gdr at codesourcery dot com>
- Subject: Re: libstdc++ bootstrap failures on sparc-sun-solaris2.8 (analyzed)
- From: Richard Henderson <rth at redhat dot com>
- Date: Tue, 31 Jul 2001 17:08:06 -0700
- Cc: David Edelsohn <dje at watson dot ibm dot com>, Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>, gcc at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org, Alexandre Oliva <aoliva at redhat dot com>, Jan Hubicka <jh at suse dot cz>
- References: <200107312116.RAA26308@makai.watson.ibm.com> <flsnfcdc80.fsf@jambon.cmla.ens-cachan.fr>
On Tue, Jul 31, 2001 at 11:23:43PM +0200, Gabriel Dos Reis wrote:
> 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?
Because the build machinery doesn't know that it's a 32 vs 64
bit thing. All it knows is that it's yet another multilib.
Anyway, how are you going to tell if your ultrasparc can't run
a 64 bit binary? Certainly all of them are capable, given the
right os/kernel combination. I'll suggest trying to run it is
the only foolproof way of detecting whether it can be run.
r~