From: "Boyd Roberts" <boyd@planete.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] which linux! which gcc!
Date: Sun, 3 Jun 2001 08:54:37 +0200 [thread overview]
Message-ID: <003301c0ebfa$0e3ffdc0$e8b7c6d4@SOMA> (raw)
In-Reply-To: <200106021653.SAA25202@rackham.cd.chalmers.se>
From: "Laura Creighton" <lac@cd.chalmers.se>
>
> the gcc is entirely hosed.
yup. a good metric is probably the number of command line options.
it has too many and that's a really bad sign. yeah, i've installed
the damn thing to please boneheaded fools on their road to ruin. as
soon as it comes apart who's gotta fix it?
rm would.
next prev parent reply other threads:[~2001-06-03 6:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-02 16:53 Laura Creighton
2001-06-02 18:02 ` andrey mirtchovski
2001-06-02 17:45 ` Jim Choate
2001-06-03 7:20 ` Boyd Roberts
2001-06-04 11:55 ` Theo Honohan
2001-06-03 6:54 ` Boyd Roberts [this message]
2001-06-08 8:38 ` Ryan O'NEil
2001-06-02 17:41 anothy
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='003301c0ebfa$0e3ffdc0$e8b7c6d4@SOMA' \
--to=boyd@planete.net \
--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).