On 2 April 2017 at 15:11, Yann E. MORIN <[email protected]> wrote: > Hello, > > On 2017-03-08 18:23 +0100, Yann E. MORIN spake thusly: >> When a C++ compiler is not found, then AC_PROG_CXX will set CXX to >> 'false'. >> >> However, we test that we can find $CXX, and indeed false exists in >> the PATH, for virtually all systems we have a chance to be compiled >> on. So we conclude that we do have a C++ compiler, when this is >> clearly wrong. >> >> Improve our hack by trying to run the C++ compiler with a benign call, >> that should succeed if the CXX is really a C++ compiler: tell it to dump >> its pre-defined macros. >> >> Signed-off-by: "Yann E. MORIN" <[email protected]> >> Reviewed-by: Peter Hutterer <[email protected]> > > Ping? ;-) > Renamed g++ and c++ and CXX and ends up being set to g++ :-\ Perhaps there's something broken on my end ?
An alternative solutions is drop the "which" all together and make this a configure toggle. Default to disabled and toggle at make distcheck via AM_DISTCHECK_CONFIGURE_FLAGS. This way the release manager will ensure that tarballs with 'broken' headers are not shipped. That should also work if CXX is set to "false", is and empty string or set to the wrong value. -Emil _______________________________________________ wayland-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/wayland-devel
