Re: [PATCH v2] build: validate libraries returned from meson find function

[Ali Alnubani <alialnu@nvidia.com>]

On 10/2/25 7:28 PM, Bruce Richardson wrote:
> On Thu, Oct 02, 2025 at 06:42:15PM +0300, Ali Alnubani wrote:
>> On 10/2/25 3:45 PM, David Marchand wrote:
>>
>>> On Thu, 2 Oct 2025 at 13:54, David Marchand <david.marchand@redhat.com> wrote:
>>>> On Wed, 24 Sept 2025 at 13:13, Bruce Richardson
>>>> <bruce.richardson@intel.com> wrote:
>>>>> The meson find_library() API call sometimes finds a library that is
>>>>> actually incompatible with the current build, for example, returning a
>>>>> 64-bit library when doing a 32-bit build. To avoid problems with this,
>>>>> check each library returned from a find_library() call and treat the
>>>>> library as unfound if its incompatible.
>>>>>
>>>>> This checking is not necessary (or should not be necessary) for
>>>>> dependencies got using pkg-config, since the .pc files for each build
>>>>> type are stored in a different directory on the system.
>>>>>
>>>>> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
>>>> Acked-by: David Marchand <david.marchand@redhat.com>
>>> Applied, thanks.
>> Hello,
>>
>> I have warnings like this for mlx5 drivers on Ubuntu 22.04 with clang:
>>
>> Message: Disabling mlx5 [drivers/net/mlx5]: missing internal dependency
>> "common_mlx5"
>>
>> Build command:
>> CC=clang PKG_CONFIG_PATH=/opt/rdma-core/build/lib/pkgconfig meson --werror
>> --buildtype=debugoptimized build
>>
>> gcc does not reproduce.
>>
> [Trimming CC list a bit]
>
> Hi,
>
> There must be an earlier error where the check for a library used by
> common_mlx5 fails. Can you perhaps send on a more complete build log, or
> perhaps log a bugzilla and attach the meson configuration output, and the
> meson build logfile there?
>
> /Bruce

Created a Bugzilla ticket with meson logs and more info:

https://bugs.dpdk.org/show_bug.cgi?id=1798

Thanks,
Ali