Re: -current broken when src is on NFS

From: Tim Kientzle <tim_at_kientzle.com>
Date: Fri, 17 Jul 2015 21:29:47 -0700
> On Jul 16, 2015, at 9:57 PM, O'Connor, Daniel <darius_at_dons.net.au> wrote:
> 
> 
>> On 16 Jul 2015, at 21:41, Rick Macklem <rmacklem_at_uoguelph.ca> wrote:
>> r285066 fixed a POLA violation w.r.t. the old NFS client where the new
>> client didn't return an EEXIST error return for symlink or mkdir to userland.
>> The behaviour of not returning this error to userland (which was inherited from
>> OpenBSD and was not the behaviour of the old FreeBSD NFS client but was default
>> for the new NFS client) can be enabled via:
>> vfs.nfs.ignore_eexist=1
>> 
>> You could try setting that sysctl and seeing if it makes any difference?
>> 
>> That is the only recent change to the NFS client that *might* affect this.
> 
> No dice :(
> 
> It's pretty weird, it bombs out if either src or obj is on NFS..
> But even weirder is that if I build with crochet (a wrapper for cross building to arm) it works. It doesn't work if I cross build manually and I haven't been able to determine why crochet works yet.

Crochet defaults MAKEOBJDIRPREFIX to ${WORKDIR}/obj if you have not already set it to something else.  (This avoids cross-polluting the builds if you do regular manual cross-builds on the same machine.)

If you’re having issues with /usr/obj being on NFS, that could be a factor.

Tim
Received on Sat Jul 18 2015 - 02:30:10 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:58 UTC