From: Adolf Belka <adolf.belka@ipfire.org>
To: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: New version of gettext is causing fireperf to fail to build
Date: Tue, 13 May 2025 16:12:13 +0200 [thread overview]
Message-ID: <1b4d9025-5b3c-4af0-8f75-b2b691e9e6f8@ipfire.org> (raw)
Hi All,
I am running some package updates and one of those was gettext from 0.24 to 0.25
gettext built without any problems but when the build got to fireperf it failed. Restoring gettext to the 0.24 version caused fireperf to build without any problems.
The fireperf build log content was:-
May 13 13:19:31: Building fireperf make: Entering directory '/home/build/sandbox/ipfire-2.x/lfs'
make: Nothing to be done for 'download'.
make: Leaving directory '/home/build/sandbox/ipfire-2.x/lfs'
make: Entering directory '/usr/src/lfs'
fireperf-0.2.0.tar.gz checksum OK
====================================== Installing fireperf-0.2.0 ...
Install started; saving file list to /usr/src/lsalr ...
fireperf-0.2.0/
fireperf-0.2.0/.gitignore
fireperf-0.2.0/Makefile.am
fireperf-0.2.0/autogen.sh
fireperf-0.2.0/configure.ac
fireperf-0.2.0/debian/
fireperf-0.2.0/debian/build.sh
fireperf-0.2.0/debian/changelog
fireperf-0.2.0/debian/compat
fireperf-0.2.0/debian/control
fireperf-0.2.0/debian/copyright
fireperf-0.2.0/debian/rules
fireperf-0.2.0/m4/
fireperf-0.2.0/m4/.gitignore
fireperf-0.2.0/man/
fireperf-0.2.0/man/.gitignore
fireperf-0.2.0/man/asciidoc.conf
fireperf-0.2.0/man/fireperf.txt
fireperf-0.2.0/po/
fireperf-0.2.0/po/.gitignore
fireperf-0.2.0/po/POTFILES.in
fireperf-0.2.0/src/
fireperf-0.2.0/src/.gitignore
fireperf-0.2.0/src/client.c
fireperf-0.2.0/src/client.h
fireperf-0.2.0/src/logging.c
fireperf-0.2.0/src/logging.h
fireperf-0.2.0/src/main.c
fireperf-0.2.0/src/main.h
fireperf-0.2.0/src/random.c
fireperf-0.2.0/src/random.h
fireperf-0.2.0/src/server.c
fireperf-0.2.0/src/server.h
fireperf-0.2.0/src/util.c
fireperf-0.2.0/src/util.h
cd /usr/src/fireperf-0.2.0 && ./autogen.sh
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
libtoolize: linking file 'build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: linking file 'm4/libtool.m4'
libtoolize: linking file 'm4/ltoptions.m4'
libtoolize: linking file 'm4/ltsugar.m4'
libtoolize: linking file 'm4/ltversion.m4'
libtoolize: linking file 'm4/lt~obsolete.m4'
You should update your 'aclocal.m4' by running aclocal.
intltoolize: 'po/Makefile.in.in' exists: use '--force' to overwrite
configure.ac:21: warning: The macro 'AC_PROG_CC_STDC' is obsolete.
configure.ac:21: You should run autoupdate.
./lib/autoconf/c.m4:1669: AC_PROG_CC_STDC is expanded from...
configure.ac:21: the top level
configure.ac:32: warning: AM_NLS is m4_require'd but not m4_defun'd
m4/intltool.m4:27: IT_PROG_INTLTOOL is expanded from...
configure.ac:32: the top level
configure:13968: error: possibly undefined macro: AM_NLS
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
autoreconf: error: /usr/bin/autoconf failed with exit status: 1
make: *** [fireperf:84: /usr/src/log/fireperf-0.2.0] Error 1
make: Leaving directory '/usr/src/lfs'
I found the following in the 0.24.1 version changelog
* Bug fixes:
- Fix bad interactions between autoreconf and autopoint.
and the following bug in gettext "bug #67090: autotools issue with gettext-tools 0.24.1"
with the conclusion
I have now added a piece of documentation that clarifies how to obtain the autoconf macros, and that autoreconf is discouraged for this purpose:
https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=commitdiff;h=43f5ac51ddeb1b70a7b9647cb45cfeee67fd8c41
fireperf is using autogen.sh to create the configure file and it runs autoreconf.
It looks like with the latest gettext version autoreconf should be replaced with some other method but I have no idea what?
Regards,
Adolf.
next reply other threads:[~2025-05-13 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 14:12 Adolf Belka [this message]
2025-05-13 14:24 ` Michael Tremer
2025-05-13 18:57 ` Adolf Belka
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1b4d9025-5b3c-4af0-8f75-b2b691e9e6f8@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox