From: Eli Zaretskii <eliz@gnu.org>
To: Angelo Graziosi <angelo.g0@libero.it>, Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: build failures in mingw64
Date: Sun, 09 Jul 2023 14:19:50 +0300 [thread overview]
Message-ID: <83v8et9vs9.fsf@gnu.org> (raw)
In-Reply-To: <190474050.3639024.1688895205348@mail1.libero.it> (message from Angelo Graziosi on Sun, 9 Jul 2023 11:33:25 +0200 (CEST))
> Date: Sun, 9 Jul 2023 11:33:25 +0200 (CEST)
> From: Angelo Graziosi <angelo.g0@libero.it>
> Cc: emacs-devel@gnu.org
>
>
> { printf "%s\n" "$as_me:${as_lineno-$LINENO}: checking whether MB_CUR_MAX is correct" >&5
> printf %s "checking whether MB_CUR_MAX is correct... " >&6; }
> if test ${gl_cv_macro_MB_CUR_MAX_good+y}
> then :
> printf %s "(cached) " >&6
> else $as_nop
>
> case "$host_os" in
> # Guess no on Solaris.
> solaris*) gl_cv_macro_MB_CUR_MAX_good="guessing no" ;;
> # Guess yes otherwise.
> *) gl_cv_macro_MB_CUR_MAX_good="guessing yes" ;;
> esac
> if test $LOCALE_FR_UTF8 != none; then ### *** LINE 33322 *** ###
> if test "$cross_compiling" = yes
> then :
> :
> else $as_nop
> cat confdefs.h - <<_ACEOF >conftest.$ac_ext
Thanks. This is a Gnulib bug, we've "inherited" it 2 months ago.
Paul, could you please fix this in Gnulib?
next prev parent reply other threads:[~2023-07-09 11:19 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 [this message]
2023-07-09 20:57 ` Paul Eggert
2023-07-09 22:48 ` Angelo Graziosi
2023-07-10 12:28 ` Eli Zaretskii
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=83v8et9vs9.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).