From: jca+emacs@wxcvbn.org (Jérémie Courrèges-Anglas)
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: emacs-devel@gnu.org, Darren Hoo <darren.hoo@gmail.com>
Subject: Re: build emacs outside of the source directory
Date: Thu, 14 Mar 2013 06:50:37 +0100 [thread overview]
Message-ID: <87vc8u4jiq.fsf@moo.wxcvbn.org> (raw)
In-Reply-To: <mvmk3pjmkc9.fsf@hawking.suse.de> (Andreas Schwab's message of "Thu, 07 Mar 2013 14:05:10 +0100")
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
Andreas Schwab <schwab@linux-m68k.org> writes:
> Darren Hoo <darren.hoo@gmail.com> writes:
>
>> The built object files for emacs/{src,lib,lib-src} all go to
>> build/{src,lib,lib-src}, but the *.elc files are not, they still lie in
>> the emacs/lisp diretory.
>
> That is correct, because these files are distributed, so when building
> from a tarball they are not touched.
Is that true? I haven't tried to investigate yet, but they are actually
rebuilt here (24.3 tarball). This makes me suspicious about using
a single source directory for the four emacs flavors we ship in the
OpenBSD ports tree - thinking of two or more emacs processes writing the
same .elc at the same time.
> Andreas.
--
Jérémie Courrèges-Anglas - OpenBSD Emacs port maintainer
GPG Key fingerprint: 61DB D9A0 00A4 67CF 2A90 8961 6191 8FBF 06A1 1494
[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2013-03-14 5:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2li9zwicn.fsf@darren.hoo@gmail.com>
2013-03-07 13:05 ` build emacs outside of the source directory Andreas Schwab
2013-03-14 5:50 ` Jérémie Courrèges-Anglas [this message]
2013-03-07 22:54 ` Stephen J. Turnbull
2013-03-08 7:36 ` Xue Fuqiao
2013-03-07 11:38 Darren Hoo
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=87vc8u4jiq.fsf@moo.wxcvbn.org \
--to=jca+emacs@wxcvbn.org \
--cc=darren.hoo@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.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.