From: Richard Earnshaw <rearnsha@arm.com>
To: law@cygnus.com
Cc: rearnsha@sun52.arm.com
Subject: Re: M4 problems
Date: Mon, 06 Apr 1998 03:15:00 -0000 [thread overview]
Message-ID: <199804061012.LAA06183@sun52.NIS.cambridge> (raw)
In-Reply-To: <17489.891801165@hurl.cygnus.com>
>
>
> In message < Pine.LNX.3.96.980404201041.2213A-100000@bartlet.df.lth.se >you wri
> te:
> > Are there any good reason we define M4 in the egcs/Makefile?
> Yes. It's part of the one tree build system.
>
> If you take the m4 sources and put them in the source tree with egcs,
> then egcs will automatically build and use the m4 binaries that you
> just built instead of whatever is lying around on the system.
>
The problem is not what happens when you have the m4 sources in your build
tree. It's what happens when you don't. If you don't have the source
then configure *assumes* that your gnu m4 is installed as 'm4' (if it
isn't then things break).
I don't particularly want to have to have m4 in my egcs build tree (it's
big enough already); but equally, I'm not keen on having gnu m4 installed
as anything other than gm4 (I can't have an environment where standard
utilities are being replaced by others -- not all my work is gnu based and
it could result in problems in the field which I'm not aware of).
The obvious solution for this would be for the toplevel configure to
detect (a la autoconf) where the installed version of gnu m4 is (it can
find a gnu m4 that is installed as gm4), and to use that.
Why is this not done?
Richard.
next prev parent reply other threads:[~1998-04-06 3:15 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
1998-04-05 17:27 ` Jeffrey A Law
1998-04-06 3:15 ` Richard Earnshaw [this message]
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=199804061012.LAA06183@sun52.NIS.cambridge \
--to=rearnsha@arm.com \
--cc=law@cygnus.com \
--cc=rearnsha@sun52.arm.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).