Shahzeb, Looks good to me. It is expected that GCCcore depends on dummy toolchain built software since that is the only toolchain below GCCcore. In other words, you need whatever has been built with the system compiler and binutils in order to compile GCCcore. Once you have GCCcore built, at this point you will use it to compile again M4/Bison/flex/zlib/binutils within the GCCcore toolchain so that whatever is built with GCC is completely independent from the underlying OS software stack.
-- Davide Vanzo, PhD Application Developer Adjunct Assistant Professor of Chemical and Biomolecular Engineering Advanced Computing Center for Research and Education (ACCRE) Vanderbilt University - Hill Center 201 www.accre.vanderbilt.edu On Mar 8 2017, at 12:58 pm, Siddiqui, Shahzeb <shahzeb.siddi...@pfizer.com> wrote: Hello, I want to find out if the build for GCCcore 5.4.0 is suppose to look like this under HMNS. I have copied all the files from easybuild repo into my local directory because I have disabled robot paths. One thing I don’t understand why there is M4 and binutils built with GCCcore toolchain while it also is a dependency in GCCcore. When I tried to build GCCcore-5.4.0 the dependency picks up M4 and binutils from dummy toolchain. I want to hide GCCcore and its deps, is this the correct way to do this. hpcswadm@hpcv18$eb GCCcore-5.4.0.eb -D --hidden --hide-deps=M4,Bison,flex,zlib,binutils == temporary log file in case of crash /tmp/eb-mZkRzA/easybuild-xv6sEZ.log Dry run: printing build status of easyconfigs and dependencies CFGS=/hpc/hpcswadm/easybuild * [ ] $CFGS/M4/M4-1.4.17.eb (module: Core | M4/.1.4.17) * [ ] $CFGS/Bison/Bison-3.0.4.eb (module: Core | Bison/.3.0.4) * [ ] $CFGS/flex/flex-2.6.0.eb (module: Core | flex/.2.6.0) * [ ] $CFGS/zlib/zlib-1.2.8.eb (module: Core | zlib/.1.2.8) * [ ] $CFGS/binutils/binutils-2.26.eb (module: Core | binutils/.2.26) * [ ] $CFGS/GCCcore/GCCcore-5.4.0.eb (module: Core | GCCcore/.5.4.0) Regards, Shahzeb Siddiqui HPC Linux Engineer B2220-447.2 Groton, CT
