From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: luangruo@yahoo.com, emacs-devel@gnu.org
Subject: Re: feature/android 83eeebe9ef2: Merge remote-tracking branch 'origin/master' into feature/android
Date: Mon, 19 Jun 2023 19:49:25 +0300 [thread overview]
Message-ID: <83zg4v75yi.fsf@gnu.org> (raw)
In-Reply-To: <87o7lbdedh.fsf@gmail.com> (message from Robert Pluim on Mon, 19 Jun 2023 10:51:06 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Mon, 19 Jun 2023 10:51:06 +0200
>
> >>>>> On Mon, 19 Jun 2023 16:41:28 +0800, Po Lu <luangruo@yahoo.com> said:
>
> Po Lu> Robert Pluim <rpluim@gmail.com> writes:
> >>>>>>> On Mon, 19 Jun 2023 16:18:31 +0800, Po Lu <luangruo@yahoo.com> said:
> >>
> >> Po Lu> Does this fix the problem?
> >>
> >> Yes, although the resulting emacs now interposes rpl_vfprintf and rpl_printf
> >> instead of the glibc functions. Why is that suddenly necessary?
>
> Po Lu> Because Gnulib has detected that [vasn]printf aren't POSIX or C23
> Po Lu> compliant. It's not possible to avoid using Gnulib replacement
> Po Lu> functions in lib-src, as long as the headers there include config.h.
>
> But master doesnʼt do that. Or is this branch using a newer version of
> gnulib?
Can you show the failed test program and the error messages? Maybe we
should take this up with the Gnulib developers. AFAIU, modern
GNU/Linux systems which use new enough glibc aren't supposed to
require replacements of library functions.
next prev parent reply other threads:[~2023-06-19 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <168713616877.28101.8095250217334338322@vcs2.savannah.gnu.org>
[not found] ` <20230619005609.28E56C19263@vcs2.savannah.gnu.org>
2023-06-19 8:14 ` feature/android 83eeebe9ef2: Merge remote-tracking branch 'origin/master' into feature/android Robert Pluim
2023-06-19 8:18 ` Po Lu
2023-06-19 8:38 ` Robert Pluim
2023-06-19 8:41 ` Po Lu
2023-06-19 8:51 ` Robert Pluim
2023-06-19 16:49 ` Eli Zaretskii [this message]
2023-06-20 0:54 ` Po Lu
2023-06-20 8:03 ` Robert Pluim
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=83zg4v75yi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--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.
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).