On 23/10/15 14:31, Martin Lucina wrote:
The standard convention for cross toolchains is to install into
$PREFIX/$AUTOCONF-TUPLE, so for us that would be e.g.
$PREFIX/x86_64-rumprun-netbsd. Take at look at the musl toolchains [1] for
examples.
Following that scheme directly doesn't really cut it for us in any way (xen
and hw libs would still conflict, and the usability of having to add things
to PATH after installing packages is rubbish). I wanted to put the lib (and
possibly include) dirs into separate subdirs, akin to what is happening in
/usr on some linux distros. The problem is that the NetBSD makefiles
hardcode the libdir location based on the root dir. I think I woke up a
simple solution to that problem, but need to make it work. Anyway, it will
be a "user-invisible" change, so not necessary to bundle with flag days.
I would split the problem up:
1) Install into $PREFIX/$AUTOCONF-TUPLE.
2) Resolve the xen and hw lib conflicts.
3) Work out what needs to be done to allow install to $PREFIX, where
$PREFIX == /usr.
I wouldn't, because solving it that way involves multiple user-visible
changes even for the "hey I just want to use this on one platform" case.
Furthermore, "2" is extremely unlikely to happen (xen and hw needs to be
built with different kernel defines).
