public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law AT cygnus.com>
To: Marc Espie <espie AT quatramaran.ens.fr>
Cc: mrs AT wrs.com, egcs AT egcs.cygnus.com
Subject: Re: FreeBSD 4.0
Date: Thu, 16 Sep 1999 13:54:00 -0000	[thread overview]
Message-ID: <18505.937514824@upchuck.cygnus.com> (raw)
In-Reply-To: <199909162035.WAA19219@quatramaran.ens.fr>

  In message < 199909162035.WAA19219@quatramaran.ens.fr >you write:
  > Sigh. I wonder if I speak martian of something sometimes...
  > See, this is exactly what I mean.
  > I do understand that the end user  may want to install a newer compiler
  > on an older OpenBSD.  I have absolutely no problem with this.
  > *of course* he shouldn't get fucked by whatever we want to do with the
  > compiler.
You and MRS are both wrong in this case.  You still do not want to override
USER_H, even if you "own" /usr as the distribution maintainer.

And you'll find that if you do things the right way from the start that
you won't need to override USER_H, even when building your distributions.


  > What I mean is that we want to keep upgrading our system headers.
  > We want them to work, we want the current system to match what gcc
  > needs.
And that's fine.  I did it myself in the pre-net2 days for Berkeley.  To find
out what's getting mashed you install the compiler, then go look at what's
in its include directory.  Manually filter out the small number of files it's
going to always install (which you absolutely should not override).

jeff


WARNING: multiple messages have this Message-ID
From: Jeffrey A Law <law@cygnus.com>
To: Marc Espie <espie@quatramaran.ens.fr>
Cc: mrs@wrs.com, egcs@egcs.cygnus.com
Subject: Re: FreeBSD 4.0
Date: Thu, 30 Sep 1999 18:02:00 -0000	[thread overview]
Message-ID: <18505.937514824@upchuck.cygnus.com> (raw)
Message-ID: <19990930180200.Pyo3RTIaQ-nO4O60cGDYfko-SnSUD8xFvvG_e-3dZKI@z> (raw)
In-Reply-To: <199909162035.WAA19219@quatramaran.ens.fr>

  In message < 199909162035.WAA19219@quatramaran.ens.fr >you write:
  > Sigh. I wonder if I speak martian of something sometimes...
  > See, this is exactly what I mean.
  > I do understand that the end user  may want to install a newer compiler
  > on an older OpenBSD.  I have absolutely no problem with this.
  > *of course* he shouldn't get fucked by whatever we want to do with the
  > compiler.
You and MRS are both wrong in this case.  You still do not want to override
USER_H, even if you "own" /usr as the distribution maintainer.

And you'll find that if you do things the right way from the start that
you won't need to override USER_H, even when building your distributions.


  > What I mean is that we want to keep upgrading our system headers.
  > We want them to work, we want the current system to match what gcc
  > needs.
And that's fine.  I did it myself in the pre-net2 days for Berkeley.  To find
out what's getting mashed you install the compiler, then go look at what's
in its include directory.  Manually filter out the small number of files it's
going to always install (which you absolutely should not override).

jeff


  reply	other threads:[~1999-09-16 13:54 UTC|newest]

