all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Rob Browning <rlb@defaultvalue.org>
Cc: 3883@debbugs.gnu.org
Subject: bug#3883: Interleaved builds in separate trees create different versions
Date: Wed, 06 Apr 2011 18:02:30 -0400	[thread overview]
Message-ID: <t4y63n9gy1.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87r5wc30h2.fsf@raven.defaultvalue.org> (Rob Browning's message of "Sun, 19 Jul 2009 13:02:33 -0700")

(A very delayed reply)

Rob Browning wrote:

> If you try to build two trees from the same source directory at the
> same time, alternating the respective SRCDIR/configure, make, and make
> install operations, the first tree will end up with a ".2" version while
> the second tree will end up with a ".1" version.

I think this happens because the second make recompiles the .el files,
and the output .elc files are written into the lisp/ directory in the
source-tree, not the build directory. Then the first build thinks it
need to redump Emacs, because the .elc files have newer timestamps.

Neither make should need to compile the .el files at all, but this is
tricky, see http://debbugs.gnu.org/cgi/bugreport.cgi?bug=2151 .

Arguably, the compiled .elc files should be written into the build
tree's lisp/ directory, not the source lisp/ directory.
But, they are supposed to be platform independent, so maybe the current
set-up is designed to let them be shared between all builds.
But, they get recompiled anyway, so that doesn't actually work...





      reply	other threads:[~2011-04-06 22:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-19 20:02 bug#3883: Interleaved builds in separate trees create different versions Rob Browning
2011-04-06 22:02 ` Glenn Morris [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=t4y63n9gy1.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=3883@debbugs.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.