From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] popt build failing during autoreconf
Date: Tue, 8 Jan 2019 20:48:22 +0000 (UTC) [thread overview]
Message-ID: <q132am$sni$1@blaine.gmane.org> (raw)
The popt package has recently started failing to build during the
autoreconf step. I've been using buildroot-2016.11.2, but I tried
updating the popt package files to those from git-master, and it still
fails the same way. This appears to be an incompatibility between
automake and perl 5.26:
$ ./output/host/usr/bin/automake --version
Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/\${ <-- HERE ([^ \t=:+{}]+)}/@./output/host/usr/bin/automake line 3936.
It appears that buildroot-2016.11.2 is using automake 1.15, and the
current git buildroot master branch is using version 1.15.1. Should I
be able to update the automake package without causing problems?
========================================== make output shown below ======================================
umask 0022 && make -C /home/nextgen/buildroot/buildroot-2016.11.2 O=/home/nextgen/buildroot/output/.
>>> popt 1.16 Configuring
>>> popt 1.16 Gettextizing
[...]
>>> popt 1.16 Autoreconfiguring
Use of uninitialized value $args[0] in split at /home/nextgen/buildroot/output/host/usr/bin/autoreconf line 493, <GEN3> line 7.
autoreconf: configure.ac: AM_GNU_GETTEXT is used, but not AM_GNU_GETTEXT_VERSION
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/\${ <-- HERE ([^ \t=:+{}]+)}/ at /home/nextgen/buildroot/output/host/usr/bin/automake line 3936.
autoreconf: /home/nextgen/buildroot/output/host/usr/bin/automake failed with exit status: 255
make[1]: *** [package/pkg-generic.mk:208: /home/nextgen/buildroot/output/build/popt-1.16/.stamp_configured] Error 1
make: *** [Makefile:16: _all] Error 2
--
Grant Edwards grant.b.edwards Yow! Hmmm ... an arrogant
@ bouquet with a subtle
gmail.com suggestion of POLYVINYL
CHLORIDE ...
next reply other threads:[~2019-01-08 20:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 20:48 Grant Edwards [this message]
2019-01-08 21:53 ` [Buildroot] popt build failing during autoreconf Grant Edwards
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='q132am$sni$1@blaine.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=buildroot@busybox.net \
/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