On 06/26/14 09:36, Nathan Whitehorn wrote:
On 06/26/14 08:44, Baptiste Daroussin wrote:
On Thu, Jun 26, 2014 at 08:35:14AM -0700, Nathan Whitehorn wrote:
On 06/26/14 03:02, Alexey Dokuchaev wrote:
On Wed, Jun 25, 2014 at 07:23:05AM -0700, Justin Hibbits wrote:
As I mentioned earlier, you can set "FAVORITE_COMPILER=gcc" in
make.conf, and it'll build with gcc47.
FAVORITE_COMPILER looks more like a hack to me. Ideally boost's port
Makefile should be fixed instead.
I also would rather use system compiler (whether it's gcc4.2 or clang)
instead of gcc47.
./danfe
Yes, it should be made to respect whatever cc is.
As long as cc is supported upstream, boost being a nightmare to
maintain I will
reject all patches that are not accepted upstream first, otherwise
bumping to
1.56 will be painful.
That said I fully support the effort.
regards,
Bapt
Surely there's a way to pass the compiler that you want to bjam at the
command line.
-Nathan
As a follow-up, it is using clang because the ports system tells it to,
not because of something in boost. boost has c++11-lang in its Makefile,
which makes bsd.compiler.mk set CXX to clang++, which boost then uses.
-Nathan
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
