How do you handle the binutils dependency for other software (like mpich)? I have been using the GCC-4.9.2-binutils-2.25 version on a haswell node. Binutils is required to build GCC, but it is also required to build other software with GCC. However, those packages do not list binutils (either version) as a dependency. My hack to get around the problem was change the plain binutils module in a regular “dependency” rather than a builddependency. Probably not the best solution but to be honest I think the GCC-4.9.x-binutils-2.25 sort of implies that it is included.
Brett > On Sep 2, 2015, at 7:42 AM, Ward Poelmans <[email protected]> wrote: > > On Wed, Sep 2, 2015 at 2:39 PM, Backeljauw Franky > <[email protected]> wrote: >> I’m wondering: why do I have both binutils/2.25 and >> binutils/2.25-GCC-4.9.3-binutils-2.25 (the same for Bison, flex, M4, zlib)? >> Are the non-GCC-versions actually used, or are they just dependencies needed >> to built the GCC-versions? > > binutils/2.25 is build with the system compiler and used to bootstrap > GCC. After that we build binutils/2.25-GCC-4.9.3-binutils-2.25 and use > it. Bison & co are deps needed to build binutils. > > In principle, you can delete binutils/2.25 (and deps). > > Ward
