building nvmetcli in buildroot

stephane gonauer stephane.gonauer at 6wind.com
Thu Nov 9 23:43:05 PST 2017


Hi,

I dug further into the question to better understand.

>From my understanding the root cause lies in setuptools :

- buildroot uses --prefix option to set the prefix to $(TARGET_DIR)
- the setup.cfg from nvmetcli uses -install-script
- When both options are present, install-script completely overrides
--prefix and is considered as an absolute path.

I tried to uses $(TARGET_DIR) inside setup.cfg but it is not evaluated
when reaching setup.cfg (and it results in a path containing the
TARGET_DIR and not its value).

Unless someone knows how to better use setuptools, I don't see a
solution inside nvmetcli tree

Stéphane

2017-11-09 18:10 GMT+01:00 Christoph Hellwig <hch at lst.de>:
> I'm perfectly happy to make life for buildroots easier, but nvmetcli
> is an admin tool that should live in /usr/sbin.  We'll need to find
> a way for that to still be the default.



More information about the Linux-nvme mailing list