public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janis187 at us dot ibm dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/19135] New: build failure in libiberty multilibs Date: Thu, 23 Dec 2004 00:47:00 -0000 [thread overview] Message-ID: <20041223004714.19135.janis187@us.ibm.com> (raw) GCC builds are broken on powerpc64-unknown-linux-gnu since this patch to libiberty: http://gcc.gnu.org/ml/gcc-cvs/2004-12/msg00805.html. I configure with --build, --host, and --target=powerpc64-linux and --with-cpu=default32; see my recent test results for mainline for the complete set of configure options I use. This problem occurs even for simple builds of C only. The build in powerpc64-linux/64/libiberty tries to create libiberty.so.0.0.0 from 64-bit object files without specifying -m64. The build continues and eventually succeeds, but 'make install' tries the same thing and fails. -- Summary: build failure in libiberty multilibs Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: bootstrap AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: janis187 at us dot ibm dot com CC: gcc-bugs at gcc dot gnu dot org,hjl at gnu dot org GCC build triplet: powerpc64-linux GCC host triplet: powerpc64-linux GCC target triplet: powerpc64-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19135
next reply other threads:[~2004-12-23 0:47 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-12-23 0:47 janis187 at us dot ibm dot com [this message] 2004-12-23 0:53 ` [Bug bootstrap/19135] [4.0 Regression] " pinskia at gcc dot gnu dot org 2004-12-23 1:14 ` hjl at lucon dot org 2004-12-23 1:20 ` hjl at lucon dot org 2004-12-23 1:20 ` hjl at lucon dot org 2004-12-23 1:22 ` pinskia at gcc dot gnu dot org 2004-12-23 5:58 ` aj at gcc dot gnu dot org 2004-12-23 6:53 ` hjl at lucon dot org 2004-12-23 7:06 ` aj at gcc dot gnu dot org 2004-12-23 17:18 ` janis187 at us dot ibm dot com 2004-12-23 18:22 ` hjl at lucon dot org 2004-12-23 18:50 ` janis187 at us dot ibm dot com 2004-12-23 18:55 ` hjl at lucon dot org 2004-12-23 19:30 ` hjl at lucon dot org 2004-12-23 19:44 ` janis187 at us dot ibm dot com 2004-12-23 21:40 ` hjl at lucon dot org 2004-12-25 8:25 ` aj at gcc dot gnu dot org 2004-12-26 23:39 ` janis187 at us dot ibm dot com 2004-12-27 2:41 ` hjl at lucon dot org 2004-12-28 15:42 ` aj 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=20041223004714.19135.janis187@us.ibm.com \ --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: linkBe 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).