On Friday, 23.10.2015 at 14:10, Antti Kantee wrote: > On 23/10/15 09:50, Martin Lucina wrote: > >Great. Ping me when the branch is in a state to test and I'll give it a > >whirl before we merge it. > > Thanks, but not necessary. > > >>What it does not (yet) buy you is a recommendation to install into an > >>established hierarchy, such as /usr. Or, you can, but given that e.g. > >>/usr/lib/libc.a would be installed, you might run into trouble ... Will fix > >>that later. > > > >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. Step 1) can be done ASAP with the current setup, and is still better than what we have now (no install option). Step 3) is, in my opinion, best left to $DISTRO packaging people as each $DISTRO has it's own slightly different idea of how cross toolchains should be installed. In other words, it saves us the work of figuring out step 3). I'm happy to volunteer to make step 2) work. -mato
