Re: -current broken when src is on NFS

2015-07-19 Thread Simon J. Gerraty
> Given that we have (or at least had at one time) some of those magical > "..." paths that cause bmake to search up the hierarchy for its .mk > files, I wonder if an odd relationship between src and obj dir confuses > it, or if it somehow wanders into a wrong src tree while searching? Based on Da

Re: -current broken when src is on NFS

2015-07-19 Thread David Wolfskill
On Sun, Jul 19, 2015 at 10:31:36AM -0600, Ian Lepore wrote: > > I've been following this saga (on irc and here) as much as I have time > for, and I can't escape the feeling that it is the directory structure > at fault somehow, but I can't quite put my finger on it. > > I never (ever) build f

Re: -current broken when src is on NFS

2015-07-19 Thread Ian Lepore
On Sat, 2015-07-18 at 10:26 -0700, Simon J. Gerraty wrote: > O'Connor, Daniel wrote: > > However, Crochet _does_ build on the NFS client _and_ when the source > > tree isn't in /usr/src which makes this issue very strange :-/ > > I've seen similar errors in rescue... (no NFS) though I cannot > q

Re: -current broken when src is on NFS

2015-07-18 Thread Simon J. Gerraty
O'Connor, Daniel wrote: > However, Crochet _does_ build on the NFS client _and_ when the source > tree isn't in /usr/src which makes this issue very strange :-/ I've seen similar errors in rescue... (no NFS) though I cannot quite recall the cause other than it seems very sensitive to MAKEOBJDIRP

Re: -current broken when src is on NFS

2015-07-17 Thread O'Connor, Daniel
> On 18 Jul 2015, at 13:59, Tim Kientzle wrote: > 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

Re: -current broken when src is on NFS

2015-07-17 Thread Tim Kientzle
> On Jul 16, 2015, at 9:57 PM, O'Connor, Daniel wrote: > > >> On 16 Jul 2015, at 21:41, Rick Macklem 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 returni

Re: -current broken when src is on NFS

2015-07-17 Thread O'Connor, Daniel
> On 17 Jul 2015, at 14:27, O'Connor, Daniel wrote: >> On 16 Jul 2015, at 21:41, Rick Macklem 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 e

Re: -current broken when src is on NFS

2015-07-16 Thread O'Connor, Daniel
> On 16 Jul 2015, at 21:41, Rick Macklem 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 a

Re: -current broken when src is on NFS

2015-07-16 Thread Rick Macklem
Daniel O'Conner wrote: > I am seeing the following breakage when building -current and the source is > on NFS > > make -j 4 buildworld > ... > --- rescue.all__D --- > --- rescue --- > MAKEOBJDIRPREFIX=/usr/obj/src/FreeBSD-HEAD/rescue/rescue make -f rescue.mk > exe > --- sbin.all__D --- > --- pfctl

-current broken when src is on NFS

2015-07-16 Thread O'Connor, Daniel
I am seeing the following breakage when building -current and the source is on NFS make -j 4 buildworld ... --- rescue.all__D --- --- rescue --- MAKEOBJDIRPREFIX=/usr/obj/src/FreeBSD-HEAD/rescue/rescue make -f rescue.mk exe --- sbin.all__D --- --- pfctl_qstats.o --- cc -O2 -pipe -Wall -Wmissin