lspci | grep -i mellanox
will show if you have any mellanox devices on the system, some of these could 
be used as normal ethernet devices though

ibstatus
will show if any of those are running in Infiniband mode

If ibstatus doesn't exist then you probably don't have infiniband, or at least 
lack the packages for using it.

________________________________________
From: easybuild-requ...@lists.ugent.be <easybuild-requ...@lists.ugent.be> on 
behalf of Joaquim Jornet Somoza <j.jornet.som...@gmail.com>
Sent: Friday, March 15, 2024 11:44
To: easybuild@lists.ugent.be
Subject: Re: [easybuild] Failure in UCX-1.14.1-GCCcore-12.3.0.eb when 
installing foss-2023a.eb

Dear Ake,

How can I check this?

Thank you!

El vie, 15 mar 2024, 7:58, Åke Sandgren 
<ake.sandg...@umu.se<mailto:ake.sandg...@umu.se>> escribió:
No there is no bug there.

Which MOFED stack version are you using?
Or does your system lack Infiniband?

________________________________________
From: easybuild-requ...@lists.ugent.be<mailto:easybuild-requ...@lists.ugent.be> 
<easybuild-requ...@lists.ugent.be<mailto:easybuild-requ...@lists.ugent.be>> on 
behalf of Joaquim Jornet Somoza 
<j.jornet.som...@gmail.com<mailto:j.jornet.som...@gmail.com>>
Sent: Thursday, March 14, 2024 16:02
To: easybuild@lists.ugent.be<mailto:easybuild@lists.ugent.be>
Subject: [easybuild] Failure in UCX-1.14.1-GCCcore-12.3.0.eb when installing 
foss-2023a.eb

Dear easybuilders,

I am trying to install foss-2023a.eb on a RH7.7 servers, but when installing 
UCX-1.14.1-GCCcore-12.3.0.eb , the installation fails with the following error:
...
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../.. "-DCPU_FLAGS=|avx" 
-I/dev/shm/easybuild/UCX/1.14.1/GCCcore-12.3.0/ucx-1.14.1/src 
-I/dev/shm/easybuild/UCX/1.14.1/GCCcore-12.3.0/ucx-1.14.1 
-I/dev/shm/easybuild/UCX/1.14.1/GCCcore-12.3.0/ucx-1.14.1/src 
-I/software/easybuild/x86_64/software/numactl/2.0.16-GCCcore-12.3.0/include 
-I/software/easybuild/x86_64/software/zlib/1.2.13-GCCcore-12.3.0/include 
-I/software/easybuild/x86_64/software/pkgconf/1.9.5-GCCcore-12.3.0/include 
-I/software/easybuild/x86_64/software/binutils/2.40-GCCcore-12.3.0/include -O3 
-g -Wall -Werror -mavx -funwind-tables -Wno-missing-field-initializers 
-Wno-unused-parameter -Wno-unused-label -Wno-long-long -Wno-endif-labels 
-Wno-sign-compare -Wno-multichar -Wno-deprecated-declarations -Winvalid-pch 
-Wno-pointer-sign -Werror-implicit-function-declaration -Wno-format-zero-length 
-Wnested-externs -Wshadow -Werror=declaration-after-statement -O2 
-ftree-vectorize -march=native -fno-math-errno -fPIC -MT 
rc/verbs/libuct_ib_la-rc_verbs_ep.lo -MD -MP -MF 
rc/verbs/.deps/libuct_ib_la-rc_verbs_ep.Tpo -c rc/verbs/rc_verbs_ep.c -o 
rc/verbs/libuct_ib_la-rc_verbs_ep.o >/dev/null 2>&1
base/ib_md.c: In function 'uct_ib_md_access_flags':
base/ib_md.c:638:25: error: 'IBV_ACCESS_ON_DEMAND' undeclared (first use in 
this function); did you mean 'IBV_EXP_ACCESS_ON_DEMAND'?
  638 |         access_flags |= IBV_ACCESS_ON_DEMAND;
      |                         ^~~~~~~~~~~~~~~~~~~~
      |                         IBV_EXP_ACCESS_ON_DEMAND
base/ib_md.c:638:25: note: each undeclared identifier is reported only once for 
each function it appears in
base/ib_md.c: In function 'uct_ib_mem_reg_internal':
base/ib_md.c:751:24: error: 'IBV_ACCESS_ON_DEMAND' undeclared (first use in 
this function); did you mean 'IBV_EXP_ACCESS_ON_DEMAND'?
  751 |     if (access_flags & IBV_ACCESS_ON_DEMAND) {
      |                        ^~~~~~~~~~~~~~~~~~~~
      |                        IBV_EXP_ACCESS_ON_DEMAND
base/ib_md.c: In function 'uct_ib_md_global_odp_init':
base/ib_md.c:1449:54: error: 'IBV_ACCESS_ON_DEMAND' undeclared (first use in 
this function); did you mean 'IBV_EXP_ACCESS_ON_DEMAND'?
 1449 |                            UCT_IB_MEM_ACCESS_FLAGS | 
IBV_ACCESS_ON_DEMAND,
      |                                                      
^~~~~~~~~~~~~~~~~~~~
      |                                                      
IBV_EXP_ACCESS_ON_DEMAND


Any hint on how to fix it? Is there a bug with IBV_ACCESS_ON_DEMAND variable?

Reply via email to