unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Building Emacs out of source tree?
Date: Sun, 17 Mar 2024 16:18:35 +0200	[thread overview]
Message-ID: <864jd554ck.fsf@gnu.org> (raw)
In-Reply-To: <Zfbn/VHVvJ5UElC4@tuxteam.de> (tomas@tuxteam.de)

> Date: Sun, 17 Mar 2024 13:54:21 +0100
> From: <tomas@tuxteam.de>
> 
> 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.

That is the correct way.

> 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

How come?  chartab.c is just one of the source files, and is not
mentioned specially in any Makefile, AFAICT.  Why is that file somehow
missing, and others aren't?  Please investigate why.  (Could it be
your src tree was not clean of all the *.o files?)

> - one missing symbol rpl_chmodat; this gets defined in
>   some header -- sneaking a strategically placed
> 
>     #undef rpl_chmodat

If this is on GNU/Linux, then you shouldn't need to have any
rpl_chmodat anywhere.  I just searched my source/build tree on
GNU/Linux, and didn't find rpl_chmodat anywhere.  So once again,
please investigate.

And in any case, this doesn't seem to have anything to do with
out-of-tree builds, does it?

> 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?

Of course we do.  They are supported and should continue to be
supported.



  reply	other threads:[~2024-03-17 14: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 [this message]
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=864jd554ck.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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).