Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Neumann <s.neumann@phase-zero.de>
To: buildroot@busybox.net
Subject: [Buildroot] pkgconfig confusion
Date: Fri, 17 Apr 2009 11:56:04 +0200	[thread overview]
Message-ID: <1239962164.6397.6.camel@sven> (raw)

Hi,

I've tried to update to the latest buildroot snapshot today and ran into
a problem with pkg-config:

>>> pkgconfig undefined Extracting
gzip: /home/sven/buildroot-new/dl/pkgconfig-undefined.tar.gz: No such
file or directory
tar: This does not look like a tar archive

So I had a look at package/pkgconfig/pkgconfig.mk and found that it
defines all variables with the PKG_CONFIG prefix instead of using
PKGCONFIG. Changing this seems to fix the problem (see attached diff).
Alternatively one could rename pkgconfig/pkgconfig.mk to
pkg-config/pkg-config.mk.


Sven


-------------- next part --------------
A non-text attachment was scrubbed...
Name: pkgconfig.diff
Type: text/x-patch
Size: 3283 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090417/a1823cac/attachment.bin>

             reply	other threads:[~2009-04-17  9:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17  9:56 Sven Neumann [this message]
2009-04-17 10:25 ` [Buildroot] pkgconfig confusion Sven Neumann
2009-04-17 14:18 ` Peter Korsgaard

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=1239962164.6397.6.camel@sven \
    --to=s.neumann@phase-zero.de \
    --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