Re: C++11

On 05/16/2014 12:43 PM, Stephen Leake wrote:
>> Does that g++ version compile plain nvm? That's is using the very same
>> standard library functions from <algorithm>...
> 
> But options.hh does not have "#include <algorithm> ". Adding that fixes
> the problem; mtn compiles (tests running ...).

Good, that means the compiler and standard libraries are just fine,
which I'm glad.

> Apparently "#include <algorithm>" is implied somehow, or included in
> another include file, in nvm?

Maybe C++11 is more restrictive on including header (or allows the
library to be written so). Sounds like we want to add that include to
nvm as well.

>> If so, it looks like the m4 macro is failing to do its job properly.
> 
> config.log says it checks 'g++' first (default language version), then
> 'g++ -std=gnu++11', and that works, so it is used.
> 
> So yes, this is a bug in the m4 macro.

Interesting, I thought I tested that. But you're right, this looks like
the macro doesn't do what it's supposed to do. It itself claims:

#   The first argument, if specified, indicates whether you insist on an
#   extended mode (e.g. -std=gnu++11) or a strict conformance mode (e.g.
#   -std=c++11).  If neither is specified, you get whatever works, with
#   preference for an extended mode.

I left it unspecified, as I'm fine with whatever works (tm).

I corrected the order of tests, now. So for gcc, it now yields the c++??
rather than gnu++?? variants.

Regards

Markus Wanner

_______________________________________________
Monotone-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/monotone-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iEYEAREDAAYFAlN194sACgkQsPwMloDjyo8l0ACggIh9VHBrv1fbjE5RlXW8/y47
4oMAniN3wvMBcC/6grzAUNBjEU8MNBK/
=iNnZ
-----END PGP SIGNATURE-----