> From: Hans-Peter Nilsson <h...@axis.com> > Date: Fri, 24 Oct 2014 06:32:06 +0200
> The libcpp configure checks are actually run with gcc which is > bogus by itself, but apparently working. I guess the C vs. C++ > declaration etc. differences for libcpp are mostly hidden by > using _GNU_SOURCE (through AC_USE_SYSTEM_EXTENSIONS), and I'm a > bit surprised that's not used for libiberty and fixincludes. Bah, I was confused by a cached value; strike "and fixincludes". > Still, a red herring. brgds, H-P
