Re: building releases for various architectures
On Friday, April 13, 2007 at 00:06:45 +0200, Joachim Schipper wrote:
On Thu, Apr 12, 2007 at 11:31:30PM +0200, Maurice Janssen wrote:
I have a few old computers (vax, hppa, sparc), most of them with quite
small hard disks. Too small to build the userland. I also have a i386
with more than enough disk space running as nfs server.
Right now, I have a /export/${arch}/src and /export/${arch}/obj for each
architecture. Works fine, but most of the contents of the source
directories is the same for each architecture. Seems like a waste of
resources to keep it separate.
The FAQ mentions building a kernel with a read only source tree, but
nothing about userland. Is it possible to mount /usr/src read-only and
build the userland?
Yes, 'mostly'. You *will* need to 'make obj' beforehand, but IIRC most
everything will only write to obj when compiling. A noticeable exception
are the kernels (but you could always symlink /usr/src/sys to somewhere
appropriate).
For a better idea, how about one of the 'remove duplicates by
hardlinking them together' packages? It would allow you to have
essentially identical trees without wasting more than some inodes. Other
variations on this theme are possible, like lndir(1).
After reading your and an off-list reply and thinking about it again,
I realised that it's not really necessary to have a RO source tree.
Each architecture uses its own subdirectory for the kernel and the rest
goes to /usr/obj. The 'make obj' step for one architecture doesn't
interfere with the other architectures.
Thanks for the hint,
Maurice
building releases for various architectures
Hi,
Is it possible to have a single src directory that is shared by various
architectures to build releases?
I have a few old computers (vax, hppa, sparc), most of them with quite
small hard disks. Too small to build the userland. I also have a i386
with more than enough disk space running as nfs server.
Right now, I have a /export/${arch}/src and /export/${arch}/obj for each
architecture. Works fine, but most of the contents of the source
directories is the same for each architecture. Seems like a waste of
resources to keep it separate.
The FAQ mentions building a kernel with a read only source tree, but
nothing about userland. Is it possible to mount /usr/src read-only and
build the userland?
Thanks,
Maurice
Re: building releases for various architectures
Maurice Janssen wrote:
Hi,
Is it possible to have a single src directory that is shared by various
architectures to build releases?
I have a few old computers (vax, hppa, sparc), most of them with quite
small hard disks. Too small to build the userland. I also have a i386
with more than enough disk space running as nfs server.
Right now, I have a /export/${arch}/src and /export/${arch}/obj for each
architecture. Works fine, but most of the contents of the source
directories is the same for each architecture. Seems like a waste of
resources to keep it separate.
The FAQ mentions building a kernel with a read only source tree, but
nothing about userland. Is it possible to mount /usr/src read-only and
build the userland?
calling all cars, calling all cars, we have an APB out on a bunch of
FSes that should be on NFS. danger: these FSes may be armed and
dangerous, possibly with extra network latency. use extreme caution and
try to keep them separate if possible!
if you see any with v4, call for donations before apprehending.
cheers,
jake
Thanks,
Maurice
