Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pkgconf: Add a symlink to the GNU_TARGET_NAME-pkg-config
Date: Wed, 2 Mar 2016 21:25:53 +0100	[thread overview]
Message-ID: <20160302212553.718456cf@free-electrons.com> (raw)
In-Reply-To: <1456770170-6326-1-git-send-email-jer@airfi.aero>

Dear Jeroen Roovers,

On Mon, 29 Feb 2016 19:22:50 +0100, Jeroen Roovers wrote:
>  Lots of packages start to call pkg-config "properly" and run into
>  failures like this:
> 
> *
> * System Logging Utilities
> *
> syslogd (SYSLOGD) [N/y/?] n
> klogd (KLOGD) [N/y/?] n
> logger (LOGGER) [Y/n/?] y
> make[2]: .../output/host/usr/bin/arm-buildroot-linux-gnueabihf-pkg-config: Command not found
> make[2]: .../output/host/usr/bin/arm-buildroot-linux-gnueabihf-pkg-config: Command not found
> make[1]: Leaving directory '.../output/build/busybox-1.24.1'

I think we should solve this specific problem by passing the PKG_CONFIG
in the Busybox environment.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2016-03-02 20:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 18:22 [Buildroot] [PATCH] pkgconf: Add a symlink to the GNU_TARGET_NAME-pkg-config Jeroen Roovers
2016-02-29 19:19 ` Bernd Kuhls
2016-02-29 20:35   ` Thomas Petazzoni
2016-02-29 23:09     ` Peter Korsgaard
2016-03-01  8:14       ` Thomas Petazzoni
2016-03-01  8:15         ` Peter Korsgaard
2016-03-01 21:12     ` Arnout Vandecappelle
2016-03-18 17:24       ` Yann E. MORIN
2016-03-18 21:14         ` Arnout Vandecappelle
2016-03-02 20:25 ` Thomas Petazzoni [this message]
2016-03-18 17:25   ` Yann E. MORIN

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=20160302212553.718456cf@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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