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/24119] gcc-4.x fails to build on AIX 5.2.0.0-ML04 Date: Fri, 30 Sep 2005 16:24:00 -0000 [thread overview] Message-ID: <20050930162309.5245.qmail@sourceware.org> (raw) In-Reply-To: <20050929120943.24119.h.m.brand@xs4all.nl> ------- Additional Comments From dje at gcc dot gnu dot org 2005-09-30 16:23 ------- Yes, GCC 4.1 needs -Wl,-bbigtoc, but what is "-B/usr/local/ppc64/bin" for? Once you do something like that, it's an unsupported build. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24119
next prev parent reply other threads:[~2005-09-30 16:24 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-09-29 12:10 [Bug c/24119] New: " h dot m dot brand at xs4all dot nl 2005-09-29 13:21 ` [Bug target/24119] " pinskia at gcc dot gnu dot org 2005-09-30 16:24 ` dje at gcc dot gnu dot org [this message] 2005-09-30 18:07 ` h dot m dot brand at xs4all dot nl 2005-10-01 16:00 ` dje at gcc dot gnu dot org [not found] <bug-24119-11434@http.gcc.gnu.org/bugzilla/> 2005-10-02 4:45 ` dje at gcc dot gnu dot org 2005-10-02 13:23 ` h dot m dot brand at xs4all dot nl 2005-10-04 14:24 ` h dot m dot brand at xs4all dot nl 2005-10-04 15:00 ` dje at watson dot ibm dot com 2005-10-04 19:13 ` h dot m dot brand at xs4all dot nl 2005-10-04 19:24 ` dje at watson dot ibm dot com 2005-10-06 4:30 ` dje at gcc dot gnu dot org 2005-10-06 6:33 ` h dot m dot brand at xs4all dot nl 2005-10-06 8:44 ` h dot m dot brand at xs4all dot nl 2005-10-06 13:30 ` dje at watson dot ibm dot com 2005-10-06 14:04 ` h dot m dot brand at xs4all dot nl 2005-10-06 14:07 ` dje at watson dot ibm dot com 2005-10-06 17:24 ` dje at gcc dot gnu dot org 2005-10-11 14:37 ` h dot m dot brand at xs4all dot nl 2005-10-11 14:52 ` h dot m dot brand at xs4all dot nl
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=20050930162309.5245.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).