From: Per Bothner <bothner@cygnus.com>
To: law@cygnus.com
Cc: egcs@cygnus.com
Subject: Re: testing consistency
Date: Thu, 11 Sep 1997 14:01:00 -0000 [thread overview]
Message-ID: <199709112101.OAA12091@cygnus.com> (raw)
In-Reply-To: <19111.874006103@hurl.cygnus.com>
> Based on the rest of your message the answer is "yes, there has
> been something in the standard gcc releases to do this".
There does seem to be. That is a bug that should be fixed.
> on linux, gcc will be installed in /usr.
99% of Linux users use a distribution, such as Debian or RedHat.
/usr should belong to the distribution. For user to randomly
add packages to /usr is wrong, because it reduces the effectiveness
of using a package management system. For example, if /usr/bin/gcc
is overridden, the package system may complain when it is time to
do a laietr update. And a later package update will fail to remove
the user-installed gcc-lib.
Packages manually compiled by the user (not using the package management
system) belong in /usr/local, not /usr, on any well-run Linux system.
Yes, I have violated this rule. But gcc should not do it by default.
> Well, I still think it's the wrong thing to do, but if Richard
> Henderson or someone else familiar with linux sez it's OK, then
> I'll go ahead and install the changes.
I say: don't. It's wrong.
--Per Bothner
Cygnus Solutions bothner@cygnus.com http://www.cygnus.com/~bothner
next prev parent reply other threads:[~1997-09-11 14:01 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-10 22:37 Aaron Jackson
1997-09-11 0:40 ` Jim Wilson
1997-09-11 9:23 ` Jeffrey A Law
1997-09-11 10:17 ` H.J. Lu
1997-09-11 11:05 ` Jeffrey A Law
1997-09-11 11:05 ` H.J. Lu
1997-09-11 11:05 ` Jeffrey A Law
1997-09-11 11:36 ` H.J. Lu
1997-09-11 11:36 ` Jeffrey A Law
1997-09-11 12:54 ` H.J. Lu
1997-09-11 13:20 ` Jeffrey A Law
1997-09-11 14:01 ` Per Bothner [this message]
1997-09-11 15:09 ` Richard Henderson
1997-09-18 12:57 ` Bob Glickstein
1997-09-11 13:37 ` Jim Wilson
1997-09-11 14:11 ` Per Bothner
1997-09-11 15:01 ` Jeffrey A Law
1997-09-11 16:13 ` Joe Buck
1997-09-11 17:08 ` Jim Wilson
1997-09-11 18:39 ` Joe Buck
1997-09-11 13:20 ` Per Bothner
1997-09-12 7:27 ` Paul Koning
1997-09-11 12:57 ` Ian Lance Taylor
1997-09-11 13:51 ` H.J. Lu
1997-09-11 13:54 ` Ian Lance Taylor
1997-09-11 13:59 ` H.J. Lu
1997-09-11 14:04 ` Ian Lance Taylor
1997-09-11 19:01 ` Jim Wilson
1997-09-14 12:06 ` Joel Sherrill
1997-09-14 12:19 ` Jeffrey A Law
1997-09-14 12:44 ` Joel Sherrill
1997-09-18 22:56 ` Jeffrey A Law
1997-09-19 8:04 ` H.J. Lu
1997-09-19 8:15 ` Jeffrey A Law
1997-09-19 12:19 ` Jim Wilson
1997-09-19 13:14 ` Joe Buck
1997-09-19 14:51 ` Dave Love
1997-09-19 17:12 ` Jeffrey A Law
-- strict thread matches above, loose matches on Subject: below --
1997-09-19 9:52 Kaveh R. Ghazi
1997-09-19 10:20 ` Joe Buck
1997-09-18 21:42 Mike Stump
1997-09-18 21:50 ` Jeffrey A Law
1997-09-18 21:55 ` Joe Buck
[not found] <oren6qtfsg.fsf@sunsite.dcc.unicamp.br>
1997-09-18 20:37 ` Jeffrey A Law
1997-09-18 21:32 ` Alexandre Oliva
1997-09-18 22:24 ` Jeffrey A Law
1997-09-15 14:44 Alexandre Oliva
1997-09-11 21:33 Peter Seebach
[not found] <199709112227.SAA01970cygnus.egcs@tweedledumb.cygnus.com>
1997-09-11 16:31 ` not-for-mail
1997-09-11 15:27 meissner
1997-09-11 16:06 ` Doug Evans
1997-09-11 17:08 ` Joe Buck
1997-09-11 11:36 Mike Stump
1997-09-11 12:47 ` Jim Wilson
1997-09-05 18:09 meissner
1997-09-05 18:55 ` Joel Sherrill
1997-09-04 18:48 Joe Buck
1997-09-04 20:13 ` Dave Avery
1997-09-04 21:11 ` Jim Wilson
1997-09-05 8:56 ` Joe Buck
1997-09-05 8:58 ` Joe Buck
1997-09-05 7:26 ` Joel Sherrill
1997-09-05 12:44 ` Jeffrey A Law
1997-09-05 16:40 ` Joel Sherrill
1997-09-10 15:21 ` Jeffrey A Law
1997-09-10 16:15 ` Joe Buck
1997-09-10 16:22 ` Jeffrey A Law
1997-09-10 22:23 ` Alexandre Oliva
1997-09-11 9:23 ` Jeffrey A Law
1997-09-11 10:01 ` Jeffrey A Law
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=199709112101.OAA12091@cygnus.com \
--to=bothner@cygnus.com \
--cc=egcs@cygnus.com \
--cc=law@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).