I’d argue that binutils are not compilers, and that they are irrelevant for most users. Besides that, looks good to me. We have a similar table on a per-stage basis, but it is currently only exposed to our internal group.
Damian On 06/04/17 06:13, "[email protected] on behalf of Jack Perdue" <[email protected] on behalf of [email protected]> wrote: Howdy all, At some point in the past year I blatantly lied to Kenneth by claiming we had a web page that clearly explains to our users what components are in each toolchain while we use a flat (non-hierarchical) module naming scheme. Since then I've/we've made such a page. :) https://hprc.tamu.edu/wiki/index.php/SW:Toolchains Does it make sense to EB builders? Would your users understand it???? What could be done to make it easier for users to grasp? We have LOTS of novice users so its always hard for me (who's been doing UNIX for 30+ years now) to relate what is important. Thanks for any feedback (whether I agree or not), -- Jack Perdue Lead Systems Administrator High Performance Research Computing TAMU Division of Research [email protected] http://hprc.tamu.edu HPRC Helpdesk: [email protected] ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------
