* [Buildroot] popt build failing during autoreconf
@ 2019-01-08 20:48 Grant Edwards
2019-01-08 21:53 ` Grant Edwards
0 siblings, 1 reply; 2+ messages in thread
From: Grant Edwards @ 2019-01-08 20:48 UTC (permalink / raw)
To: buildroot
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 ...
^ permalink raw reply [flat|nested] 2+ messages in thread* [Buildroot] popt build failing during autoreconf
2019-01-08 20:48 [Buildroot] popt build failing during autoreconf Grant Edwards
@ 2019-01-08 21:53 ` Grant Edwards
0 siblings, 0 replies; 2+ messages in thread
From: Grant Edwards @ 2019-01-08 21:53 UTC (permalink / raw)
To: buildroot
On 2019-01-08, Grant Edwards <grant.b.edwards@gmail.com> wrote:
> The popt package has recently started failing to build during the
> autoreconf step. [...] 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?
It is indeed an incompatiblity between automake 1.15 and perl 5.26.
Changing the automake version to 1.15.1 in the buildroot-2016.11.2
automake.mk file fixes the problem. You can't, however, just use the
automake.mk file from git master, because the newer autotools host
paths are not what other packages expect.
--
Grant Edwards grant.b.edwards Yow! Here we are in America
at ... when do we collect
gmail.com unemployment?
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-01-08 21:53 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-01-08 20:48 [Buildroot] popt build failing during autoreconf Grant Edwards
2019-01-08 21:53 ` Grant Edwards
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox