From: Stefan Kangas <stefankangas@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: lux <lx@shellcodes.org>, Paul Eggert <eggert@cs.ucla.edu>,
60843@debbugs.gnu.org
Subject: bug#60843: 30.0.50; Build failure on old GNU/Linux system
Date: Tue, 5 Sep 2023 14:11:22 -0700 [thread overview]
Message-ID: <CADwFkmnOF-WtsLbejV7R6e6qOTX5-KbFA8=mnRzZnHGN+ADzeg@mail.gmail.com> (raw)
In-Reply-To: <87k01majuu.fsf@yahoo.com> (Po Lu's message of "Mon, 16 Jan 2023 17:50:49 +0800")
Po Lu <luangruo@yahoo.com> writes:
> lux <lx@shellcodes.org> writes:
>
>> Po Lu <luangruo@yahoo.com> writes:
>>
>>> Since the last gnulib merge, Emacs refuses to build on Fedora 9:
>>>
>>> qcopy-acl.c: In function ‘is_attr_permissions’:
>>> qcopy-acl.c:36: warning: implicit declaration of function ‘attr_copy_action’
>>> qcopy-acl.c:36: error: ‘ATTR_ACTION_PERMISSIONS’ undeclared (first use in this function)
>>> qcopy-acl.c:36: error: (Each undeclared identifier is reported only once
>>> qcopy-acl.c:36: error: for each function it appears in.)
>>>
>>> Would someone please take a look at this? Thanks.
>>
>> Probably because the version of libattr in Fedora 9 is too low, Fedora 9
>> using the libattr-2.4.41, `ATTR_ACTION_PERMISSIONS' is not defined.
>>
>> I see the `ATTR_ACTION_PERMISSIONS' first defined in 2008-05-19
>> (https://git.savannah.nongnu.org/cgit/attr.git/commit/?id=467bbfa56a14c1571082cab2385d272bead78fdc)
>>
>> You can also disable xattr to solve the problem:
>>
>> $ ./configure --disable-xattr
>>
>> I compiled successfully in Fedora 9:
>>
>> [root@localhost emacs]# lsb_release -a
>> LSB Version: :core-3.1-amd64:core-3.1-noarch:graphics-3.1-amd64:graphics-3.1-noarch
>> Distributor ID: Fedora
>> Description: Fedora release 9 (Sulphur)
>> Release: 9
>> Codename: Sulphur
>> [root@localhost emacs]# emacs --version
>> GNU Emacs 30.0.50
>> Copyright (C) 2023 Free Software Foundation, Inc.
>> GNU Emacs comes with ABSOLUTELY NO WARRANTY.
>> You may redistribute copies of GNU Emacs
>> under the terms of the GNU General Public License.
>> For more information about these matters, see the file named COPYING.
>
> Yes, but it should be fixed in gnulib. Emacs should compile cleanly
> without any arguments to configure.
Paul, do you have any comments here?
next prev parent reply other threads:[~2023-09-05 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87o7qz9sy6.fsf.ref@yahoo.com>
2023-01-16 1:19 ` bug#60843: 30.0.50; Build failure on old GNU/Linux system Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-16 6:55 ` lux
2023-01-16 9:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-05 21:11 ` Stefan Kangas [this message]
2023-09-06 0:35 ` Paul Eggert
2023-09-06 2:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-06 6:32 ` Stefan Kangas
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='CADwFkmnOF-WtsLbejV7R6e6qOTX5-KbFA8=mnRzZnHGN+ADzeg@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=60843@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=luangruo@yahoo.com \
--cc=lx@shellcodes.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).