From: Paul Eggert <eggert@cs.ucla.edu>
To: Andrea Corallo <akrl@sdf.org>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: Rajeev N <rajeev.jnk@sivalik.com>,
Emacs Development <Emacs-devel@gnu.org>
Subject: Re: emacs-28 build failure - gnulib
Date: Tue, 5 Oct 2021 09:24:23 -0700 [thread overview]
Message-ID: <830dd541-56f8-0864-b8e6-8af5c004ce0e@cs.ucla.edu> (raw)
In-Reply-To: <xjfzgrnc2wd.fsf@ma.sdf.org>
On 10/5/21 1:05 AM, Andrea Corallo wrote:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> Yes, it seems like --native-compilation builds are failing after the
>> gnulib update; Paul added to the CCs.
I think I've now fixed that on the emacs-28 branch; see:
https://bugs.gnu.org/50985#44
> make -C lib all
> make[1]: Entering directory '/home/akrl/emacs2/lib'
> CC fchmodat.o
> In file included from fchmodat.c:40:
> ./stdlib.h:783:1: error: wrong number of arguments specified for ‘malloc’ attribute
> 783 | _GL_FUNCDECL_SYS (aligned_alloc, void *,
> | ^~~~~~~~~~~~~~~~
> ./stdlib.h:783:1: note: expected between 0 and 0, found 2
This looks like detritus from a previous build. I've run into that
problem myself. Please try 'make bootstrap', or start over from a fresh
Git checkout.
next prev parent reply other threads:[~2021-10-05 16:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 1:51 emacs-28 build failure - gnulib Rajeev N via Emacs development discussions.
2021-10-05 7:25 ` Lars Ingebrigtsen
2021-10-05 8:05 ` Andrea Corallo via Emacs development discussions.
2021-10-05 16:24 ` Paul Eggert [this message]
2021-10-05 16:53 ` Andrea Corallo via Emacs development discussions.
2021-10-05 18:24 ` Paul Eggert
2021-10-05 18:51 ` Andreas Schwab
2021-10-05 19:08 ` Paul Eggert
2021-10-05 19:50 ` Andreas Schwab
2021-10-05 12:50 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2021-10-06 5:34 Manuel Uberti
2021-10-06 8:20 ` Andrea Corallo via Emacs development discussions.
2021-10-06 8:23 ` Manuel Uberti
2021-10-06 8:56 ` Robert Pluim
2021-10-06 8:57 ` Manuel Uberti
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=830dd541-56f8-0864-b8e6-8af5c004ce0e@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=Emacs-devel@gnu.org \
--cc=akrl@sdf.org \
--cc=larsi@gnus.org \
--cc=rajeev.jnk@sivalik.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).