unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Greg Troxel <gdt@lexort.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Officially require GNU Make to build Guile? (was Re: Bootstrap optimization)
Date: Sun, 28 Oct 2018 20:12:32 -0400	[thread overview]
Message-ID: <smush0pehlb.fsf@linuxpal.mit.edu> (raw)
In-Reply-To: <87tvl58zvd.fsf_-_@netris.org> (Mark H. Weaver's message of "Sun,  28 Oct 2018 18:33:47 -0400")


Mark H Weaver <mhw@netris.org> writes:

> Hmm, good question.  I'm not sure, not because 2002 is too recent, but
> rather because I'm not sure that GNU Make should be a requirement for
> building Guile.
>
> Guile's README does not list GNU Make in the section of "Required
> External Packages".  This, along with the fact that we use Automake
> which is clearly designed to produce portable Makefiles, makes me
> inclined to think that if Guile depends on non-standard extensions in
> GNU Make, that this is a bug.

Agreed that requiring GNU Make is a bug.

> On the other hand, if this is a bug, it seems that we've had this bug
> for several years at least, and that non-GNU systems are already working
> around it by adding GNU Make as a requirement.  For example, the Guile 2
> packages in the OpenBSD and FreeBSD ports collections already list GNU
> Make as a prerequisite for building Guile 2.  Our README also has
> "Special Instructions For Some Systems" which mentions that gmake is
> required on FreeBSD 11.0.  However, there's no mention of any other
> non-GNU systems requiring GNU Make to build Guile.

NetBSD's pkgsrc (which is portable to about 20 systems) also is marked
to need GNU make.  Practically, it's not a problem, because packaging
systems have to deal with many programs that require GNU make anway.

> So, we now have a choice.  We can fully embrace a requirement on GNU
> Make, or we can treat it as a bug to be fixed.
>
> I'm still inclined to consider it a bug, but maybe we can have the best
> of both worlds here.  I see that Automake has conditionals:

I am also inclined to see it as a bug.  Generally, most times GNU make
is needed are because someone used an extension without realizing that
there is make other than GNU make, vs it making a huge difference.  But
if it is hard to do things differently, that's somewhat tilting at
windwills.   But hey, that's what running scheme is all about!



  reply	other threads:[~2018-10-29  0:12 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 [this message]
2018-10-29 10:33         ` Mikael Djurfeldt
2018-10-30  6:04           ` Mark H Weaver

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=smush0pehlb.fsf@linuxpal.mit.edu \
    --to=gdt@lexort.com \
    --cc=guile-devel@gnu.org \
    --cc=mhw@netris.org \
    /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).