From: Benjie Chen <benjie@amsterdam.lcs.mit.edu>
To: Mike Stump <mrs@apple.com>
Cc: Benjie Chen <benjie@amsterdam.lcs.mit.edu>, gcc@gcc.gnu.org
Subject: Re: problem compiling gcc
Date: Wed, 02 Apr 2003 01:10:00 -0000 [thread overview]
Message-ID: <20030402000803.GA13507@amsterdam.lcs.mit.edu> (raw)
In-Reply-To: <49CFDC06-648B-11D7-B09F-003065A77310@apple.com>
hi
using CC='gcc -no-cpp-precomp' fixes my problem with building
a snapshot of the 3.3 branch on MacOS. i will give this version
a try.
thanks
benjie
On Tue, Apr 01, 2003 at 01:45:43PM -0800, Mike Stump wrote:
> On Tuesday, April 1, 2003, at 11:55 AM, Benjie Chen wrote:
> >i have ran into several problems compiling a non 3.1 version of gcc on
> >MacOS
> >X. 3.1 does not compile one of our programs that uses c++ templates
> >aggresively, so i am trying some other versions of gcc.
>
> I'd recommend a snapshot from the 3.3 branch instead. Also, use
> CC='gcc -no-cpp-precomp' when compiling.
--
benjie chen
benjie@lcs.mit.edu
prev parent reply other threads:[~2003-04-02 0:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 21:45 Benjie Chen
2003-04-01 23:18 ` Mike Stump
2003-04-02 1:10 ` Benjie Chen [this message]
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=20030402000803.GA13507@amsterdam.lcs.mit.edu \
--to=benjie@amsterdam.lcs.mit.edu \
--cc=gcc@gcc.gnu.org \
--cc=mrs@apple.com \
/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).