Hi Keith,
On 06/03/14 22:09, Keith Hostetler wrote:
I see. Do you need a tar file to create every toolchain? If not, what else do
you use as the source?
Usually, a toolchain involves a compiler and a bunch of libraries (most
commonly MPI, BLAS, LAPACK, FFT).
See https://github.com/hpcugent/easybuild/wiki/Compiler-toolchains for
more details.
So, most commonly toolchains are basically bundles of a handful of
tools, for which EasyBuild knows how to prepare.
You'll need source tarballs or installation files for each of the
toolchain elements, but the toolchain itself doesn't have any sources of
its own.
regards,
Kenneth
________________________________________
From: [email protected] [[email protected]] On Behalf Of Ward Poelmans
[[email protected]]
Sent: Wednesday, March 05, 2014 9:48 AM
To: [email protected]
Subject: Re: [easybuild] Toolchains
On Tue, Mar 4, 2014 at 9:27 PM, Keith Hostetler
<[email protected]> wrote:
You say that it is normal for the dependencies to fail, but if they fail then
it won't use them and thus won't create the software. As I said, I used GCC as
my toolchain, but when I do, it fails due to unresolved dependencies and so I
don't get a software compilation. Do I need to build GCC's toolchain too?
Yes, you need to build a GCC toolchain with easybuild. I suppose that
until now, you've used a system gcc?
Easybuild is build aroud the idea that it is in full control: the
entire (well, almost entire), toolchain is build by easybuild.
Ward