From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Porting fun, part II
Date: Mon, 17 Jul 2000 12:50:09 -0400 [thread overview]
Message-ID: <200007171650.MAA28027@smtp3.fas.harvard.edu> (raw)
The reason to have pcc generate .8 or .v or .2
or whatever rather than .o is that we use it to
build for multiple architectures in the same
directory, just like 8c or vc or 2c, etc.
See for example the gs or tex build
processes (or don't; they're ugly).
I think what you were looking for was
ape/psh and then you can use CC=cc
which will generate .o's.
Russ
next reply other threads:[~2000-07-17 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-17 16:50 Russ Cox [this message]
2000-07-17 18:16 ` Randolph Fritz
-- strict thread matches above, loose matches on Subject: below --
2000-07-17 9:29 Randolph Fritz
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=200007171650.MAA28027@smtp3.fas.harvard.edu \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.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 NNTP newsgroup(s).