From: Jon Ringle <jon@ringle.org>
To: ptxdist@pengutronix.com
Subject: [ptxdist] host-autoconf: hardcoded path to m4
Date: Mon, 18 Feb 2019 15:18:36 -0500 [thread overview]
Message-ID: <CAMwGMjz7n56iZ4Kik_Jv4pn1CxaO2GozJzAMeJu4JA-WXS8wMg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1170 bytes --]
The host-autoconf.make package creates a *-dev.tar.gz package, but the
host-autoconf-2.69/bin/auto4mte script install found in it contains a
hardcoded path to m4 that results in a build failure for future builds that
use the host-autoconf-2.69-arm-*-dev.tar.gz package:
Line 90 of the autom4te in mine has:
my $m4 = $ENV{"M4"} ||
'/srv/bamboo-home/xml-data/build-dir/29261826/GPEC-EC6-JOB1/platform-ec1c/sysroot-host/bin/m4';
Resulting in a build failure of any package that calls autogen.sh in the
extract.post phase:
-------------------------------------
target: host-libfastjson.extract.post
-------------------------------------
pkg_patch_autogen: 'ptxdist-2019.01.0/patches/libfastjson-0.99.8/autogen.sh'
autom4te: need GNU m4 1.4 or later:
/srv/bamboo-home/xml-data/build-dir/29261826/GPEC-EC6-JOB1/platform-ec1c/sysroot-host/bin/m4
aclocal: error: echo failed with exit status: 1
/usr/local/lib/ptxdist-2019.01.0/rules/post/ptxd_make_world_extract.make:38:
recipe for target
'/srv/gpec-build/rootfs/platform-ec1c/state/host-libfastjson.extract.post'
failed
make: ***
[/srv/gpec-build/rootfs/platform-ec1c/state/host-libfastjson.extract.post]
Error 1
-Jon
[-- Attachment #1.2: Type: text/html, Size: 2287 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2019-02-18 20:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 20:18 Jon Ringle [this message]
2019-02-22 8:14 ` [ptxdist] [PATCH] host-autotools-autoconf: fix m4 path Michael Olbrich
2019-02-22 12:59 ` Michael Olbrich
2019-02-22 13:19 ` Michael Olbrich
2019-02-22 18:08 ` Jon Ringle
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=CAMwGMjz7n56iZ4Kik_Jv4pn1CxaO2GozJzAMeJu4JA-WXS8wMg@mail.gmail.com \
--to=jon@ringle.org \
--cc=ptxdist@pengutronix.com \
--cc=ptxdist@pengutronix.de \
/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