Date: Sat, 26 Oct 2013 21:53:26 +1100 From: Jason Birch <jbirch@jbirch.net> To: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Kernel/World/Ports compilation within jails; targeting many platforms. Message-ID: <CAA=KUht4Kyz=-J6yGJdPfO4Bnr0a8-qU8k_Aj2Gp0MKjjPM=Qw@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Is it considered 'good form' to do compilation for other machines, architectures, and FreeBSD versions within jails? As a concrete example, my 'main' system is a FreeBSD 9.1-RELEASE amd64 system, and I would like to compile FreeBSD 11-CURRENT for my BeagleBone Black (ARMv7). Does it make more sense to create a jail environment on my 9.1-RELEASE machine to do all compilation and 'staging' for the BeagleBlack? Originally I had just compiled gcc targeting arm and checked out sources into a location that wasn't /usr/src/. This is simple enough for one different target, but I'm wondering if I'll be a little bit more sane if I've got a jail for each individual target I'm compiling for. Each jail can then be set up with one, consistent compiler and source tree in the same location -- even if the compiler (GCC/Clang) and source (X-RELEASE vs Y-STABLE vs CURRENT) differ between targets? Are this a sane thing to be doing? For those of you that have several FreeBSD targets but do most of your set up on a single machine, how do you logically separate your 'worlds'? Regards, JB
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAA=KUht4Kyz=-J6yGJdPfO4Bnr0a8-qU8k_Aj2Gp0MKjjPM=Qw>