On Thu, 5 Sep 2013 21:39:42 +0200, Tijl Coosemans writes:
>fmake does set it. It goes something like this:
>
>1) the port makefiles are all named Makefile so fmake sets
> MAKEFILE=Makefile. With bmake this is sometimes an absolute path.
IIRC it will be an absolute path anytime .OBJDIR!=.CURDIR
On Thu, 5 Sep 2013 17:59:36 +, Alexey Dokuchaev writes:
>Yes, I've seen the fresh import; will test it tomorrow. I'm not sure what
>is the problem, but "ports should be able to control the value of MAKEFILE
>as desired" looks strange. MAKEFILE is one of the standard bsd.port.mk's
bmake trea
With the new version of bmake (20130904), ports should be able to
control the value of MAKEFILE as desired.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-un
The following reply was made to PR conf/181116; it has been noted by GNATS.
From: "Simon J. Gerraty"
To: Garrett Cooper
Cc: "freebsd-gnats-sub...@freebsd.org" ,
"freebsd-bugs@FreeBSD.org"
Subject: Re: conf/181116: CURRENT build always uses bmake, even thou
On Wed, 7 Aug 2013 11:24:15 -0700, Garrett Cooper writes:
>Ah, but src.conf controls WITH* (and the option is documented in the manage,=
> along with all the others). You accidentally broke POLA :(.
The real issue is that the option handling needs an overhaul.
The processing of options should be
The following reply was made to PR conf/181116; it has been noted by GNATS.
From: "Simon J. Gerraty"
To: Garrett Cooper
Cc: "freebsd-gnats-sub...@freebsd.org" ,
"freebsd-bugs@FreeBSD.org"
Subject: Re: conf/181116: CURRENT build always uses bmake, even thou
Also the synopsis is somewhat missleading.
It only doesn't work when WITHOUT_BMAKE is specified in src.conf which
src/Makefile does not honor - so would apply to any WITH[OUT]_ knob.
But the larger question is why you are wanting to use fmake
Thanks
--sjg
_
The following reply was made to PR conf/181116; it has been noted by GNATS.
From: "Simon J. Gerraty"
To: Garrett Cooper
Cc: "freebsd-gnats-sub...@freebsd.org" ,
"freebsd-bugs@FreeBSD.org"
Subject: Re: conf/181116: CURRENT build always uses bmake, even thou
src/Makefile does not read bsd.own.mk so does not see src.conf
it does however see make.conf
More importantly, is this a "test" or is there a percieved need to
continue building with fmake? If so why?
I was aiming to get rid of WITH[OUT]_BMAKE soon - in time for 10.0
_
On Mon, 15 Apr 2013 00:43:46 -0400, Glen Barber writes:
>Currently, FreeBSD's make(1). But my src.conf has not changed (as far
>as build options) in several months.
Thanks - fwiw a buildworld with FreeBSD's make(1) and all the options you
mentioned (plus WITH_BMAKE of course) finished successful
On Mon, 15 Apr 2013 00:30:39 -0400, Glen Barber writes:
>Possible. For what it is worth, the only WITH_* entries in my src.conf
>are:
>
> WITH_BIND_UTILS=3Dyes
> WITH_BSD_GREP=3D yes
> WITH_BSD_PATCH=3D yes
> WITH_IDEA=3D yes
> WITH_MAIL=3D yes
>
>This looks exactly like the same problem I reported to you in private
Yes it does. As noted; the error is the result of bmake passing its
-J flag onto an invokation of the old make.
The prevelance of makefiles which have bare invocations of 'make' mean
that's a reasonable possibility when /usr/b
FWIW the buildworld I just did (with freebsd make as /usr/bin/make)
finished ok (tree updated to r249461), and lots of previous builds used
bmake as /usr/bin/make. I'll rebuild this same tree that way...
Yep, that complete ok too.
> I'm rebuilding world right now so it might be due to a
On Sat, 13 Apr 2013 22:54:41 -0700, Garrett Cooper writes:
>The tree is synched up to the latest head version. I'm suspecting it =
>might be something to do with the changes made over the past 2 weeks in =
>terms of /Makefile, but I could be wrong. I'll look into this further =
>when I can..
I've
On Sat, 13 Apr 2013 21:26:17 -0700, Garrett Cooper writes:
> The summary could be a bit better. Basically "buildworld with =
>bmake installed as make does not work with WITH_BMAKE specified on =
>CURRENT on next compile".
>HTH,
Hmm, I've been building current with buildworld and bmake as ma
On Wed, 24 Oct 2012 11:54:30 +0400, Andrey Chernov writes:
>so only bmake case left unfixed.
It's fixed in bmake-20121010 which I need to import.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubsc
On Sun, 7 Oct 2012 01:48:35 -0700, Garrett Cooper writes:
>Correction -- bmake hates empty strings for commands too...
That's interesting. I thought I fixed that back in May..
Ok, that was something like @${EMPTY}
This is a variant of the same thing - will fix - in make.
In the meantime, yo
17 matches
Mail list logo
