From: Mark H Weaver <mhw@netris.org>
To: Mikael Djurfeldt <mikael@djurfeldt.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Officially require GNU Make to build Guile? (was Re: Bootstrap optimization)
Date: Tue, 30 Oct 2018 02:04:38 -0400 [thread overview]
Message-ID: <87a7mwkm0e.fsf@netris.org> (raw)
In-Reply-To: <CAA2XvwJGFL89k81C8Y5wTawceAUPGLLMquWut=ibcfuCf7w00Q@mail.gmail.com> (Mikael Djurfeldt's message of "Mon, 29 Oct 2018 11:33:01 +0100")
Hi Mikael,
Mikael Djurfeldt <mikael@djurfeldt.com> writes:
> But, as you concluded, Guile currently uses GNU Make specific
> functionality. $(filter-out ...) in bootstrap/Makefile.am is such a
> case and also the vpath and %-thingies in am/bootstrap.am.
I guess you're right.
> Probably, you should start out by making an inventory of the various
> uses of GNU Make functionality and for each case evaluate how much
> work would be required to make it standard. First then it is possible
> to decide if it is worth to do it.
>
> However, note that applying my suggested patch would not really change
> the situation much in this respect since that piece of functionality
> already now depends on the GNU Make specific $ (filter-out ...), such
> that when GNU Make specifics get handled, having applied my patch
> doesn't really increase the amount of work in any way.
It's a good point. Okay, I'm convinced. Please go ahead and push your
patch to stable-2.2. Thanks for talking me through it.
Regards,
Mark
prev parent reply other threads:[~2018-10-30 6:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 12:25 Bootstrap optimization Mikael Djurfeldt
2018-10-28 1:34 ` Mark H Weaver
2018-10-28 7:24 ` Mikael Djurfeldt
2018-10-28 12:40 ` Mikael Djurfeldt
2018-10-28 22:33 ` Officially require GNU Make to build Guile? (was Re: Bootstrap optimization) Mark H Weaver
2018-10-29 0:12 ` Greg Troxel
2018-10-29 10:33 ` Mikael Djurfeldt
2018-10-30 6:04 ` Mark H Weaver [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7mwkm0e.fsf@netris.org \
--to=mhw@netris.org \
--cc=guile-devel@gnu.org \
--cc=mikael@djurfeldt.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).