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

2020-09-03 Thread Luca Boccassi
On Wed, 2020-09-02 at 17:05 +0200, David Marchand wrote: > On Wed, Sep 2, 2020 at 2:39 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.f

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

2020-09-02 Thread David Marchand
On Wed, Sep 2, 2020 at 2:39 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 v2] avoid libfdt checks adding full paths to pkg-config

2020-09-02 Thread Luca Boccassi
On Wed, 2020-09-02 at 14:39 +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 probe t

[dpdk-dev] [PATCH v2] 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