public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/23158] building GCC 3.3.6 fails on ppc64 with gcc4 and gcc4.1 Date: Sun, 31 Jul 2005 17:35:00 -0000 [thread overview] Message-ID: <20050731173421.30251.qmail@sourceware.org> (raw) In-Reply-To: <20050731092040.23158.markus@unixforces.net> ------- Additional Comments From pinskia at gcc dot gnu dot org 2005-07-31 17:34 ------- Huh, stdin and stdout are being replaced with restrict. This is not a GCC bug. Try compile gcc 3.3.6 by hand and not using emage at all. I don't trust gentoo's build system right now. -- What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23158
next prev parent reply other threads:[~2005-07-31 17:34 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-07-31 9:25 [Bug c/23158] New: building libstdc++.so.5 " markus at unixforces dot net 2005-07-31 16:17 ` [Bug bootstrap/23158] " pinskia at gcc dot gnu dot org 2005-07-31 16:40 ` [Bug bootstrap/23158] building GCC 3.3.6 " pinskia at gcc dot gnu dot org 2005-07-31 16:44 ` pinskia at gcc dot gnu dot org 2005-07-31 17:13 ` markus at unixforces dot net 2005-07-31 17:22 ` pinskia at gcc dot gnu dot org 2005-07-31 17:27 ` pinskia at gcc dot gnu dot org 2005-07-31 17:35 ` pinskia at gcc dot gnu dot org [this message] 2005-07-31 17:55 ` markus at unixforces dot net 2005-07-31 18:56 ` markus at unixforces dot net 2005-07-31 18:57 ` markus at unixforces dot net 2005-07-31 19:00 ` pinskia at physics dot uc dot edu 2005-07-31 19:01 ` pinskia at gcc dot gnu dot org 2005-07-31 19:11 ` pinskia at gcc dot gnu dot org 2005-07-31 19:15 ` markus at unixforces dot net 2005-07-31 19:49 ` pinskia at gcc dot gnu dot org [not found] <bug-23158-10311@http.gcc.gnu.org/bugzilla/> 2006-08-24 23:55 ` yangdh at cableplus dot com dot cn 2006-08-25 0:03 ` pinskia at gcc dot gnu dot org 2006-11-13 22:32 ` tom_gall at mac dot com 2007-04-04 13:35 ` gcc at futurenotfound dot com
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=20050731173421.30251.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).