Hi Åke,
The make actually fails as shown below. There are hundreds of configure
and checking lines above the lines I display, and the first make command
fails as shown in the output.
Can you suggest anything else to check? Are there issues with AVX512 on
Skylake, and if so, how to work around it?
FYI, the foss-2018a and foss-2018b toolchains have been built without
problems on the Skylake node.
Thanks,
Ole
On 20-02-2019 18:01, Åke Sandgren wrote:
That's not the real problem.
You have to look through that log and figure out what it really is.
I.e., where does the make actually fail.
On 2/20/19 4:10 PM, Ole Holm Nielsen wrote:
On 2/20/19 2:45 PM, Åke Sandgren wrote:
What is the actual error? Look in
/tmp/eb-dyNH9x/easybuild-binutils-2.31.1-20190220.140138.qdBpn.log
It's:
$ tail /tmp/eb-dyNH9x/easybuild-binutils-2.31.1-20190220.140138.qdBpn.log
config.status: executing default commands
make[1]: Leaving directory
`/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1'
make: *** [all] Error 2
(at easybuild/tools/run.py:501 in parse_cmd_output)
== 2019-02-20 14:02:45,435 easyblock.py:2870 WARNING build failed (first
300 chars): cmd " env LIBS='-Wl,-rpath=/usr/lib -Wl,-rpath=/usr/lib64'
make -j 80 CFLAGS="-g -O2 -fPIC" " exited with exit code 2 and output:
make[1]: Entering directory
`/home/modules/build/binutils/2.31.1/dummy-/binutils-2.31.1'
make[1]: Nothing to be done for `all-target'.
Configuring in ./libiberty
Config
== 2019-02-20 14:02:45,435 easyblock.py:288 INFO Closing log for
application name binutils version 2.31.1
