Re: don't include CFLAGS in CXXFLAGS

2015-04-28 Thread Jonathan Gray
On Fri, Jul 18, 2014 at 12:10:25AM +1000, Jonathan Gray wrote: sys.mk automatically gets included by make(1) and sets CXXFLAGS to CFLAGS. If a Makefile defines additional CFLAGS they will then be passed to the C++ compiler. Which creates problems with flags that should only be used by the C

don't include CFLAGS in CXXFLAGS

2014-07-17 Thread Jonathan Gray
sys.mk automatically gets included by make(1) and sets CXXFLAGS to CFLAGS. If a Makefile defines additional CFLAGS they will then be passed to the C++ compiler. Which creates problems with flags that should only be used by the C compiler in Makefiles that deal with both C and C++ (like Mesa).

Re: don't include CFLAGS in CXXFLAGS

2014-07-17 Thread Stuart Henderson
On 2014/07/18 00:10, Jonathan Gray wrote: sys.mk automatically gets included by make(1) and sets CXXFLAGS to CFLAGS. If a Makefile defines additional CFLAGS they will then be passed to the C++ compiler. Which creates problems with flags that should only be used by the C compiler in Makefiles

Re: don't include CFLAGS in CXXFLAGS

2014-07-17 Thread Vadim Zhukov
2014-07-17 16:13 GMT+02:00 Stuart Henderson st...@openbsd.org: On 2014/07/18 00:10, Jonathan Gray wrote: sys.mk automatically gets included by make(1) and sets CXXFLAGS to CFLAGS. If a Makefile defines additional CFLAGS they will then be passed to the C++ compiler. Which creates problems