On 25/09/14 14:11, Justin Cormack wrote: > I have started adding NetBSD cross builds to various architectures to > the head tests. Not sure how many the machine its running on can cope > with, currently got sparc64 (as there were no sparc build tests at all > and it is a tier 1 architecture) and evbarm, and I have the compiler > build done for mips64-el so may add that.
I assume you wanted to include this remindatory URL: http://build.myriabit.eu:8012/waterfall (which is linked from http://builds.rumpkernel.org/) Looks ... even more impressive now. I need to get a screen with wider horizontal resolution ;) Is there any difference between -cross and -x? -cross runs the tests too? Just to document the setup, was it any more complicated than running ./build.sh -m arch once, and then setting CC, AS, LD, OBJCOPY to point to the created toolchain and CFLAGS to contain --sysroot (as is output by buildrump.sh)? > Some teething issues but I have hand tested them so buildbot should be > fine soon. Apart from some overnight hiccup in HEAD of NetBSD, seems to be doing quite nicely. > Obviously it doesnt run any tests as its a cross build - thats another > issue... "obviously" = "no qemu-user support for said targets", or something else? > (arm64 is the other one that I need to sort out, it builds but not > happy that it works) mips64 doesn't seem to be happy enough to even build. nice work! ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ rumpkernel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
