Date: Tue, 30 Jun 2015 20:54:07 +0200 From: Willem Jan Withagen <wjw@digiware.nl> To: "Simon J. Gerraty" <sjg@juniper.net>, jbtakk@iherebuywisely.com Cc: freebsd-current <freebsd-current@freebsd.org>, current <current@freebsd.org> Subject: Re: "proper way" or "unworkable idea" ? Message-ID: <5592E5CF.6020509@digiware.nl> In-Reply-To: <20845.1435678348@chaos> References: <E1Z9WxI-0006i4-2Y@rmm6prod02.runbox.com> <20845.1435678348@chaos>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30/06/2015 17:32, Simon J. Gerraty wrote: > Jeffrey Bouquet <jbtakk@iherebuywisely.com> wrote: > >> If I've a spare /mnt/usr/src , it seems buildworld quite soon fails, >> where it otherwise may succeed in /usr/src. Any CLI parameters or> the >> build system is hardcoded enough so that there will always be >> problems? > > The only thing hard coded is the default MAKEOBJDIRPREFIX (it isn't > called that but it works the same way), but even that should work for any > location. I always have MAKEOBJDIRPREFIX when doing buildworld etc, > and have never used /usr/src. > > Is there perhaps something interesting about /mnt/usr/src (like > ancient?) On some of the systems where I use different versions, I have /usr/srcs mounted of the NFS-server. in which I have. /usr/srcs/src8/src /usr/srcs/src9/src /usr/srcs/src10/src /usr/srcs/head/src Then also have /usr/objs mounted, with the same setup And on the remote systems link /usr/src -> /usr/srcs/src??/src and same for obj.... I have yet to run into trouble when I do the normal things. It gets messy if I'd like to build both i386 and amd64 in the same obj-tree. That does not always work, but adding a differentiating i386 and amd64 to the hierarchy seemed to fix it. But I retired all but one i386, and that is soon to follow. --WjW
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5592E5CF.6020509>