unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: tomas@tuxteam.de
To: Robert Pluim <rpluim@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Building Emacs out of source tree?
Date: Mon, 18 Mar 2024 09:50:33 +0100	[thread overview]
Message-ID: <ZfgAWR94CEirdYug@tuxteam.de> (raw)
In-Reply-To: <87h6h4t09f.fsf@gmail.com>

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

On Mon, Mar 18, 2024 at 09:25:16AM +0100, Robert Pluim wrote:
> >>>>> On Sun, 17 Mar 2024 20:24:28 +0100, <tomas@tuxteam.de> said:

[...]

>     Tomas> It is GNU/Linux, yes, and this was my take too, since "my" libc
>     Tomas> does carry a chmodat.
> 
> That in itself doesnʼt mean gnulib wonʼt try to replace it: sometimes
> gnulib deems libc versions of functions buggy and wraps them. But I
> donʼt see that for chmodat on my GNU/Linux box.
> 
>     >> And in any case, this doesn't seem to have anything to do with
>     >> out-of-tree builds, does it?
> 
>     Tomas> Thing is, in-tree build (after a make bootstrap) succeeds right
>     Tomas> away. Out of tree builds (also after make bootstrap) failed for
>     Tomas> me as described above.
> 
> Did you build in-tree and then build out-of-tree? Maybe 'make
> bootstrap' in that situation is missing some cleanup.

AFAIR, I first built out-of-tree after a "git pull" (I didn't a "git
clean", so the src tree might have been dirty [1]), then copied that
chartab.o, then #undef'd. After a "make bootstrap" (still out-of-tree)
the first issue (chartab.o) returned.

That's when I resorted to in-tree build, first "make bootstrap" then
"make", which succeeded right away.

Take all of this with a grain of salt, though: I'll do a more systematic
rehearsal this weekend, hopefully.

>     Tomas> So I'll definitely have a look. Next week is a bit busy, so it
>     Tomas> might take me until weekend.
> 
>     Tomas> Thanks for confirming that (a) out-of-tree build is supposed to
>     Tomas> work and (b) there is interest in knowing when it doesn't.
> 
> Yes to both (and it works fine for me).

Thanks, Robert. I'm reporting back :)

Cheers

[1] Since I've been doing out-of-tree all the time, there's no reason
   for the src tree to be dirty (famous last...).

-- 
t

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

  reply	other threads:[~2024-03-18  8:50 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 [this message]
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=ZfgAWR94CEirdYug@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=help-gnu-emacs@gnu.org \
    --cc=rpluim@gmail.com \
    /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).