From: Ian Lance Taylor <ian@cygnus.com>
To: cato@df.lth.se
Cc: egcs@cygnus.com
Subject: Re: M4 problems
Date: Sun, 05 Apr 1998 10:02:00 -0000 [thread overview]
Message-ID: <199804051618.MAA03735@subrogation.cygnus.com> (raw)
In-Reply-To: <Pine.LNX.3.96.980404201041.2213A-100000@bartlet.df.lth.se>
Date: Sat, 4 Apr 1998 20:12:36 +0200 (MET DST)
From: Krister Walfridsson <cato@df.lth.se>
Are there any good reason we define M4 in the egcs/Makefile?
The top level egcs Makefile is just a generic Makefile which can be
used to build a number of tools in the same directory. It's the same
Makefile that is for binutils and gdb releases, for example.
One of the tools that it can build is autoconf. To do that, you would
put the autoconf and m4 sources as sibling directories to gcc, and run
something like make all-autoconf. When doing this, M4 is defined to
make the right thing happen.
The reason I don't like it is that I get errors from autoconf that I
need GNU m4, but autoconf is generally smart enough to find my GNU m4
(which in NetBSD normlly lives in /usr/pkg/bin and is called gm4) unless
M4 is defined. And we doesn't use M4 anywhere as far I can see.
I think the right fix for the general case is probably to locate m4 in
the top level configure script, along the lines of how DEFAULT_YACC is
handled.
Ian
next prev parent reply other threads:[~1998-04-05 10:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-04 14:20 Krister Walfridsson
1998-04-05 10:02 ` Ian Lance Taylor [this message]
1998-04-05 17:27 ` Jeffrey A Law
1998-04-06 3:15 ` Richard Earnshaw
1998-04-06 8:26 ` Ian Lance Taylor
1998-04-13 6:43 Krister Walfridsson
1998-04-14 13:21 ` 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=199804051618.MAA03735@subrogation.cygnus.com \
--to=ian@cygnus.com \
--cc=cato@df.lth.se \
--cc=egcs@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).