Timberland nvme-cli/libnvme upstream merge - dbus dependency.

[John Meneghini]

On 2/3/23 12:30, Keith Busch wrote:
>> The current nvme-cli meson.build configuration for libnvme is always pulling the
>> fallback. A workaround is to build libnvme as separate step as you would do when
>> packaging.
> I'm just trying to build this right now on an embedded system, and my goodness,
> it is fucking painful. It's a bare-bones busybox enviroment with no internet
> connection. Just getting meson on there was unpleasant, and now the build just
> gives up with the failed dependencies.
> 

Here's how I solved the problem on my redhat platforms: fedora36, centos9 and rhel-8.6

$ sudo dnf update -y
$ sudo dnf install -y meson cmake dbus-devel libuuid libuuid-devel libuuid-debuginfo json-c-devel json-c-debuginfo json-c \
        json-c-doc libhugetlbfs libhugetlbfs-devel libhugetlbfs-lib clang openssl openssl-devel dbus-devel
                                                                                                 ^^^^^^^^

Every time I find a missing library or package I add it to my tool chain because the meson fallback/compile stuff is always 
broken and full of bugs.

This is what you want to see:


Build targets in project: 21

nvme-cli 2.3

   Subprojects
     libnvme: YES

Found ninja-1.10.2 at /usr/bin/ninja
Configuration located in: .build
-------------------------------------------------------
ninja -C .build
ninja: Entering directory `.build'
[119/119] Linking target nvme

/John