From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Building Emacs out of source tree?
Date: Tue, 19 Mar 2024 07:18:38 +0100 [thread overview]
Message-ID: <623d6924-170a-4005-a84f-78a32a89e121@easy-emacs.de> (raw)
In-Reply-To: <Zfbn/VHVvJ5UElC4@tuxteam.de>
I'm running autogen.sh first, then .configure
Am 17.03.24 um 13:54 schrieb tomas@tuxteam.de:
> 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
next prev parent reply other threads:[~2024-03-19 6:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 12:54 Building Emacs out of source tree? tomas
2024-03-17 14:18 ` 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 [this message]
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=623d6924-170a-4005-a84f-78a32a89e121@easy-emacs.de \
--to=andreas.roehler@easy-emacs.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).