From: "Bernhard M. Wiedemann" <bernhardout@lsmod.de>
To: emacs-devel@gnu.org
Subject: Re: emacs reproducible builds part1 of 2 : eln
Date: Fri, 31 May 2024 10:22:15 +0200 [thread overview]
Message-ID: <32f589fe-7c9f-4d0c-b058-f2bea843e5d5@lsmod.de> (raw)
In-Reply-To: <yp1r0dipgrs.fsf@fencepost.gnu.org>
On 31/05/2024 09.44, Andrea Corallo wrote:
> Ouch I'm not sure there will ever be a 29.4... Eli?
A 30.0 release would also be fine, if it happens this year.
> Bernhard trying master is not an option?
not that easy. My test-tools expect a .spec file that builds rpms.
When I try to use master and use an adapted 29.3 .spec file I get either
autoreconf errors or using the (old?) configure
No rule to make target '@STDBIT_H@', needed by 'fingerprint.o'.
autoreconf errors were:
autoreconf: running: /usr/bin/autoconf
--include=/home/abuild/rpmbuild/BUILD/emacs-29.3
--include=/home/abuild/rpmbuild/BUILD/emacs-29.3/m4 --force
configure.ac:6405: warning: AM_LANGINFO_CODESET is m4_require'd but
not m4_defun'd
configure.ac:6391: EMACS_PAPER_WIDTH is expanded from...
configure.ac:6405: the top level
configure.ac:7382: warning: gl_STDBIT_H is m4_require'd but not m4_defun'd
m4/gnulib-comp.m4:225: gl_INIT is expanded from...
configure.ac:7382: the top level
configure.ac:6392: error: possibly undefined macro: AM_LANGINFO_CODESET
If this token and others are legitimate, please use
m4_pattern_allow.
See the Autoconf documentation.
configure:35948: error: possibly undefined macro: gl_STDBIT_H
configure:36429: error: possibly undefined macro: gl_MUSL_LIBC
configure:38427: error: possibly undefined macro: gl_PREREQ_READUTMP_H
configure:41153: error: possibly undefined macro: gl_FUNC_GETLINE
configure:41165: error: possibly undefined macro: gl_PREREQ_GETLINE
configure:42944: error: possibly undefined macro: gl_FUNC_MEMSET_EXPLICIT
configure:42956: error: possibly undefined macro:
gl_PREREQ_MEMSET_EXPLICIT
configure:44134: error: possibly undefined macro: gl_FUNC_XATTR
configure:47673: error: possibly undefined macro: gl_FUNC_GETDELIM
configure:47685: error: possibly undefined macro: gl_PREREQ_GETDELIM
autoreconf: error: /usr/bin/autoconf failed with exit status: 1
error: Bad exit status from /var/tmp/rpm-tmp.v5UOFL (%build)
Ciao
Bernhard M.
next prev parent reply other threads:[~2024-05-31 8:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 21:17 emacs reproducible builds part1 of 2 : eln Bernhard M. Wiedemann
2024-01-12 8:22 ` Eli Zaretskii
2024-01-12 16:19 ` Andrea Corallo
2024-01-12 16:26 ` Eli Zaretskii
2024-01-13 9:52 ` Andrea Corallo
2024-02-10 16:35 ` Andrea Corallo
2024-02-10 17:45 ` Stefan Monnier
2024-02-10 18:31 ` Andrea Corallo
2024-02-10 18:44 ` Stefan Monnier
2024-02-10 20:37 ` Andrea Corallo
2024-02-11 10:24 ` Andrea Corallo
2024-02-11 20:13 ` Stefan Monnier
2024-02-11 21:44 ` Andrea Corallo
2024-05-22 6:06 ` Bernhard M. Wiedemann
2024-05-22 12:31 ` Eli Zaretskii
2024-05-27 17:33 ` Andrea Corallo
2024-05-28 15:20 ` Andrea Corallo
2024-05-31 7:26 ` Bernhard M. Wiedemann
2024-05-31 7:44 ` Andrea Corallo
2024-05-31 8:22 ` Bernhard M. Wiedemann [this message]
2024-05-31 10:45 ` Eli Zaretskii
2024-05-31 10:33 ` Eli Zaretskii
2024-01-12 16:14 ` Simon Tournier
2024-01-12 20:13 ` Eli Zaretskii
2024-02-12 7:10 ` Björn Bidar
[not found] ` <87il2ub1jy.fsf@>
2024-02-12 8:17 ` Andrea Corallo
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=32f589fe-7c9f-4d0c-b058-f2bea843e5d5@lsmod.de \
--to=bernhardout@lsmod.de \
--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).