From: Basile Starynkevitch <basile@starynkevitch.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Building Emacs out of source tree?
Date: Sun, 17 Mar 2024 18:53:59 +0100 [thread overview]
Message-ID: <0091d885-6904-475a-8e46-956756cf0057@starynkevitch.net> (raw)
In-Reply-To: <864jd554ck.fsf@gnu.org>
On 3/17/24 15:18, Eli Zaretskii wrote:
> 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.
I actually am git pulling and buiding GNU emacs on Linux Debian/x86-64
(inside its source tree) more than twice a week.
(Why do you want to build it outside of source tree?)
Very often it build and works ok.
> rimski.x86_64 % /usr/local/bin/emacs-30.0.50 --version GNU Emacs
> 30.0.50 Development version ad3a3ad6e616 on master branch; build date
> 2024-03-16. Copyright (C) 2024 Free Software Foundation, Inc. GNU
> Emacs comes with ABSOLUTELY NO WARRANTY. You may redistribute copies
> of GNU Emacs under the terms of the GNU General Public License. For
> more information about these matters, see the file named COPYING.
Thanks
--
Basile Starynkevitch<basile@starynkevitch.net>
(only mine opinions / les opinions sont miennes uniquement)
92340 Bourg-la-Reine, France
web page: starynkevitch.net/Basile/
See/voir:https://github.com/RefPerSys/RefPerSys
next prev parent reply other threads:[~2024-03-17 17:53 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 [this message]
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=0091d885-6904-475a-8e46-956756cf0057@starynkevitch.net \
--to=basile@starynkevitch.net \
--cc=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).