From: David Marchand <david.marchand@redhat.com>
To: bruce.richardson@intel.com
Cc: dev@dpdk.org
Subject: [dpdk-dev] pkg-config file generated with meson
Date: Thu, 29 Nov 2018 14:55:36 +0100 [thread overview]
Message-ID: <CAJFAV8y3PFptuSSi9K8AG6pZTqxrq417wuux5+F1wtG4hnnvFQ@mail.gmail.com> (raw)
Hello Bruce,
I built v18.11 with meson and had a little look at the libdpdk.pc file.
It looks like pkg-config works fine with --libs but is recursively opening
libdpdk.pc when asking for the cflags:
$ PKG_CONFIG_PATH=build/meson-private:$PKG_CONFIG_PATH pkg-config --libs
libdpdk
-L/usr/local/lib64 -lrte_telemetry -lrte_bpf -lrte_flow_classify
-lrte_pipeline -lrte_table -lrte_port -lrte_vhost -lrte_security
-lrte_sched -lrte_reorder -lrte_rawdev -lrte_pdump -lrte_power -lrte_meter
-lrte_member -lrte_lpm -lrte_latencystats -lrte_kni -lrte_jobstats
-lrte_ip_frag -lrte_gso -lrte_gro -lrte_eventdev -lrte_efd
-lrte_distributor -lrte_cryptodev -lrte_compressdev -lrte_cfgfile
-lrte_bitratestats -lrte_bbdev -lrte_acl -lrte_timer -lrte_hash
-lrte_metrics -lrte_pci -lrte_ethdev -lrte_net -lrte_mbuf -lrte_mempool
-lrte_ring -lrte_eal -lrte_kvargs -lrte_cmdline
$ PKG_CONFIG_PATH=build/meson-private:$PKG_CONFIG_PATH pkg-config --cflags
libdpdk
Failed to open 'build/meson-private/libdpdk.pc': Too many open files
Package 'libdpdk', required by 'DPDK', not found
$ PKG_CONFIG_PATH=build/meson-private:$PKG_CONFIG_PATH strace pkg-config
--cflags libdpdk 2>&1|grep -c 'open(.*libdpdk.pc'
1022
I must be doing something wrong...
I use meson 0.47.2 and dpdk is only built locally, not installed on the
system.
--
David Marchand
next reply other threads:[~2018-11-29 13:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 13:55 David Marchand [this message]
2018-11-29 14:07 ` Luca Boccassi
2018-11-29 14:13 ` David Marchand
2018-12-03 12:44 ` Luca Boccassi
2018-12-03 12:50 ` David Marchand
2018-12-13 9:36 ` Luca Boccassi
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=CAJFAV8y3PFptuSSi9K8AG6pZTqxrq417wuux5+F1wtG4hnnvFQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).