From: "Jan Remeš" <remes@netcope.com>
To: Luca Boccassi <bluca@debian.org>
Cc: Rastislav Cernay <cernay@netcope.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v4] net/nfb: new netcope driver
Date: Thu, 7 Mar 2019 15:14:39 +0100 [thread overview]
Message-ID: <CAAnEdtA1MgQsO9dUW_-v4wP_zp2CDqzopV=hkdP6qFZYpLp-tw@mail.gmail.com> (raw)
In-Reply-To: <aeb9f41231d6bb514d8e0fa4b73129f7145da269.camel@debian.org>
Hi,
> I see netcope-common provides a pkg-config file, that's great.
> However it's a bit broken at the moment:
>
> Name: netcope-common
> Version: 6.3.0
> Description: Common software package for NetCOPE platform
> Libs: -L${libdir}
> Cflags: -I${includedir}
>
> There is no linker flag, and Libs.private is missing. It should have:
>
> Libs: -L${libdir} -lnfb
> Libs.private: -lfdt
>
> Could you please get it fixed?
We are preparing a release of netcope-common, which will include fixed
pkg-config file.
>
> This will not work - the pkg-config filename is netcope-common.pc, not
> libnfb.pc. The convention would be to rename the pkg-config file to
> libnfb.pc, but if you want to keep the current name then all pkg-config
> calls in this patch need to be updated.
The first proposal on this issue, which this patch version is based
upon, was to add a new "libnfb.pc" pkg-config file to netcope-common.
This might be finalized either as a fix in netcope-common.pc or a
separate libnfb.pc being shipped. Once this decision is made, we will
address it appropriately in the patch.
Best regards,
Jan Remes
next prev parent reply other threads:[~2019-03-07 14:14 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 12:57 [dpdk-dev] [PATCH] net/nfb: new Netcope driver Rastislav Cernay
2019-02-26 12:57 ` [dpdk-dev] [PATCH] net/nfb: new netcope driver Rastislav Cernay
2019-02-26 14:20 ` Rami Rosen
2019-02-26 16:33 ` Rastislav Černay
2019-02-26 15:46 ` Stephen Hemminger
2019-02-27 11:43 ` [dpdk-dev] [PATCH v2] net/nfb: new Netcope driver Rastislav Cernay
2019-02-27 15:28 ` Ferruh Yigit
2019-03-01 14:37 ` [dpdk-dev] [PATCH v3] net/nfb: new netcope driver Rastislav Cernay
2019-03-01 18:47 ` Stephen Hemminger
2019-03-04 14:07 ` Rastislav Černay
2019-03-01 18:50 ` Stephen Hemminger
2019-03-04 9:53 ` David Marchand
2019-03-04 11:34 ` David Marchand
2019-03-04 14:33 ` Rastislav Černay
2019-03-04 12:35 ` David Marchand
2019-03-04 12:48 ` David Marchand
2019-03-04 15:15 ` Rastislav Černay
2019-03-05 20:31 ` Rami Rosen
2019-03-05 22:41 ` Luca Boccassi
2019-03-06 14:51 ` Rastislav Černay
2019-03-06 13:25 ` Luca Boccassi
2019-03-07 13:24 ` [dpdk-dev] [PATCH v4] " Rastislav Cernay
2019-03-07 13:46 ` Luca Boccassi
2019-03-07 14:14 ` Jan Remeš [this message]
2019-03-22 12:12 ` [dpdk-dev] [PATCH v5] " Rastislav Cernay
2019-03-22 12:12 ` Rastislav Cernay
2019-03-28 16:01 ` Ferruh Yigit
2019-03-28 16:01 ` Ferruh Yigit
2019-04-01 14:55 ` Rastislav Černay
2019-04-01 14:22 ` Ferruh Yigit
2019-04-01 14:22 ` Ferruh Yigit
2019-04-02 16:05 ` Rastislav Černay
2019-04-02 16:05 ` Rastislav Černay
2019-04-01 14:23 ` Luca Boccassi
2019-04-01 14:23 ` Luca Boccassi
2019-04-01 14:55 ` Rastislav Černay
2019-04-04 9:05 ` [dpdk-dev] [PATCH v6] " Rastislav Cernay
2019-04-04 9:05 ` Rastislav Cernay
2019-04-05 0:08 ` Ferruh Yigit
2019-04-05 0:08 ` Ferruh Yigit
2019-04-07 15:03 ` [dpdk-dev] [PATCH v7] " Rastislav Cernay
2019-04-07 15:03 ` Rastislav Cernay
2019-04-12 12:15 ` Ferruh Yigit
2019-04-12 12:15 ` Ferruh Yigit
2019-04-12 12:16 ` Ferruh Yigit
2019-04-12 12:16 ` Ferruh Yigit
2019-04-12 14:37 ` [dpdk-dev] [PATCH] net/nfb: remove redundant linking Rastislav Cernay
2019-04-12 14:37 ` Rastislav Cernay
2019-04-12 15:02 ` Ferruh Yigit
2019-04-12 15:02 ` Ferruh Yigit
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='CAAnEdtA1MgQsO9dUW_-v4wP_zp2CDqzopV=hkdP6qFZYpLp-tw@mail.gmail.com' \
--to=remes@netcope.com \
--cc=bluca@debian.org \
--cc=cernay@netcope.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).