Re: [Boost-users] conflicting intmax_t definitions - Boost 1.53 and gcc 4.8 incompatibility?

Subject: Re: [Boost-users] conflicting intmax_t definitions - Boost 1.53 and gcc 4.8 incompatibility?
From: Nate Finch (nate.finch_at_[hidden])
Date: 2014-01-21 14:16:16

Yeah, I don't know what is different, but I was able to at least get myself
working by removing some using statements and manually specifying the boost
namespace where needed.  No idea why it was working before and why it's
broken now, though.  Not originally my code... we'll see if anyone else
ends up hitting it who has more time to look into it than I do.

Thanks for the help.

On Mon, Jan 20, 2014 at 8:21 AM, John Maddock <john_at_[hidden]>wrote:

> Yes, there are some using namespace boost statements, and some of them are
>> before some includes... but why would that suddenly break when it was
>> working before I upgraded?  Is boost now defining its own intmax_t (and
>> other such tings, like uint64_t) where it wasn't before?
>>
>
> No, nothing in that part of Boost has changed for some time I believe.
>
> Boost does define it's own intmax_t etc *in namespace boost*, if you
> import these into the global namespace then expect things to break, sorry
> but that's the way it's *always* been.  My guess is it worked before
> because the Boost and std lib versions happened to be identical by chance.
>
>
> John.
> _______________________________________________
> Boost-users mailing list
> Boost-users_at_[hidden]
> http://lists.boost.org/mailman/listinfo.cgi/boost-users
>