On 23 October 2015 at 10:50, Martin Lucina <mar...@lucina.net> wrote: > On Friday, 23.10.2015 at 00:47, Antti Kantee wrote: >> On 12/10/15 13:54, Antti Kantee wrote: >> >Hi, >> > >> >I'm tweaking the build system (the fun never ends) to allow installation >> >of the Rumprun toolchain and libs into an arbitrary directory, the idea >> >of course being that you can then tar up that directory for binary >> >packages. I'm currently targeting for it to be possible to install one >> >configuration; having e.g. x86_64-hw and x86_64-xen in the same destdir >> >is out of the immediate scope (even if in the eventual scope). >> > >> >Naturally, some amount of rototilling is required. As usual, >> >"build-rr.sh" is the only official way to build things. However, it's >> >important for me to keep the developer shortcuts working too. So, if >> >over the course of the rototillage you notice some shortcuts breaking, >> >ping the list, and we'll see what to do about it. >> > >> >The user-visible change will be installing app-tools to destdir/bin. If >> >someone wants to write the compat lint to keep app-tools also where they >> >currently are in addition to destdir, let me know in the next day or so. >> > Otherwise, we'll just have a flag day. >> > >> >I'll send another email when the initial part of the rototill is >> >complete (a day or few, depending on how boring fighting with the build >> >system gets). >> >> Ok, I got it working enough so that I can build+install to a destdir and rm >> -rf builddir and still be able to compile and run things (*). Given that >> it's late and I do need to update all the docs everywhere for the app-tools >> path change, I pushed the result to a branch (pooka-destdir) and will be >> merging it tomorrow. >> >> *) well apparently travis disagrees, but not going to fix it tonight. for >> once i was smart enough to not push directly to master. > > Great. Ping me when the branch is in a state to test and I'll give it a > whirl before we merge it. > >> So what this buys you is that you can tar up the destination dir, and untar >> it to the same location on a "similar enough" machine (same backing >> toolchain etc). It should make e.g. doing Travis CI on rumprun-packages >> easier (any volunteers for making that happen?) > > The main problem with Travis and packages is that it will kill any build > job taking longer than 50 minutes, which rules out at least rust, and > possibly other packages. (And rules out running "make world" as a single > job.) > > As a stopgap I'm going to try and get things building using the Docker Hub > (just treating it as a "autobuilder") based on the work Justin did.
I have docker hub builds here https://hub.docker.com/r/justincormack/rumprun-packages/builds/ They are working ex rust now; its possible that even docker hub is timing out on that as it gave me an exception error. Just pushed the mode fixes to my fork so node may build now, in which case everything ex rust is working, and can look at adding this to CI. >> 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. > > (PREFIX would normally default to /usr/local) > > [1] > https://e82b27f594c813a5a4ea5b07b06f16c3777c3b8c.googledrive.com/host/0BwnS5DMB0YQ6bDhPZkpOYVFhbk0/musl-1.1.6/ >
