List of Open Source Software which can be built on Fugaku
 |
Spack will be used to manage open source software packages on Fugaku.
Fugaku users can easily use pre-installed packages and built packages based on Spack recipes.
The following list shows the results of building/compiling packages for aarch64 according to the Spack recipes.
Note that the results in this list do not guarantee that each package will work properly.
On the other hand, Fujitsu will provide the following packages compiled with Fujitsu compiler on Fugaku as "external" packages, of which Spack can be aware.
|
atlas 3.10.3
| Compiler | Fujitsu Compiler Fujitsu C/C++ Compiler 4.10.0 tcsds-1.2.38 |
|---|---|
| Result | Dependency Error |
Failed Reason
Failed to install dependency package :
------------------------------------------------
==> Warning: config:terminal_title has been replaced by install_status and is ignored
==> Warning: Failed to initialize repository: '$spack/var/spack/repos/local'.
No repo.yaml found in '$spack/var/spack/repos/local'
To remove the bad repository, run this command:
spack repo rm $spack/var/spack/repos/local
==> Installing atlas-3.10.3-572odzqd4l62uvqqip4pd7mywnwyfmny [1/1]
==> No binary for atlas-3.10.3-572odzqd4l62uvqqip4pd7mywnwyfmny found: installing from source
==> Fetching https://spack-llnl-mirror.s3-us-west-2.amazonaws.com/_source-cache/archive/26/2688eb733a6c5f78a18ef32144039adcd62fabce66f2eb51dd59dde806a6d2b7.tar.bz2
==> Fetching https://spack-llnl-mirror.s3-us-west-2.amazonaws.com/_source-cache/archive/9a/9ad8f0d3f3fb5521db49f2dd716463b8fb2b6bc9dc386a9956b8c6144f726352.tgz
==> Moving resource stage
source: /data/rccs-sdt/a01008/tmpdir/spack-stage/resource-lapack-572odzqd4l62uvqqip4pd7mywnwyfmny/spack-src/
destination: /data/rccs-sdt/a01008/tmpdir/spack-stage/spack-stage-atlas-3.10.3-572odzqd4l62uvqqip4pd7mywnwyfmny/spack-src/spack-resource-lapack/lapack-3.5.0
==> Ran patch() for atlas
==> atlas: Executing phase: 'install'
==> Error: ProcessError: Command exited with status 1:
'./../configure' '--prefix=/vol0003/rccs-sdt/data/a01008/spack-all-test/env-20240227/spack/opt/spack/linux-rhel8-a64fx/fj-4.10.0/atlas-3.10.3-572odzqd4l62uvqqip4pd7mywnwyfmny' '--shared' '-b' '64' '-t' '-1' '-C' 'ic' '/vol0003/rccs-sdt/data/a01008/spack-all-test/env-20240227/spack/lib/spack/env/fj/fcc' '-C' 'if' '/vol0003/rccs-sdt/data/a01008/spack-all-test/env-20240227/spack/lib/spack/env/fj/frt' '--with-netlib-lapack-tarfile=/data/rccs-sdt/a01008/tmpdir/spack-stage/resource-lapack-572odzqd4l62uvqqip4pd7mywnwyfmny/lapack-3.5.0.tgz'
7 warnings found in build log:
>> 6 /vol0003/rccs-sdt/data/a01008/tmpdir/spack-stage/spack-stage-atlas-3
.10.3-572odzqd4l62uvqqip4pd7mywnwyfmny/spack-src/spack-build/./..//C
ONFIG/include/atlas_sys.h:224: warning: the use of `tmpnam' is dange
rous, better use `mkstemp'
7 ./xconfig -d s ./../ -d b /vol0003/rccs-sdt/data/a01008/tmpdir/spack
-stage/spack-stage-atlas-3.10.3-572odzqd4l62uvqqip4pd7mywnwyfmny/spa
ck-src/spack-build -D c -DATL_DYLIBS -b 64 -t -1 -C ic /vol0003/rcc
s-sdt/data/a01008/spack-all-test/env-20240227/spack/lib/spack/env/fj
/fcc -C if /vol0003/rccs-sdt/data/a01008/spack-all-test/env-20240227
/spack/lib/spack/env/fj/frt -Si lapackref 1
8 probe_OS.o: In function `ATL_tmpnam':
>> 9 /vol0003/rccs-sdt/data/a01008/tmpdir/spack-stage/spack-stage-atlas-3
.10.3-572odzqd4l62uvqqip4pd7mywnwyfmny/spack-src/spack-build/./..//C
ONFIG/include/atlas_sys.h:224: warning: the use of `tmpnam' is dange
rous, better use `mkstemp'
10 probe_asm.o: In function `ATL_tmpnam':
>> 11 /vol0003/rccs-sdt/data/a01008/tmpdir/spack-stage/spack-stage-atlas-3
.10.3-572odzqd4l62uvqqip4pd7mywnwyfmny/spack-src/spack-build/./..//C
ONFIG/include/atlas_sys.h:224: warning: the use of `tmpnam' is dange
rous, better use `mkstemp'
12 probe_vec.o: In function `ATL_tmpnam':
>> 13 /vol0003/rccs-sdt/data/a01008/tmpdir/spack-stage/spack-stage-atlas-3
.10.3-572odzqd4l62uvqqip4pd7mywnwyfmny/spack-src/spack-build/./..//C
ONFIG/include/atlas_sys.h:224: warning: the use of `tmpnam' is dange
rous, better use `mkstemp'
14 probe_arch.o: In function `ATL_tmpnam':
>> 15 /vol0003/rccs-sdt/data/a01008/tmpdir/spack-stage/spack-stage-atlas-3
.10.3-572odzqd4l62uvqqip4pd7mywnwyfmny/spack-src/spack-build/./..//C
ONFIG/include/atlas_sys.h:224: warning: the use of `tmpnam' is dange
rous, better use `mkstemp'
16 /data/rccs-sdt/a01008/tmpdir/ccZ0BHs8.o: In function `ATL_tmpnam':
>> 17 /vol0003/rccs-sdt/data/a01008/tmpdir/spack-stage/spack-stage-atlas-3
.10.3-572odzqd4l62uvqqip4pd7mywnwyfmny/spack-src/spack-build/./..//C
ONFIG/include/atlas_sys.h:224: warning: the use of `tmpnam' is dange
rous, better use `mkstemp'
18 probe_pmake.o: In function `ATL_tmpnam':
>> 19 /vol0003/rccs-sdt/data/a01008/tmpdir/spack-stage/spack-stage-atlas-3
.10.3-572odzqd4l62uvqqip4pd7mywnwyfmny/spack-src/spack-build/./..//C
ONFIG/include/atlas_sys.h:224: warning: the use of `tmpnam' is dange
rous, better use `mkstemp'
20 It appears you have cpu throttling enabled, which makes timings
21 unreliable and an ATLAS install nonsensical.
22
23 OS-controlled CPU throttling is so course grained, that timings beco
me
24 essentially random. What this means for an ATLAS install is that AT
LAS
25 cannot tell the difference between a good and bad kernel, and so the
See build log for details:
/data/rccs-sdt/a01008/tmpdir/spack-stage/spack-stage-atlas-3.10.3-572odzqd4l62uvqqip4pd7mywnwyfmny/spack-build-out.txt
<= Back to list