From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] glib can't find libffi for target platform
Date: Tue, 31 May 2016 07:45:36 +0200 [thread overview]
Message-ID: <20160531054536.GB32696@pengutronix.de> (raw)
In-Reply-To: <loom.20160526T152435-766@post.gmane.org>
Hi,
On Thu, May 26, 2016 at 02:12:45PM +0000, desmond wrote:
> I have been using ptxdist2013.12.0 for sometime now with ubuntu15.04 without
> any problems.
>
> I recently upgraded to Ubuntu16 and I am running into a problem when the
> build system tries to build glib for the target platform. It can't seem to
> find libffi.
>
> This is under the .prepare step for the target build. libffi was successfully
> built for the target already.
>
> --------------------
> target: glib.prepare
> --------------------
>
> checking for LIBFFI... no
> configure: error: in `home/Toolchain/TQMa28/TQ-ARM-BSP-REV.0109/platform-
> tqma28/build-target/glib-2.36.4':
> configure: error: The pkg-config script could not be found or is too old.
> Make sure it
> is in your PATH or set the PKG_CONFIG environment variable to the full
> path to pkg-config.
>
> Alternatively, you may set the environment variables LIBFFI_CFLAGS
> and LIBFFI_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
>
> I had downgraded gawk to 4.1.1 because I was getting a ton of warning. I also
> tried export LIBFFI_CFLAGS and LIBFFI_LIBS, but I think ptxdist discard the
> environment variables that I set.
>
> I can provide more of the log if needed.
>
> Any help will be much appreciated.
If I remember correctly, that is because your bash is no longer vulnerable
to Shellshock :-/. The fixes for that disabled a 'feature' that ptxdist
relied on. The details are in the commit message for the fix
974f2aa064fc302be9cd5250a761d16b3993ceb0 ("pkg-config-wrapper: don't use
check_pipe_status").
To fix this in a BSP you need to copy scripts/pkg-config-wrapper and
rules/cross-pkg-config-wrapper.make from a later ptxdist version that
contains this fix into your BSP and then modify the paths in
cross-pkg-config-wrapper.make to install your new version of
pkg-config-wrapper.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2016-05-31 5:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 14:12 desmond
2016-05-31 5:45 ` Michael Olbrich [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=20160531054536.GB32696@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--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