This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++ bootstrap failures on sparc-sun-solaris2.8 (analyzed)
- To: Richard Henderson <rth at redhat dot com>, Gabriel Dos Reis <gdr at codesourcery dot com>, 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>
- Subject: Re: libstdc++ bootstrap failures on sparc-sun-solaris2.8 (analyzed)
- From: Phil Edwards <pedwards at disaster dot jaj dot com>
- Date: Tue, 31 Jul 2001 20:21:33 -0400
- References: <200107312116.RAA26308@makai.watson.ibm.com> <flsnfcdc80.fsf@jambon.cmla.ens-cachan.fr> <20010731170806.B4763@redhat.com>
On Tue, Jul 31, 2001 at 05:08:06PM -0700, Richard Henderson wrote:
> 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.
It's that "given the right combination" part that causes the problem.
A 32-bit kernel can't run a 64-bit binary, even if the latest ultrasparc
chip and the latest solaris are in use. If `isainfo` doesn't include
sparcv9, then we need to treat 64-bit solaris like any other cross-compile;
the hardware becomes irrelevent.
Phil
--
Would I had phrases that are not known, utterances that are strange, in
new language that has not been used, free from repetition, not an utterance
which has grown stale, which men of old have spoken.
- anonymous Egyptian scribe, c.1700 BC