It's especially useful to know because this list can expect the same problem to be reported as a bug in BPL repeatedly from now on :)
Did you submit the bug to GCC's bugzilla, and if you did do you have a link? If you didn't, submitting it and having it rejected is worth doing just so we can link to the bug from here. Niall On 18 May 2012 at 20:28, Jonas Wielicki wrote: > On 18.05.2012 19:47, Niall Douglas wrote: > > So it was a bug in GCC after all. Useful to know. > Sorry that I forgot to mention. I was pretty sure it was the GCC after I > tried with two different Boost versions and the very same code was > running fine on gcc 4.6.3 platforms. It is not 100% bulletproof, but I > guess its the GCCs fault. > > -- > Jonas > _______________________________________________ > Cplusplus-sig mailing list > Cplusplus-sig@python.org > http://mail.python.org/mailman/listinfo/cplusplus-sig -- Technology & Consulting Services - ned Productions Limited. http://www.nedproductions.biz/. VAT reg: IE 9708311Q. Work Portfolio: http://careers.stackoverflow.com/nialldouglas/ _______________________________________________ Cplusplus-sig mailing list Cplusplus-sig@python.org http://mail.python.org/mailman/listinfo/cplusplus-sig
