unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Building Emacs out of source tree?
Date: Sun, 17 Mar 2024 20:24:28 +0100	[thread overview]
Message-ID: <ZfdDbPqafdsVwx+1@tuxteam.de> (raw)
In-Reply-To: <864jd554ck.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2088 bytes --]

On Sun, Mar 17, 2024 at 04:18:35PM +0200, Eli Zaretskii wrote:
> > 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.

Thanks for confirming.

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

Good question. I was surprised myself -- anyway, copying chartab.o
from <source>/src/ (why was it there in the first place?) to
<build>src/ let the build continue, until...

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

It is GNU/Linux, yes, and this was my take too, since "my" libc
does carry a chmodat.

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

Thing is, in-tree build (after a make bootstrap) succeeds right
away. Out of tree builds (also after make bootstrap) failed for
me as described above.

So I'll definitely have a look. Next week is a bit busy, so it
might take me until weekend.

Thanks for confirming that (a) out-of-tree build is supposed to
work and (b) there is interest in knowing when it doesn't.

Cheers
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2024-03-17 19:24 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 [this message]
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=ZfdDbPqafdsVwx+1@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).