From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc@gcc.gnu.org, <java@gcc.gnu.org>
Subject: Re: Yet another sparc-sun-solaris2.8 bootstrap failure
Date: Tue, 09 Apr 2002 06:13:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.44.0204091507560.21072-100000@naos.dbai.tuwien.ac.at> (raw)
In-Reply-To: <20020408222404.Y32482@sunsite.ms.mff.cuni.cz>
On Mon, 8 Apr 2002, Jakub Jelinek wrote:
>> This is about the fourth (or fifth?) *different* bootstrap failure on
>> this platform on the release branch. :-(
> I've just commited a fix for this.
Thanks!
Now we are back at the other libffi related bootstrap failure
http://gcc.gnu.org/ml/gcc/2002-04/msg00029.html
| checking size of double... 8
| checking size of long double... 16
| checking size of void *... 8
| checking whether byte ordering is bigendian... cross-compiling... unknown
| checking to probe for byte ordering... guessing bigendian ... unknown
| configure: error: unknown endianess - sorry
| gmake[1]: *** [configure-target-libffi] Error 1
| gmake[1]: Leaving directory `/files/pfeifer/OBJ-0402-1049'
| gmake: *** [bootstrap-lean] Error 2
which occurs only on 32-bit sparc hosts:
http://gcc.gnu.org/ml/gcc/2002-04/msg00080.html
| I have it! The difference is not whether I'm testing trunk or branch,
| the difference is whether the host is
|
| % isainfo -v
| 64-bit sparcv9 applications
| 32-bit sparc applications
|
| which is okay, or
|
| % isainfo -v
| 32-bit sparc applications
|
| which is where this configure test breaks.
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
next prev parent reply other threads:[~2002-04-09 13:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 13:17 Gerald Pfeifer
2002-04-08 13:25 ` Jakub Jelinek
2002-04-09 6:13 ` Gerald Pfeifer [this message]
2002-04-09 8:25 ` Jakub Jelinek
2002-04-09 14:46 ` Tom Tromey
2002-04-09 15:24 ` Gerald Pfeifer
2002-04-09 15:35 ` David S. Miller
2002-04-09 17:01 ` Richard Henderson
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=Pine.BSF.4.44.0204091507560.21072-100000@naos.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=java@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).