all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Rob Browning <rlb@defaultvalue.org>, emacs-devel@gnu.org
Subject: Re: Possibility of a ${srcdir}/info/dir target race?
Date: Thu, 23 Oct 2014 01:38:07 -0400	[thread overview]
Message-ID: <mka94n4a80.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <544878F7.6020708@cs.ucla.edu> (Paul Eggert's message of "Wed, 22 Oct 2014 20:41:43 -0700")

Paul Eggert wrote:

> I fixed this bug in trunk bzr 118181, along with another bug
> (wildcards weren't expanded in dependencies) and some performance
> tuneups.  It's not urgent to apply these changes to the emacs-24
> branch as the problems shouldn't occur when building from an Emacs
> source distribution.

Surely the actual relevant change is only to add ${MKDIR_P}
${srcdir}/info, which could easily have been applied to emacs-24, only
it's mixed in with unrelated performance improvements?

And the "wildcards" thing is only relevant if you've deleted
every texi file from doc/misc (which even Debian doesn't do)?
Similar constructs have been used for years in eg lisp/Makefile.in
lisptagsfiles etc.



  parent reply	other threads:[~2014-10-23  5:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22 19:13 Possibility of a ${srcdir}/info/dir target race? Rob Browning
2014-10-22 20:11 ` Stefan Monnier
2014-10-22 21:22   ` Glenn Morris
2014-10-22 23:18     ` Rob Browning
2014-10-22 23:55   ` Rob Browning
2014-10-23  3:41     ` Paul Eggert
2014-10-23  5:32       ` Glenn Morris
2014-10-23  5:49         ` Glenn Morris
2014-10-23 15:20           ` Rob Browning
2014-10-23  5:38       ` Glenn Morris [this message]
2014-10-23  6:36         ` Paul Eggert
2014-10-23 15:22         ` Rob Browning
2014-10-23 15:43       ` Rob Browning

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=mka94n4a80.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=rlb@defaultvalue.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.