Thread overview: 88+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-16 13:13 Mike Stump
1999-09-16 13:36 ` Marc Espie
1999-09-16 13:54   ` Jeffrey A Law [this message]
1999-09-30 18:02     ` Jeffrey A Law
1999-09-30 18:02   ` Marc Espie
1999-09-30 18:02 ` Mike Stump
  -- strict thread matches above, loose matches on Subject: below --
1999-09-20 13:43 Mike Stump
1999-09-30 18:02 ` Mike Stump
1999-09-16 12:42 Mike Stump
1999-09-30 18:02 ` Mike Stump
1999-09-14 19:32 Wes Morgan
1999-09-14 20:08 ` Richard Henderson
1999-09-15  2:00   ` Jeffrey A Law
1999-09-30 18:02     ` Jeffrey A Law
1999-09-30 18:02   ` Richard Henderson
1999-09-14 22:34 ` Loren James Rittle
1999-09-14 23:00   ` Zack Weinberg
1999-09-14 23:14     ` David O'Brien
1999-09-15  0:25       ` Zack Weinberg
1999-09-15  0:56         ` David O'Brien
1999-09-15  1:21           ` Andreas Schwab
1999-09-15  1:40             ` David O'Brien
1999-09-15  2:23               ` Andreas Schwab
1999-09-15  3:11                 ` David O'Brien
1999-09-15  3:52                   ` Andreas Schwab
1999-09-30 18:02                     ` Andreas Schwab
1999-09-30 18:02                   ` David O'Brien
1999-09-30 18:02                 ` Andreas Schwab
1999-09-20  3:58               ` Jeffrey A Law
1999-09-30 18:02                 ` Jeffrey A Law
1999-09-30 18:02               ` David O'Brien
1999-09-30 18:02             ` Andreas Schwab
1999-09-30 18:02           ` David O'Brien
1999-09-15  1:17         ` David O'Brien
1999-09-15  9:23           ` Zack Weinberg
1999-09-15 10:24             ` David O'Brien
1999-09-16 14:48               ` Richard Henderson
1999-09-30 18:02                 ` Richard Henderson
1999-09-30 18:02               ` David O'Brien
1999-09-20  4:20             ` Jeffrey A Law
1999-09-30 18:02               ` Jeffrey A Law
1999-09-30 18:02             ` Zack Weinberg
1999-09-20  4:34           ` Jeffrey A Law
1999-09-20  9:26             ` Zack Weinberg
1999-09-20  9:55               ` Jeffrey A Law
1999-09-20 10:17                 ` Zack Weinberg
1999-09-20 10:38                   ` Richard Earnshaw
1999-09-20 11:02                     ` Zack Weinberg
1999-09-30 18:02                       ` Zack Weinberg
1999-09-20 11:39                     ` Horst von Brand
1999-09-20 11:49                       ` Chris G. Demetriou
1999-09-30 18:02                         ` Chris G. Demetriou
1999-09-30 18:02                       ` Horst von Brand
1999-09-30 18:02                     ` Richard Earnshaw
1999-09-23  8:51                   ` Jeffrey A Law
1999-09-30 18:02                     ` Jeffrey A Law
1999-09-30 18:02                   ` Zack Weinberg
1999-09-30 18:02                 ` Jeffrey A Law
1999-09-30 18:02               ` Zack Weinberg
1999-09-30 18:02             ` Jeffrey A Law
1999-09-30 18:02           ` David O'Brien
1999-09-30 18:02         ` Zack Weinberg
1999-09-15  2:00       ` Jeffrey A Law
1999-09-15  2:25         ` David O'Brien
1999-09-15  2:33           ` Jeffrey A Law
1999-09-30 18:02             ` Jeffrey A Law
1999-09-30 18:02           ` David O'Brien
     [not found]         ` <37DFAD27.3E6A25E3@datadesign.com>
     [not found]           ` <199909152042.PAA29374@latour.rsch.comm.mot.com>
1999-09-15 14:26             ` Bruce Korb
1999-09-15 17:10               ` Jeffrey A Law
1999-09-16  1:46                 ` Marc Espie
1999-09-16  6:57                   ` Jeffrey A Law
1999-09-16  7:41                     ` Marc Espie
1999-09-16  7:55                       ` Jeffrey A Law
1999-09-30 18:02                         ` Jeffrey A Law
1999-09-30 18:02                       ` Marc Espie
1999-09-30 18:02                     ` Jeffrey A Law
1999-09-30 18:02                   ` Marc Espie
1999-09-30 18:02                 ` Jeffrey A Law
1999-09-30 18:02               ` Bruce Korb
1999-09-30 18:02         ` Jeffrey A Law
1999-09-30 18:02       ` David O'Brien
1999-09-15  1:59     ` Jeffrey A Law
1999-09-30 18:02       ` Jeffrey A Law
1999-09-30 18:02     ` Zack Weinberg
1999-09-15  7:42   ` Wes Morgan
1999-09-30 18:02     ` Wes Morgan
1999-09-30 18:02   ` Loren James Rittle
1999-09-30 18:02 ` Wes Morgan

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=18505.937514824@upchuck.cygnus.com \
    --to=gcc@gcc.gnu.org \
    /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).