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.
Can we do the docs work on a branch? It might be a good idea to sort out
the installation as well, then update the docs and push to master all in
one go...
Yea we could have but we didn't when it would have been useful to do so,
and now we chose not to further complicate things by playing with
multiple branches in multiple repos.
Also, what's the magic trick to check out the Wiki as a git repo?
The magic trick is available from the "clone this wiki locally" box on
every page of the wiki.
