From: "Mike Frysinger" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-wireless/dump1090/
Date: Tue, 31 Jan 2017 09:55:41 +0000 (UTC) [thread overview]
Message-ID: <1485856492.612d9d554e36e585458b1e96b2bd53fcb41feda8.vapier@gentoo> (raw)
commit: 612d9d554e36e585458b1e96b2bd53fcb41feda8
Author: Ian Coolidge <icoolidge <AT> google <DOT> com>
AuthorDate: Tue Jan 31 09:54:52 2017 +0000
Commit: Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Tue Jan 31 09:54:52 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=612d9d55
net-wireless/dump1090: respect $PKG_CONFIG settings
Hardcoding `pkg-config` breaks cross-compiling.
net-wireless/dump1090/dump1090-0.0_p20140919.ebuild | 4 ++--
net-wireless/dump1090/dump1090-9999.ebuild | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/net-wireless/dump1090/dump1090-0.0_p20140919.ebuild b/net-wireless/dump1090/dump1090-0.0_p20140919.ebuild
index 495ceb4..eb5c454 100644
--- a/net-wireless/dump1090/dump1090-0.0_p20140919.ebuild
+++ b/net-wireless/dump1090/dump1090-0.0_p20140919.ebuild
@@ -32,8 +32,8 @@ src_prepare() {
src_compile() {
emake CC="$(tc-getCC)" \
- CFLAGS="$(pkg-config --cflags librtlsdr)" \
- LIBS="${LDFLAGS} $(pkg-config --libs librtlsdr) -lm -lpthread" \
+ CFLAGS="$($(tc-getPKG_CONFIG) --cflags librtlsdr)" \
+ LIBS="${LDFLAGS} $($(tc-getPKG_CONFIG) --libs librtlsdr) -lm -lpthread" \
all
}
diff --git a/net-wireless/dump1090/dump1090-9999.ebuild b/net-wireless/dump1090/dump1090-9999.ebuild
index 495ceb4..eb5c454 100644
--- a/net-wireless/dump1090/dump1090-9999.ebuild
+++ b/net-wireless/dump1090/dump1090-9999.ebuild
@@ -32,8 +32,8 @@ src_prepare() {
src_compile() {
emake CC="$(tc-getCC)" \
- CFLAGS="$(pkg-config --cflags librtlsdr)" \
- LIBS="${LDFLAGS} $(pkg-config --libs librtlsdr) -lm -lpthread" \
+ CFLAGS="$($(tc-getPKG_CONFIG) --cflags librtlsdr)" \
+ LIBS="${LDFLAGS} $($(tc-getPKG_CONFIG) --libs librtlsdr) -lm -lpthread" \
all
}
next reply other threads:[~2017-01-31 9:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 9:55 Mike Frysinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-11 2:06 [gentoo-commits] repo/gentoo:master commit in: net-wireless/dump1090/ Richard Farina
2017-07-30 10:04 Michał Górny
2018-08-16 20:45 Richard Farina
2018-08-19 22:05 Michael Weber
2018-08-19 22:29 Michael Weber
2019-07-03 5:22 Rick Farina
2019-09-27 14:05 Rick Farina
2020-01-20 12:52 Agostino Sarubbo
2020-01-21 10:42 Agostino Sarubbo
2020-12-28 14:48 David Seifert
2020-12-28 14:48 David Seifert
2020-12-29 10:11 David Seifert
2021-01-19 14:24 Sam James
2021-01-20 9:29 Sam James
2021-01-20 10:13 David Seifert
2021-09-26 19:36 Conrad Kostecki
2021-10-12 18:06 Marek Szuba
2021-10-14 10:00 Sam James
2021-10-14 10:00 Sam James
2021-10-15 6:00 Agostino Sarubbo
2024-12-03 11:14 Sam James
2024-12-03 11:14 Sam James
2025-03-01 1:14 Conrad Kostecki
2025-03-01 1:14 Conrad Kostecki
2025-03-01 23:27 Conrad Kostecki
2025-03-28 20:48 Conrad Kostecki
2025-03-28 20:48 Conrad Kostecki
2025-03-28 20:48 Conrad Kostecki
2025-04-21 22:54 Conrad Kostecki
2025-04-21 22:54 Conrad Kostecki
2025-08-10 22:38 Conrad Kostecki
2025-09-11 21:08 Conrad Kostecki
2025-09-11 21:08 Conrad Kostecki
2025-09-11 21:08 Conrad Kostecki
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=1485856492.612d9d554e36e585458b1e96b2bd53fcb41feda8.vapier@gentoo \
--to=vapier@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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