From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: stefankangas@gmail.com, emacs-devel@gnu.org
Subject: Re: master bdb13a0e5c5 1/2: Adjust to Gnulib’s recent module renaming
Date: Fri, 03 Jan 2025 22:01:39 +0200 [thread overview]
Message-ID: <86y0zrfyzg.fsf@gnu.org> (raw)
In-Reply-To: <71e9d8d5-ae3b-4687-bd75-58c0c5013196@cs.ucla.edu> (message from Paul Eggert on Fri, 3 Jan 2025 11:06:38 -0800)
> Date: Fri, 3 Jan 2025 11:06:38 -0800
> Cc: stefankangas@gmail.com, emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
>
> On 2025-01-02 22:42, Eli Zaretskii wrote:
> > Could you elaborate on what you had in mind?
>
> I don't have anything special or genius or anything like that in mind.
> Just the feeling that it could be done without nt/gnulib-cfg.mk. Perhaps
> by goosing configure's cache variables, as nt/mingw-cfg.site already
> does. Or perhaps in some other way. Feel free to ignore my inkling.
Setting configure's cache variables is a more troublesome method than
omitting modules. First, Gnulib and Autoconf rename these variables
from time to time, which requires constant vigilance and followup
changes. More importantly, understanding which Autoconf-determined
variable(s) need to be tweaked to force the configure script arrive at
the desired result is anything but simple.
prev parent reply other threads:[~2025-01-03 20:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2001.1735773573.32144.emacs-diffs@gnu.org>
2025-01-02 17:30 ` master bdb13a0e5c5 1/2: Adjust to Gnulib’s recent module renaming Eli Zaretskii
2025-01-02 17:57 ` Stefan Kangas
2025-01-02 19:38 ` Paul Eggert
2025-01-02 20:30 ` Eli Zaretskii
2025-01-02 21:15 ` Paul Eggert
2025-01-03 6:42 ` Eli Zaretskii
2025-01-03 19:06 ` Paul Eggert
2025-01-03 20:01 ` Eli Zaretskii [this message]
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=86y0zrfyzg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=stefankangas@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).