From: Mike Stump <mrs@apple.com>
To: Long Fei <lfei@ecn.purdue.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: help: how to "quick rebuild" gcc ?
Date: Fri, 23 May 2003 19:09:00 -0000 [thread overview]
Message-ID: <CB9B6D9D-8D4E-11D7-8138-003065A77310@apple.com> (raw)
In-Reply-To: <003801c320ef$5060a750$25fea8c0@feilaptop>
On Thursday, May 22, 2003, at 10:51 PM, Long Fei wrote:
> I am modifying some gcc source files ...
> Can anybody tell me how to "quick rebuild" gcc (i.e. rebuild only
> modified
> source files) instead of starting from "make bootstrap" everytime ?
cd build-tree/gcc
make -j2 cc1plus
or
make -j2 cc1
is not an uncommon way to do this. Takes 15 seconds on my machine.
next prev parent reply other threads:[~2003-05-23 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 6:06 Long Fei
2003-05-23 14:34 ` Kelley Cook
2003-05-23 19:09 ` Mike Stump [this message]
2003-05-23 19:42 ` DJ Delorie
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=CB9B6D9D-8D4E-11D7-8138-003065A77310@apple.com \
--to=mrs@apple.com \
--cc=gcc@gcc.gnu.org \
--cc=lfei@ecn.purdue.edu \
/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).