public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dwalker07 at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/53883] GCC 4.7.1 doesn't build on Mac OS X 10.4.11 Tiger/PowerPC (32-bit), at least with MacPorts
Date: Sun, 08 Jul 2012 20:45:00 -0000 [thread overview]
Message-ID: <bug-53883-4-WkA4ehrTj7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53883-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53883
--- Comment #3 from Daryle Walker <dwalker07 at yahoo dot com> 2012-07-08 20:45:06 UTC ---
(In reply to comment #2)
> (In reply to comment #0)
> > (Should I try building GCC 4.7.1 straight from you guys, without going through
> > MacPorts?)
>
> Yes, probably.
I'm working on that now....
next prev parent reply other threads:[~2012-07-08 20:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-07 2:15 [Bug driver/53883] New: GCC 4.7.1 doesn't build on Mac OS X 10.4.11 Tiger/PowerPC (32-bit) dwalker07 at yahoo dot com
2012-07-07 2:21 ` [Bug driver/53883] " dwalker07 at yahoo dot com
2012-07-07 12:47 ` redi at gcc dot gnu.org
2012-07-08 20:45 ` dwalker07 at yahoo dot com [this message]
2012-07-10 1:32 ` [Bug driver/53883] GCC 4.7.1 doesn't build on Mac OS X 10.4.11 Tiger/PowerPC (32-bit), at least with MacPorts dwalker07 at yahoo dot com
2012-07-10 1:34 ` dwalker07 at yahoo dot com
2012-07-10 6:36 ` schwab@linux-m68k.org
2012-07-14 18:52 ` dwalker07 at yahoo dot com
2012-08-05 16:52 ` dwalker07 at yahoo dot com
2012-08-05 17:09 ` dwalker07 at yahoo dot com
2012-08-05 17:13 ` dwalker07 at yahoo 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=bug-53883-4-WkA4ehrTj7@http.gcc.gnu.org/bugzilla/ \
--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).