Re: [easybuild] GCCcore build in HMNS

2017-03-08 Thread Vanzo, Davide
o bypass this issue, but it was not correct. Even though I might have had a os package to satisfy dependency some apps did not work correctly especially when they used –with-=$EBROOT From: easybuild-requ...@lists.ugent.be [mailto:easybuild-requ...@lists.ugent.be] On Behalf Of Vanzo, Davide Sent: Wedn

RE: [easybuild] GCCcore build in HMNS

2017-03-08 Thread Siddiqui, Shahzeb
dency some apps did not work correctly especially when they used –with-=$EBROOT From: easybuild-requ...@lists.ugent.be [mailto:easybuild-requ...@lists.ugent.be] On Behalf Of Vanzo, Davide Sent: Wednesday, March 8, 2017 2:09 PM To: easybuild@lists.ugent.be Subject: Re: [easybuild] GCCcore build

Re: [easybuild] GCCcore build in HMNS

2017-03-08 Thread Jack Perdue
On 03/08/2017 01:08 PM, Vanzo, Davide wrote: 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. Which is still

Re: [easybuild] GCCcore build in HMNS

2017-03-08 Thread Vanzo, Davide
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 thi