Error install with upcxx 2020
Module list:
- StdEnv (S)
- GCCcore/7.3.0
- zlib/1.2.11-GCCcore-7.3.0 (H)
- binutils/2.30-GCCcore-7.3.0 (H)
- GCC/7.3.0-2.30
- hpcx/2.4
- OpenMPI/3.1.1-GCC-7.3.0-2.30
- OpenBLAS/0.3.1-GCC-7.3.0-2.30
- gompi/2018b
- FFTW/3.3.8-gompi-2018b
- ScaLAPACK/2.0.2-gompi-2018b-OpenBLAS-0.3.1
- foss/2018b
- bzip2/1.0.6-GCCcore-7.3.0 (H)
- ncurses/6.1-GCCcore-7.3.0 (H)
- libreadline/7.0-GCCcore-7.3.0 (H)
- GMP/6.1.2-GCCcore-7.3.0 (H)
- libffi/3.2.1-GCCcore-7.3.0 (H)
- Python/2.7.15-foss-2018b
Where:
S: Module is Sticky, requires --force to unload or purge
H: Hidden Module
(base) [cnphuong@login-2.SAGA ~/downloads/upcxx-2020.3.0]$ echo $CXX
mpicxx
(base) [cnphuong@login-2.SAGA ~/downloads/upcxx-2020.3.0]$ echo $CC
gcc./install ~/upcxx
ERROR
GASNet configuration:
Portable conduits:
Portable SMP-loopback conduit (smp) ON (enabled)
Portable UDP/IP conduit (udp) ON (auto)
Portable MPI conduit (mpi) ON (auto)
Native, high-performance conduits:
Unified Communication X conduit (ucx) OFF (auto)
InfiniBand IB Verbs conduit (ibv) ON (auto)
Cray XC Aries conduit (aries) OFF (not found)
Some conduits require --enable-XXX configure flags and/or additional
variables providing the install location of vendor drivers.
See the GASNet documentation for details.
Misc Settings
MPI compatibility: yes
Pthreads support: yes
Segment config: fast
PSHM support: posix
BLCR support: no
Atomics support: native
PMI support: yes (version=x)
make[1]: *** [Makefile:532: install] Error 2
UPC++ installation failed. Please report the ENTIRE log above to: upcxx@googlegroups.com
make[1]: *** [/cluster/home/cnphuong/downloads/upcxx-2020.3.0/bld/Makefile.rules:86: failure] Error 1
make: *** [/cluster/home/cnphuong/downloads/upcxx-2020.3.0/bld/Makefile.rules:35: install] Error 2
UPC++ Installation failed. Please report the ENTIRE log above to: upcxx@googlegroups.com
Last time, I installed it, and it worked.
Comments (5)
-
-
-
assigned issue to
-
assigned issue to
-
reporter - attached error.log
I try to install with version 2019.9. There is the same error. Please see the attached file.
Thanks
-
reporter - changed status to resolved
The server links to gcc in Anaconda3. I delete it on bashrc file. And it worked.
-
- changed status to invalid
Hi Ngoc -
As explained in the error message, the problem is these variables set in your environment:
checking for CFLAGS setting... (provided) "-march=nocona -mtune=haswell -ftree-vectorize -fPIC -fstack-protector-strong -fno-plt -O2 -ffunction-sections -pipe -isystem /cluster/software/Anaconda3/2019.03/include" checking for CPP setting... (provided) "/cluster/software/Anaconda3/2019.03/bin/x86_64-conda_cos6-linux-gnu-cpp" checking for CPPFLAGS setting... (provided) "-DNDEBUG -D_FORTIFY_SOURCE=2 -O2 -isystem /cluster/software/Anaconda3/2019.03/include" checking for LDFLAGS setting... (provided) "-Wl,-O2 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -Wl,--disable-new-dtags -Wl,--gc-sections -Wl,-rpath,/cluster/software/Anaconda3/2019.03/lib -Wl,-rpath-link,/cluster/software/Anaconda3/2019.03/lib -L/cluster/software/Anaconda3/2019.03/lib" checking for CXXFLAGS setting... (provided) "-fvisibility-inlines-hidden -std=c++17 -fmessage-length=0 -march=nocona -mtune=haswell -ftree-vectorize -fPIC -fstack-protector-strong -fno-plt -O2 -ffunction-sections -pipe -isystem /cluster/software/Anaconda3/2019.03/include"
It looks like some of these were probably injected by the Anaconda python software, so you might start by unloading whatever module pulled that in. Otherwise you can just change these variables in your environment before running the UPC++ installer.
You'll need to remove at least
-O2
and-DNDEBUG
from all of these variables. Also, theCPP
setting is probably wrong and should also be unset. - Log in to comment
Sorry to hear of your problems.
However, you have not provided enough information for us to diagnose the issue.
Please attach the entire output of the failed run of the installation.
You can find "Attach files" under the "More v" button near the upper-right corner of the Bitbucket issue tracker page.
I would additionally encourage you to use the new configure-based installation process rather than the legacy
./install
script. Please read INSTALL.md for details.However, if you wish to continue using the legacy installer, it would be helpful if you could set
UPCXX_MAKE=make
in your environment to disable parallelism in the install process (making the error messages easier to read).