>then maybe you did not reconfigure your build env. >$ meson --reconfigure <build_dir>
🙂. I tried many meson commands to wipe/reconfigure my build environment, but I've just blown away the whole build directory and started again, and now it appears to be working ( though I thought I'd tried that before too ). Maybe I missed a trick with reconfiguring meson, I don't know. The PC has also been restarted a few times. The ninja build succeeds ( with warnings ). Anyway, I'm encouraged that there are people listening out there, and willing to try helping 🙂. Thanks folk, Mark [cid:a8ca81a5-8baf-4da6-a3b6-bd53d0013478][cid:4721cdc2-3222-4b8f-8ce2-87d22690b4f8] ________________________________ From: David Marchand <david.march...@redhat.com> Sent: 20 July 2022 16:18 To: Mark de Roussier <m...@hitomi-broadcast.tv> Cc: Дмитрий Степанов <stepanov.d...@gmail.com>; users@dpdk.org <users@dpdk.org> Subject: Re: Couple of build problems ( Fedora 36, DPDK 21.11.1 ) On Wed, Jul 20, 2022 at 4:59 PM Mark de Roussier <m...@hitomi-broadcast.tv> wrote: > > Hello David, > > thanks for the idea, but I'm afraid that's not the case. I do have that > already, that is what is providing libmlx4 and libmlx5. But it does not > contain librte_common_mlx5, which is what I think is probably the source of > my problem. Well, that's what I have on my Fedora to build mlx drivers. Btw, librte_common_mlx5 is an internal DPDK driver. If you still see that this component is disabled after installing those headers via the devel packages, then maybe you did not reconfigure your build env. $ meson --reconfigure <build_dir> If this is not working, you'll have to look into <build_dir>/meson-logs/, there may be some useful info in those logs. -- David Marchand
