That's pretty interesting to me, because it's the same result I have, but it works fine for my compile/linker whereas your compiler/linker appears to be insisting on having the last parameter as a plain std::string const& instead of accepting the c++11 version. What versions of gcc and ld are you using? Mine are
Although the gnu.org docs state that gcc began "fully supporting" c++11 beginning with gcc 4.8.1, it is not until gcc 5.1 that they cite libstdc++ as having full support for c++11. It looks to me like the current version of gcc for Ubuntu 16.04 is >= 5.3.1, so could you update gcc (and probably best all the packages needed by FO) and then try compiling again? (and perhaps double check that you don't for some reason have 'gcc' aliased to an older version, perhaps try running 'gcc-5 --version' to see if you already have a newer gcc installed?)
If I provided any code, scripts or other content here, it's released under GPL 2.0 and CC-BY-SA 3.0
OK well I think we have probably more clearly identified the source of your problem, though I'm still not sure about the full scope of it or just the best way to fix it. if you run
But it also seems conceivable that some of your libraries might be symlinked to older versions also, if you don't know of any particular reason to keep the old gcc on your system it might be that the best approach would be to go into your package-manager/software-center (or just use apt) and uninstall the older gcc and then reinstall/repair the newer gcc. But I really don't know.
If I provided any code, scripts or other content here, it's released under GPL 2.0 and CC-BY-SA 3.0