Just my 2 cents: This is really about a bootstrap procedure for what is presently called the GNU/4.9.3-2.25 module (proposed to be just GCC/4.9.3-binutils-2.25). I think one issue is now that this procedure is user-exposed: all the bits and pieces used in the bootstrap stay there by default, and can be deleted once GNU/4.9.3-2.25 is done.
To have a binutils compiled with GCC 4.9.3 I think is elegant, and I don't see a good reason NOT to do it. However it messes up the dependency chain. In the end with: eb -r GCC-4.9.3-binutils-2.25.eb what I'd like to see is just one and only one user-visible module: GCC/4.9.3-binutils-2.25 (there may of course be extra files, such as for yacc IIRC). loading this module will bring in both GCC and binutils but the two are co-dependent: you always need to load the two together so you might as well use just one module file. of course this is a circular dependency but easybuild could handle that internally, as some kind of "postdepend"? Regards, Bart -- Dr. Bart E. Oldeman | [email protected] | [email protected] Scientific Computing Analyst / Analyste en calcul scientifique McGill HPC Centre / Centre de Calcul Haute Performance de McGill | http://www.hpc.mcgill.ca Calcul Québec | http://www.calculquebec.ca Compute/Calcul Canada | http://www.computecanada.ca Tel/Tél: 514-396-8926 | Fax/Télécopieur: 514-396-8934
