public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Craig Burley <burley@gnu.org>
To: g77-alpha@gnu.org, egcs@cygnus.com, gcc2@cygnus.com
Subject: Re: Require GNU Make Somehow?
Date: Sat, 02 May 1998 14:30:00 -0000	[thread overview]
Message-ID: <199805022006.QAA08833@melange.gnu.org> (raw)
In-Reply-To: <rzqbttgfv8m.fsf@djlvig.dl.ac.uk>

>I'm confused about a g77 configure.in as I thought there was policy
>against one, but there used to be a test in config-lang.in for srcdir
>!= builddir.  That just warned about the need for GNU make at
>configure time.  I'll look into sorting something out for g77's
>makefile, but it presumably won't kick in until g77 starts building.

Oops, I meant config-lang.in, not configure.in, you're right.  Yes,
the test and message have gone away; I don't mind resurrecting
them, but feel that's really the job of the top-level makefile
to do, in this case, gcc's and egcs's, and thinking down that
avenue led to my original email on this topic.

>Indeed.  If I want GNU make, I'd be (should be) typing `gmake' on a
>non-GNU system and a test is needed at compile time, not configure
>time.

Right, though it might be most straightforward and reliable to
have configure time lay a sort of "trap" that is either avoided
by using GNU make at compile time, or triggered by not using
GNU make then, and the effect of the trap is to print a nice
message and exit.

        tq vm, (burley)

  reply	other threads:[~1998-05-02 14:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-05-01 16:49 Craig Burley
1998-05-01 17:18 ` Joe Buck
1998-05-01 19:37   ` Craig Burley
1998-05-02 10:47     ` Dave Love
1998-05-02 14:30       ` Craig Burley [this message]
1998-05-03 22:02         ` Jim Meyering
1998-05-04 12:46           ` Craig Burley
     [not found] <egcs.199805020042.UAA25532@melange.gnu.org>
1998-05-02  1:35 ` Todd P. Whitesel

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=199805022006.QAA08833@melange.gnu.org \
    --to=burley@gnu.org \
    --cc=egcs@cygnus.com \
    --cc=g77-alpha@gnu.org \
    --cc=gcc2@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).