public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Toon Moene <toon@moene.indiv.nluug.nl>
Cc: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>, egcs@cygnus.com
Subject: Re: egcs-980205 and m68-next-nextstep3: quick death
Date: Sun, 08 Feb 1998 13:45:00 -0000	[thread overview]
Message-ID: <12135.886971037@hurl.cygnus.com> (raw)
In-Reply-To: <9802082028.AA26597@moene.indiv.nluug.nl>

  In message < 9802082028.AA26597@moene.indiv.nluug.nl >you write:
  > [ ... patch deleted for brevity ... ]
  > 
  > Yes.  OTOH, I saw a discussion already about the "right" way to  
  > solve this (probably via libiberty ?).  Note, however, that I do  
  > know next to nothing about the configure business, so I'm just  
  > waiting for others to advise ...
Well, the "right" way isn't likely to be running in the immediate
future, so we might as well get things working again until the
"right" way is ready :-)


  > Oh, BTW, does anyone have a quick answer to the question why a  
  > standard `./configure; make bootstrap' now leads to gcc being used  
  > as the initial compiler (instead of cc, assuming both are in the  
  > path) ?
I thought configure always preferred gcc to cc if it could find gcc.

jeff

  reply	other threads:[~1998-02-08 13:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-07 11:58 Kaveh R. Ghazi
1998-02-08  0:48 ` Jeffrey A Law
1998-02-08 12:34 ` Toon Moene
1998-02-08 13:45   ` Jeffrey A Law [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-02-06 23:44 Kaveh R. Ghazi
1998-02-07  8:25 ` Robert Lipe
1998-02-07 21:24   ` Jeffrey A Law
1998-02-06 16:53 Toon Moene

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=12135.886971037@hurl.cygnus.com \
    --to=law@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=ghazi@caip.rutgers.edu \
    --cc=toon@moene.indiv.nluug.nl \
    /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).