From: Craig Burley <burley@gnu.org>
To: g77-alpha@gnu.org, egcs@cygnus.com, gcc2@cygnus.com
Subject: Re: Require GNU Make Somehow?
Date: Mon, 04 May 1998 12:46:00 -0000 [thread overview]
Message-ID: <199805041624.MAA29687@melange.gnu.org> (raw)
In-Reply-To: <87af8zc6r0.fsf@eng.ascend.com>
>This isn't quite the same, since GNU make isn't required to
>build the fileutils, but it might be useful...
Thanks! We're going to try a simple solution in the next g77 0.5.23 alpha
release, which is a release that will be based on gcc 2.8:
# We want to try to catch the common trap of building outside srcdir
# without GNU make. We do that by adding a phony target to the
# all the LANGUAGES dependencies, and doing the check in the phony target.
$(LANGUAGES): gnumake-check
gnumake-check:
@if [ $(srcdir) != . ]; then \
case `$(MAKE) --version 2>/dev/null` in \
*GNU*) true ;; \
*) echo 1>&2 ''; \
echo 1>&2 'You must use GNU make to build outside the source directory.'; \
echo 1>&2 ''; \
false;; \
esac; \
else true; \
fi
(This goes into g77's Make-lang.in, a fragment that gets pulled into
the "master" Makefile for gcc when configuring with g77 present.
$(LANGUAGES) is the list of languages the user wants to build; I'd
thought about making this just "F77 f77" to catch the problem only
when g77 itself gets built, but then realized that happens well
into a build, so this approach, which Dave Love came up with, seems
best, because it kicks back on error quite quickly after issuing
the non-GNU `make' command.)
tq vm, (burley)
next prev parent reply other threads:[~1998-05-04 12:46 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
1998-05-03 22:02 ` Jim Meyering
1998-05-04 12:46 ` Craig Burley [this message]
[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=199805041624.MAA29687@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).