public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/17646] [4.0 Regression] xgcc links 64bit objects into a 32bit target Date: Thu, 06 Jan 2005 14:12:00 -0000 [thread overview] Message-ID: <20050106141209.9561.qmail@sourceware.org> (raw) In-Reply-To: <20040924065857.17646.olh@suse.de> ------- Additional Comments From jakub at gcc dot gnu dot org 2005-01-06 14:12 ------- There is no bug, the compiler has been configured incorrectly. --libdir=/usr/lib64 should not be used for multilibbed gcc's, --libdir=/usr/lib is what you want. The os multilib magic will DTRT. Similarly, --libexecdir=/usr/lib64 --with-slibdir=/lib64 is wrong too, you should either just use --prefix=/usr and not pass these at all, or pass --libdir=/usr/lib --libexecdir=/usr/lib --with-slibdir=/lib. powerpc64 gcc defaulting to -m64 works just fine that way for years. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17646
next prev parent reply other threads:[~2005-01-06 14:12 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-09-24 6:59 [Bug bootstrap/17646] New: " olh at suse dot de 2004-09-24 11:56 ` [Bug bootstrap/17646] [4.0 Regression] " pinskia at gcc dot gnu dot org 2004-10-06 5:14 ` [Bug target/17646] " pinskia at gcc dot gnu dot org 2004-10-06 7:28 ` olh at suse dot de 2004-10-06 7:32 ` aj at gcc dot gnu dot org 2004-10-06 9:27 ` matz at suse dot de 2004-10-06 9:29 ` matz at suse dot de 2004-10-06 9:34 ` olh at suse dot de 2004-10-06 9:37 ` matz at suse dot de 2004-10-06 9:56 ` olh at suse dot de 2004-10-06 9:59 ` matz at suse dot de 2004-10-06 13:32 ` pinskia at gcc dot gnu dot org 2004-10-09 15:53 ` olh at suse dot de 2004-10-19 21:26 ` jgrimm2 at us dot ibm dot com 2004-10-27 15:38 ` jgrimm2 at us dot ibm dot com 2004-12-20 1:02 ` pinskia at gcc dot gnu dot org 2004-12-20 5:57 ` aj at gcc dot gnu dot org 2005-01-06 14:12 ` jakub at gcc dot gnu dot org [this message] 2005-01-06 14:16 ` pinskia at gcc dot gnu dot org 2005-01-06 21:58 ` olh at suse dot de 2005-01-06 22:42 ` pinskia at gcc dot gnu dot org 2005-01-06 23:46 ` olh at suse dot de
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=20050106141209.9561.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: 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).