Am 13.04.2017 um 11:53 schrieb Maik Schmidt:
Okay, I think it might be due to the fact that GCC/GCCcore are actually built with the dummy toolchain and so my compiler-specific optarch that only includes "Intel" and "GCC" is not applied there. Can I also add "dummy" to the optarch as another toolchain?Best, Maik Am 13.04.2017 um 10:13 schrieb Maik Schmidt:I have noticed that when doing a GCC/GCCcore build, it always uses the HOST architecture for -march and -mtune starting in compile stage 2, even though I have set something else via optarch. This is a real problem for heterogenous clusters if you do not make sure that the build host always is one with the oldest architecture, because then it leads to the error:"internal compiler error: Illegal instruction" when the resulting GCC is used on an older node.Is this a known issue, or is there a way to make the GCC build process respect what EasyBuild sets as the target architecture, even during the later compile stages?Thank you kindly in advance.
-- Maik Schmidt Technische Universität Dresden Zentrum für Informationsdienste und Hochleistungsrechnen (ZIH) Willers-Bau A116 D-01062 Dresden Telefon: +49 351 463-32836
smime.p7s
Description: S/MIME Cryptographic Signature
