http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53490
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-05-26 00:02:13 UTC --- (In reply to comment #4) > It was a vanilla bjam build of boost 1.49, so > no -std=c++11. Then technically that's not supported, since there are no guarantees of link-compatibility between -std=c++98 and -std=c++11 code (but I'm not aware of any specific reasons it wouldn't work for a std::set) (In reply to comment #5) > For clarity I should say I just tried with a vanilla build of 1.47 and get > essentially the same backtrace here. I don't think the build of boost 1.47 I used earlier was non-vanilla in any way, and I get no segfault on Fedora 16 using the system's boost-static-1.47.0-6.fc16.x86_64.rpm with: ~/gcc/4.7/bin/g++ j.cc -std=c++11 -Wl,-Bstatic -lboost_program_options -Wl,-Bdynamic Is it significant that you link statically? Does it fail in the same way if you link dynamically?
