Date: Wed, 24 May 2017 10:04:54 -0700 From: "Simon J. Gerraty" <sjg@juniper.net> To: Thomas Mueller <mueller6722@twc.com> Cc: <freebsd-current@freebsd.org>, Ngie Cooper <yaneurabeya@gmail.com>, <sjg@juniper.net> Subject: Re: Bug in make setting wrong MAKESYSPATH Message-ID: <24672.1495645494@kaos.jnpr.net> In-Reply-To: <BF.E8.25473.8AA45295@dnvrco-omsmta03> References: <4E.66.25473.9D551295@dnvrco-omsmta03> <81057.1495500066@kaos.jnpr.net> <CAGHfRMCC6KzywEL==_=EoH_JxmQQu2aRsU-tag8pa5M-1UD%2Bcw@mail.gmail.com> <E3.CD.25473.3CCD3295@dnvrco-omsmta03> <95058.1495555282@kaos.jnpr.net> <BF.E8.25473.8AA45295@dnvrco-omsmta03>
next in thread | previous in thread | raw e-mail | index | archive | help
Thomas Mueller <mueller6722@twc.com> wrote: > For building the system, MAKESYSPATH should be $SRCDIR/share/mk , to be = in sync. > = > I tried "make -V MAKESYSPATH" from several SRCDIRs, and that's what happ= ened. Yes. If you look at share/mk/src.sys.env.mk it detects that it was found via a .../ path, and replaces it in MAKESYSPATH with the actual location - otherwise some makefiles break. > So maybe I have to set MAKESYSPATH every time I am in ports, don't > know if this would work from /etc/make.conf (need to experiment). Probably not, because sys.mk will have already been found before that ie. the damage may already have been done = > I wonder what would happen if there is no FreeBSD installation at all > on partition where ports tree is located. An error like: make: no system rules (sys.mk). > = > > Yes, but requires you to keep /usr/share/mk in sync with whatever you = a > > building, tricky if you build head, stable/10 and stable/11 on the > > same box. > = > I don't think you have to do that, since I find that MAKESYSPATH > becomes $SRCDIR/share/mk . Per above; that's due to the default .../share/mk I was speaking about alternatives to that magic value. Thanks --sjg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24672.1495645494>