From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: angelo.g0@libero.it, emacs-devel@gnu.org
Subject: Re: build failures in mingw64
Date: Mon, 10 Jul 2023 15:28:33 +0300 [thread overview]
Message-ID: <83v8es7xxq.fsf@gnu.org> (raw)
In-Reply-To: <2ed1361e-9cf1-fb25-14bf-ee634aaf9382@cs.ucla.edu> (message from Paul Eggert on Sun, 9 Jul 2023 13:57:25 -0700)
> Date: Sun, 9 Jul 2023 13:57:25 -0700
> Cc: emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
>
> On 2023-07-09 04:19, Eli Zaretskii wrote:
> > This is a Gnulib bug, we've "inherited" it 2 months ago.
>
> Odd, that could happen if one ran 'configure' with an unusual argument,
> e.g., './configure gt_cv_locale_fr=', but I don't see how it could
> happen otherwise.
>
> The configure-time test for French locales is present only to work
> around a Solaris 10 bug, and looking into that bug I don't see how it
> could affect Emacs.
AFAIR, Gnulib-generated configure scripts always check for the French
locale, for whatever reasons.
> So I installed the attached patches to bring Emacs
> up to speed on recent Gnulib (I fixed Gnulib to handle the "unusual
> argument" issue), and to remove the unnecessary-for-Emacs French locale
> testing so this should work around whatever obscure issue Angelo ran
> into. Please give it a try.
But shouldn't LOCALE_FR_UTF8 be quoted in the below fragment?
if test $LOCALE_FR_UTF8 != none; then
if test "$cross_compiling" = yes; then :
This is still present in the configure script regenerated after your
changes on master.
Thanks.
next prev parent reply other threads:[~2023-07-10 12:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 8:05 build failures in mingw64 Angelo Graziosi
2023-07-09 8:51 ` Eli Zaretskii
2023-07-09 9:33 ` Angelo Graziosi
2023-07-09 10:01 ` Angelo Graziosi
2023-07-09 11:22 ` Eli Zaretskii
2023-07-09 11:19 ` Eli Zaretskii
2023-07-09 20:57 ` Paul Eggert
2023-07-09 22:48 ` Angelo Graziosi
2023-07-10 12:28 ` Eli Zaretskii [this message]
2023-07-10 17:00 ` Paul Eggert
2023-07-10 23:40 ` Angelo Graziosi
2023-07-09 16:17 ` Stephen Leake
-- strict thread matches above, loose matches on Subject: below --
2023-07-08 21:50 Stephen Leake
2023-07-09 5:58 ` Eli Zaretskii
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=83v8es7xxq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=angelo.g0@libero.it \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@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.
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).