From: Eli Zaretskii <eliz@gnu.org>
To: Angelo Graziosi <angelo.g0@libero.it>, Paul Eggert <eggert@cs.ucla.edu>
Cc: 61782@debbugs.gnu.org
Subject: bug#61782: About some warning building Emacs master on MSYS2/MINGW64 [autogen, configure]
Date: Sat, 25 Feb 2023 11:49:39 +0200 [thread overview]
Message-ID: <83edqekrbg.fsf@gnu.org> (raw)
In-Reply-To: <599015321.1234711.1677314756067@mail1.libero.it> (message from Angelo Graziosi on Sat, 25 Feb 2023 09:45:56 +0100 (CET))
> Date: Sat, 25 Feb 2023 09:45:56 +0100 (CET)
> From: Angelo Graziosi <angelo.g0@libero.it>
>
> I noticed that building Emacs (master) on Windows with MSYS2/MINGW64 now shows these warnings
>
> $ ./autogen.sh
> [...]
> Running 'autoreconf -fi -I m4' ...
> ac-wrapper: autoreconf: warning: auto-detected versions not found ( ); falling back to latest available
> You can now run './configure'.
>
> ./configure
> [...]
> checking for xattr library with ATTR_ACTION_PERMISSIONS... no
> configure: WARNING: libattr development library was not found or not usable.
> configure: WARNING: GNU Emacs will be built without xattr support.
> checking whether readlink signature is correct... yes
> [...]
>
> I wonder if they are to be expected and if we can do something to avoid them.
The first one doesn't happen here.
The second one is due to m4/xattr.m4. Paul, this test should not be
run on MS-Windows (although running it is mostly harmless), as xattr
will not be supported there.
next prev parent reply other threads:[~2023-02-25 9:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 8:45 bug#61782: About some warning building Emacs master on MSYS2/MINGW64 [autogen, configure] Angelo Graziosi
2023-02-25 9:49 ` Eli Zaretskii [this message]
2023-02-25 16:51 ` Angelo Graziosi
2023-02-25 17:17 ` Eli Zaretskii
2023-02-25 23:38 ` Paul Eggert
2023-02-26 6:56 ` Eli Zaretskii
2023-02-26 21:34 ` Angelo Graziosi
2023-02-27 11:13 ` Eli Zaretskii
2023-02-27 20:41 ` Paul Eggert
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=83edqekrbg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61782@debbugs.gnu.org \
--cc=angelo.g0@libero.it \
--cc=eggert@cs.ucla.edu \
/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).