all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
To: bug-gnu-emacs@gnu.org
Subject: bug#3883: Interleaved builds in separate trees create different versions
Date: Sun, 19 Jul 2009 13:02:33 -0700	[thread overview]
Message-ID: <87r5wc30h2.fsf@raven.defaultvalue.org> (raw)


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.  This doesn't happen if
you don't have separate "make" and "make install" steps.

I don't know if this behavior is intentional, but in case it's not, I
thought I'd report it.

You can trivially reproduce the situation with this script (using the
23.0.96 archive), and note that the same thing still happens if you omit
the differing configure arguments:

#!/bin/bash

set -e
set -x

tar xf emacs-23.0.96.tar.gz

mkdir -p build/1
mkdir -p build/2

(cd build/1 && ../../emacs-23.0.96/configure --with-x=yes)
(cd build/2 && ../../emacs-23.0.96/configure --with-x=no)

(cd build/1 && make)
(cd build/2 && make)

mkdir -p install/1
mkdir -p install/2

inst_1="$(pwd)/install/1"
inst_2="$(pwd)/install/2"

(cd build/1 && make DESTDIR="${inst_1}")
(cd build/2 && make DESTDIR="${inst_2}")

find -name "emacs-23.*"
find -name "DOC*"

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4






             reply	other threads:[~2009-07-19 20:02 UTC|newest]

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

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=87r5wc30h2.fsf@raven.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=3883@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@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.