all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: emacs-devel@gnu.org
Subject: Re: require GNU make to build emacs?
Date: Mon, 25 Feb 2008 22:29:15 +0200	[thread overview]
Message-ID: <utzjwlqzo.fsf@gnu.org> (raw)
In-Reply-To: <200802250522.m1P5Mf94012696@sallyv1.ics.uci.edu> (message from Dan Nicolaescu on Sun, 24 Feb 2008 21:22:41 -0800)

> From: Dan Nicolaescu <dann@ics.uci.edu>
> Cc: emacs-devel@gnu.org
> Date: Sun, 24 Feb 2008 21:22:41 -0800
> 
> Yes, IMO there's a good reason.  Being able to use conditionals,
> includes, and other advanced features should allow us to avoid using the
> C preprocessor to create Makefiles

The way to avoid using cpp is to autoconfiscate our configury, so that
the configure script produces src/Makefile from src/Makefile.in.  (Not
that I think this is such an urgent task, given that the current setup
works so well and that the rate of new OSes and/or changes in the
existing OSes is so low lately.)

> and to make the bootstrap a bit more reliable (we have way too many
> parallel make failures and other flakiness).

Failures with parallel builds are probably due to little use, not
non-GNU Make.  Most, if not all, of those I remember were fixed easily
by adding missing dependencies.  But if you have specific examples for
these problems, by all means post them.

>   > > Having a modern make should help simplify the makefiles and maybe the
>   > > whole build process.
>   > 
>   > Is that the only reason, or are there real problems with non-GNU Make
>   > in our build process?
> 
> The fact that we only use the most basic make features is a problem.

Again, specific problems, beyond those solved by autoconf, would be
appreciated.




  reply	other threads:[~2008-02-25 20:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-24 23:44 require GNU make to build emacs? Dan Nicolaescu
2008-02-25  2:38 ` Stefan Monnier
2008-02-25  2:52   ` Dan Nicolaescu
2008-02-25  4:19     ` Stefan Monnier
2008-02-25  4:29 ` Eli Zaretskii
2008-02-25  5:22   ` Dan Nicolaescu
2008-02-25 20:29     ` Eli Zaretskii [this message]
2008-02-26  1:09       ` Dan Nicolaescu
2008-02-26  4:15         ` Eli Zaretskii
2008-02-26  2:00     ` Xavier Maillard
2008-02-25 19:01 ` Richard Stallman

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=utzjwlqzo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.