Re: Bug in make setting wrong MAKESYSPATH

2017-05-28 Thread Simon J. Gerraty
Thomas Mueller wrote: > Just because I found a workaround does not mean it is not a bug. Sorry I don't know what else to tell you. make is behaving as it should, based on the way it is configured. That setup was deemed the most useful by those working on src/, so is not

Re: Bug in make setting wrong MAKESYSPATH

2017-05-27 Thread Thomas Mueller
>From Simon J. Gerraty: >> Bug occurs when building or configuring ports, syntax error in >> /BETA1/usr/share/mk/bsd.compiler.mk line 52 >This is of course specific to your particular arrangement >if you'd mounted /BETA1/usr/ports on /usr/ports, it would function as >you wish, or if

Re: Bug in make setting wrong MAKESYSPATH

2017-05-25 Thread Simon J. Gerraty
Thomas Mueller wrote: > When I did those last examples, that last line was > env MAKESYSPATH=/usr/share/mk make all-depends-list ok, that makes sense. > > > and then it seems to work correctly with no syntax error in > > > /BETA1/usr/share/mk/bsd.compiler.mk > > > > > Maybe

Re: Bug in make setting wrong MAKESYSPATH

2017-05-25 Thread Thomas Mueller
>From Simon J. Gerraty: > Thomas Mueller wrote: > > I go into /BETA1/usr/ports/ports-mgmt/synth , run > > env MAKESYSPATH make all-depends-list > I assume you mean MAKESYSPATH=something? otherwise env itself should > vomit When I did those last examples, that last line

Re: Bug in make setting wrong MAKESYSPATH

2017-05-24 Thread Simon J. Gerraty
Thomas Mueller wrote: > I go into /BETA1/usr/ports/ports-mgmt/synth , run > env MAKESYSPATH make all-depends-list I assume you mean MAKESYSPATH=something? otherwise env itself should vomit > and then it seems to work correctly with no syntax error in >

Re: Bug in make setting wrong MAKESYSPATH

2017-05-24 Thread Thomas Mueller
>From Simon J. Gerraty: > > Thomas Mueller 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 > > happened. > Yes. If you look at share/mk/src.sys.env.mk

Re: Bug in make setting wrong MAKESYSPATH

2017-05-24 Thread Simon J. Gerraty
Thomas Mueller 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 happened. Yes. If you look at share/mk/src.sys.env.mk it detects that it was found via a .../

Re: Bug in make setting wrong MAKESYSPATH

2017-05-24 Thread Thomas Mueller
>From Simon J. Gerraty: > Thomas Mueller wrote: > > It seems to me that MAKESYSPATH should match the host building system > > FreeBSD version. > Which would only be correct if building the same version of FreeBSD as > is running on the host. > Many folk work on

Re: Bug in make setting wrong MAKESYSPATH

2017-05-23 Thread Simon J. Gerraty
Thomas Mueller wrote: > It seems to me that MAKESYSPATH should match the host building system > FreeBSD version. Which would only be correct if building the same version of FreeBSD as is running on the host. Many folk work on multiple branches on the same machine. Thus for

Re: Bug in make setting wrong MAKESYSPATH

2017-05-23 Thread Thomas Mueller
> On Sun, May 21, 2017 at 1:54 AM, Thomas Mueller wrote: > > I tried building ports, starting with ports-mgmt/synth, on HEAD > > (12-current) and ran into difficulties with syntax error in bsd.compiler.mk > > . > > With PORTSDIR on another partition, mounted as /BETA1, I

Re: Bug in make setting wrong MAKESYSPATH

2017-05-22 Thread Ngie Cooper
On Sun, May 21, 2017 at 1:54 AM, Thomas Mueller wrote: > I tried building ports, starting with ports-mgmt/synth, on HEAD (12-current) > and ran into difficulties with syntax error in bsd.compiler.mk . > > With PORTSDIR on another partition, mounted as /BETA1, I got these

Re: Bug in make setting wrong MAKESYSPATH

2017-05-22 Thread Simon J. Gerraty
Thomas Mueller wrote: > I tried building ports, starting with ports-mgmt/synth, on HEAD > (12-current) and ran into difficulties with syntax error in > bsd.compiler.mk . > > With PORTSDIR on another partition, mounted as /BETA1, I got these > errors, but not when I