From: desmond <desmond.correia@prolucid.ca>
To: ptxdist@pengutronix.de
Subject: [ptxdist] glib can't find libffi for target platform
Date: Thu, 26 May 2016 14:12:45 +0000 (UTC) [thread overview]
Message-ID: <loom.20160526T152435-766@post.gmane.org> (raw)
Hello,
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.
Thanks
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2016-05-26 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 14:12 desmond [this message]
2016-05-31 5:45 ` Michael Olbrich
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=loom.20160526T152435-766@post.gmane.org \
--to=desmond.correia@prolucid.ca \
--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