public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dje at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/19645] PPC64 64-bit build failure
Date: Fri, 28 Jan 2005 00:18:00 -0000 [thread overview]
Message-ID: <20050128001818.19952.qmail@sourceware.org> (raw)
In-Reply-To: <20050126193636.19645.dje@gcc.gnu.org>
------- Additional Comments From dje at gcc dot gnu dot org 2005-01-28 00:18 -------
I bootstrapped again omitting --with-cpu=default32 and with -m64. No problems.
I also built and installed gcc version 3.4.4 20050109 (prerelease) and used it
to bootstrap with -m64. No problems.
--enable-threads=posix is the default for Linux, so that should not have any effect.
When I originally tried bootstrapping on PPC Linux, I had problems before I used
the incantation. I do not remember if the failure was due to checking. You
might try adding the following options to configure
--build=powerpc64-linux --host=powerpc64-linux --target=powerpc64-linux
--enable-shared --enable-__cxa_atexit
and see if that effects your results.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19645
next prev parent reply other threads:[~2005-01-28 0:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 19:36 [Bug target/19645] New: " dje at gcc dot gnu dot org
2005-01-26 20:52 ` [Bug target/19645] [4.0 Regression] " pinskia at gcc dot gnu dot org
2005-01-26 21:05 ` [Bug target/19645] " pinskia at gcc dot gnu dot org
2005-01-27 17:43 ` dje at gcc dot gnu dot org
2005-01-27 17:46 ` dje at gcc dot gnu dot org
2005-01-27 18:41 ` rth at gcc dot gnu dot org
2005-01-27 19:10 ` dje at watson dot ibm dot com
2005-01-27 20:38 ` rth at gcc dot gnu dot org
2005-01-27 21:17 ` pinskia at gcc dot gnu dot org
2005-01-27 21:20 ` dje at watson dot ibm dot com
2005-01-28 0:18 ` dje at gcc dot gnu dot org [this message]
2005-01-28 0:19 ` dje at gcc dot gnu dot org
2005-01-28 8:12 ` rth at gcc dot gnu dot org
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=20050128001818.19952.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).