Hi all, While trying to robot-build the foss/2015b toolchain, I ran into https://github.com/hpcugent/easybuild-framework/issues/1402. This led me to take a closer look at the binutils/GCC/GNU setup as implemented in the GNU toolchain. And now I'm wondering why it was implemented that way.
I would have expected that binutils are a dependency (rather than a builddep) of GCC. The reason is that with a hierarchical module naming scheme, it is perfectly valid to not expose the EB toolchains to users by not adding 'Core/toolchain' to the default modulepath. This means that when I (as a software developer) load GCC, I may end up with a broken installation that can't compile code optimized for my platform -- depending on the underlying system-provided binutils. This looks like a major flaw to me... Markus -- Dr. Markus Geimer Juelich Supercomputing Centre Institute for Advanced Simulation Forschungszentrum Juelich GmbH 52425 Juelich, Germany Phone: +49-2461-61-1773 Fax: +49-2461-61-6656 E-Mail: [email protected] WWW: http://www.fz-juelich.de/jsc ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------
