From: Jeffrey A Law <law@cygnus.com>
To: drepper@cygnus.com (Ulrich Drepper)
Cc: egcs@cygnus.com
Subject: Re: once we have cpplib...
Date: Thu, 09 Apr 1998 22:03:00 -0000 [thread overview]
Message-ID: <29644.892184591@hurl.cygnus.com> (raw)
In-Reply-To: <r2hg43eyby.fsf@happy.cygnus.com>
In message < r2hg43eyby.fsf@happy.cygnus.com >you write:
> bothner@cygnus.com (Per Bothner) writes:
>
> > Persnally, I don't see this as having much importance. Do we we really
> > support the -V option? Cygnus has always recommended against its use.
>
> I think it is essential. I have many old compilers lying around since
> I build and install egcs frequently. If a version is broken I must be
> easy to use an old version.
So we have gcc.c look in $(libsubdir) for cpp. If it finds it, then
it invokes the passes in the old way (cpp, cc1). If no cpp is found
then it assumes that we have an integrated cpp & cc1.
jeff
next prev parent reply other threads:[~1998-04-09 22:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-08 21:20 Ulrich Drepper
1998-04-08 23:35 ` Per Bothner
1998-04-09 2:06 ` Andreas Schwab
1998-04-09 8:27 ` Ulrich Drepper
[not found] ` <199804090635.XAA26672.cygnus.egcs@cygnus.com>
1998-04-09 14:17 ` Ulrich Drepper
1998-04-09 17:44 ` Joe Buck
1998-04-09 21:23 ` Jeffrey A Law
1998-04-11 9:32 ` John Polstra
1998-04-16 10:51 ` Manfred Hollstein
1998-04-16 22:46 ` H.J. Lu
1998-04-18 8:18 ` New installation defaults (was: Re: once we have cpplib...) Manfred Hollstein
1998-04-18 18:48 ` H.J. Lu
1998-04-10 3:43 ` once we have cpplib Martin von Loewis
1998-04-09 22:03 ` Jeffrey A Law [this message]
1998-04-10 7:27 ` Per Bothner
1998-04-21 19:10 ` Joern Rennecke
[not found] ` <199804220100.CAA28717.cygnus.egcs@phal.cygnus.co.uk>
1998-04-22 9:05 ` Ulrich Drepper
1998-04-09 18:29 ` Jeffrey A Law
1998-04-09 17:44 ` Ulrich Drepper
1998-04-10 0:39 ` Per Bothner
1998-04-13 9:43 ` Dave Brolley
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=29644.892184591@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=drepper@cygnus.com \
--cc=egcs@cygnus.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).