Re: Clang vs. GCC arm

[Lloyd Parkes <lloyd%must-have-coffee.gen.nz@localhost>]

On 3/01/2017, at 2:59 PM, Matt Thomas <matt%3am-software.com@localhost> wrote:

On Jan 1, 2017, at 7:15 PM, Lloyd Parkes <lloyd%must-have-coffee.gen.nz@localhost> wrote:

Blather...

# Disable use of pre-compiled headers on Darwin.
.if ${BUILD_OSTYPE} == "Darwin"
CPPFLAGS+=    -no-cpp-precomp
.endif

I needed to nuke this in every location order to build with GCC. 

Is there a right way to centralise this? I’ve noticed that FreeBSD and Solaris hosted builds might also benefit from this, although to a lesser extent.

Cheers,

It's easier for me to add -fbracket-depth=1000 to HOST_CPPFLAGS and just use clang.

You have to know how to drive that first, and I already know how to drive pkgsrc.

Also, when I added "-V HOST_CPPFLAGS=-fbracket-depth=1000” to my build.sh command line, host-mkdep choked on that extra flag. I have to use "-V HOST_CXXFLAGS=-fbracket-depth=1000”, which may have been what you meant in the first place.

Coming back to my original question though, can we just put this stuff in share/mk/bsd.host.mk? I realise that this will affect all of the tools built on Darwin and not just the half dozen or so that need it, and I’m fine with that.

Cheers,

Lloyd