On 10/12/2012 05:00, matt wrote:
I have made changes to ports/Mk/bsd.gcc.mk that allow the addition of
USE_GCC=any to a port's Makefile, and then committed that change to
various ports. In most (but not all!) cases this will tell the port
build with gcc instead of clang (*) .
Why not
On 10/12/12 00:54, Claude Buisson wrote:
On 10/12/2012 05:00, matt wrote:
I have made changes to ports/Mk/bsd.gcc.mk that allow the addition of
USE_GCC=any to a port's Makefile, and then committed that change to
various ports. In most (but not all!) cases this will tell the port
build with
I have made changes to ports/Mk/bsd.gcc.mk that allow the addition of
USE_GCC=any to a port's Makefile, and then committed that change to
various ports. In most (but not all!) cases this will tell the port
build with gcc instead of clang (*) .
Why not USE_GCC ?= any for the poor guys like
On 10/10/2012 02:45, Mark Linimon wrote:
The commit mail hasn't gone through yet, so I guess I need to post this
first and reference the commit mail later.
Sometime in the near future, the default CC on -current will be switched
to clang. The patch I have committed is a workaround -- an
Can we arrange exp builds with FORCE_BASE_CC_FOR_TESTING=clang that
will report all ports with USE_GCC=* but build with clang?
Lets say every three months or so?
On Tue, Oct 09, 2012 at 07:45:23PM -0500, Mark Linimon wrote:
The commit mail hasn't gone through yet, so I guess I need to post this
On Wed, Oct 10, 2012 at 05:11:07PM +0200, Roman Divacky wrote:
Can we arrange exp builds with FORCE_BASE_CC_FOR_TESTING=clang that
will report all ports with USE_GCC=* but build with clang?
Sure. That was kind of the intention.
mcl
___
The commit mail hasn't gone through yet, so I guess I need to post this
first and reference the commit mail later.
Sometime in the near future, the default CC on -current will be switched
to clang. The patch I have committed is a workaround -- an interim measure --
to get ready for this
