Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] popt build failing during autoreconf
Date: Tue, 8 Jan 2019 21:53:54 +0000 (UTC)	[thread overview]
Message-ID: <q1365i$164$1@blaine.gmane.org> (raw)
In-Reply-To: q132am$sni$1@blaine.gmane.org

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?

      reply	other threads:[~2019-01-08 21:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-08 20:48 [Buildroot] popt build failing during autoreconf Grant Edwards
2019-01-08 21:53 ` Grant Edwards [this message]

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='q1365i$164$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