Re: [dpdk-dev] [PATCH] avoid libfdt checks adding full paths to pkg-config

2020-09-16 Thread David Marchand
On Wed, Sep 2, 2020 at 1:10 PM Christian Ehrhardt wrote: > > The checks for libfdt try dependency() first which would only work if > a pkg-config would be present but libfdt has none. > Then it probes for the lib path itself via cc.find_library. > > But later it adds the result of either probe to

Re: [dpdk-dev] [PATCH] avoid libfdt checks adding full paths to pkg-config

2020-09-02 Thread Christian Ehrhardt
On Wed, Sep 2, 2020 at 1:25 PM Bruce Richardson wrote: > > On Wed, Sep 02, 2020 at 01:10:30PM +0200, Christian Ehrhardt wrote: > > The checks for libfdt try dependency() first which would only work if > > a pkg-config would be present but libfdt has none. > > Then it probes for the lib path itself

Re: [dpdk-dev] [PATCH] avoid libfdt checks adding full paths to pkg-config

2020-09-02 Thread Bruce Richardson
On Wed, Sep 02, 2020 at 01:10:30PM +0200, Christian Ehrhardt wrote: > The checks for libfdt try dependency() first which would only work if > a pkg-config would be present but libfdt has none. > Then it probes for the lib path itself via cc.find_library. > > But later it adds the result of either

[dpdk-dev] [PATCH] avoid libfdt checks adding full paths to pkg-config

2020-09-02 Thread Christian Ehrhardt
The checks for libfdt try dependency() first which would only work if a pkg-config would be present but libfdt has none. Then it probes for the lib path itself via cc.find_library. But later it adds the result of either probe to ext_deps which ends up in build and also the resulting pkg-config to