From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Building Emacs out of source tree?
Date: Sun, 17 Mar 2024 13:54:21 +0100 [thread overview]
Message-ID: <Zfbn/VHVvJ5UElC4@tuxteam.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]
Hello, Emacs
after a while, I'm trying again to pick up the custom of
compiling Emacs.
Usually, I compiled in an empty build directory, invoking
../emacs/configure.
This used to work pretty well but doesn't seem to these
days. I hit two-and-a-half snags:
- one missing chartab.o which happened to lie around
in the source dir under src; copying it over to the
corresponding spot in the build dir let the build
continue
- one missing symbol rpl_chmodat; this gets defined in
some header -- sneaking a strategically placed
#undef rpl_chmodat
let the build process continue (and now comes te half
snag: pdump dumped core -- that's what you get for
messing with things you only half-understand :)
Building in-source Just Works and produces an installable
Emacs which, prima vista behaves in a civilised manner.
It's a recent git pull, off the "master" branch:
7a0f4de3c18 (HEAD -> master) Improve C++ standard library detection on Android
Now I'd be willing to gather more details for a bug report if
there is an interest in keeping out of source tree compiles
viable; for me those aren't that crucial anymore, with the
advent of git and of 1TB+ disks.
What do you think? Do we still care for out of source builds?
Cheers
--
tomás
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next reply other threads:[~2024-03-17 12:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 12:54 tomas [this message]
2024-03-17 14:18 ` Building Emacs out of source tree? Eli Zaretskii
2024-03-17 17:53 ` Basile Starynkevitch
2024-03-17 19:33 ` tomas
2024-03-17 19:24 ` tomas
2024-03-18 8:25 ` Robert Pluim
2024-03-18 8:50 ` tomas
2024-03-18 13:27 ` Eli Zaretskii
2024-03-18 13:59 ` tomas
2024-03-19 6:18 ` Andreas Röhler
2024-03-20 5:41 ` SOLVED [was: Building Emacs out of source tree?] tomas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zfbn/VHVvJ5UElC4@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).