I am sorry, but I think that I don't like such a radical solution; I understand that as a developer you need to have a working copy of MG5 but as an user I don't see the necessity to use gnu compilers. Clang works perfectly fine (with the *only* exception of MG5 at the moment), is meant to optimise performances on OSX and therefore I am not willing to change it.
However, I temporarily changed g++/gcc/c++ and I build boost, lhapdf 6.1.5 (which now includes YAML that apparently causes the problem) and I tried to run MG5 but I keep finding the same error. At this point I am not sure what could be the solution; I may need to rebuild everything with gnu compilers to be sure that everything is consistent, but this is something that I don't want to do.
Ciao Marco,
I am sorry, but I think that I don't like such a radical solution; I understand that as a developer you need to have a working copy of MG5 but as an user I don't see the necessity to use gnu compilers. Clang works perfectly fine (with the *only* exception of MG5 at the moment), is meant to optimise performances on OSX and therefore I am not willing to change it.
However, I temporarily changed g++/gcc/c++ and I build boost, lhapdf 6.1.5 (which now includes YAML that apparently causes the problem) and I tried to run MG5 but I keep finding the same error. At this point I am not sure what could be the solution; I may need to rebuild everything with gnu compilers to be sure that everything is consistent, but this is something that I don't want to do.
Thanks
Luca