This is why I have been reluctant to make C++11 the default. There are just too many legacy systems around where it would cause issues. I'm OK with bumping the boost version to 1.55 because I think the impact of that would be minimal but if we have to do much more that that, we may want to hold off until the rest of the world catches up.
On 3/10/2016 9:40 AM, Mark Roszko wrote: > boost 1.55 only adds the the flag you now have to set to workaround. > >> Fixed in Git develop: I've added and documented two config macros: >> BOOST_MATH_USE_FLOAT128 and BOOST_MATH_DISABLE_FLOAT128 which explicitly >> enable/disable this feature. >> Defining the latter macro should fix things for your use case. > > > I think much much newer boost might fix it entirely but its also a > older gcc issue as I don't believe I ran into it on my Windows setup > which is way way more bleeding edge than Ubuntu. > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : [email protected] > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
