uilding components: server=yes mom=yes clients=yes
gui=no drmaa=no pam=no
PBS Machine type : linux
Remote copy : /bin/scp -rpB
PBS home : /var/spool/torque
Default server : localhost.localdomain
Unix Domain sockets :
Linux cpusets : no
Tcl : disabled
Tk : disabled
Authentication : trqauthd
configure: WARNING: This compilation has strict compiler options enabled that cause
the build to fail if any compiler warnings are emitted. If this build fails
because of a harmless warning, please report the problem to torqueusers@supercluster.org
and run configure again without --enable-gcc-warnings.
//
mv -f .deps/attr_atomic.Tpo .deps/attr_atomic.Po
g++ -DHAVE_CONFIG_H -I. -I…/…/…/src/include -I…/…/…/src/include xml2-config --cflags -g -D_LARGEFILE64_SOURCE -fstack-protector -Wformat -Wformat-security -DFORTIFY_SOURCE=2 -W -Wall -Wextra -Wno-unused-parameter -Wno-long-long -Wpedantic -Werror -Wno-sign-compare -MT attr_fn_acl.o -MD -MP -MF .deps/attr_fn_acl.Tpo -c -o attr_fn_acl.o attr_fn_acl.c
attr_fn_acl.c: In function ‘int set_allacl(pbs_attribute*, pbs_attribute*, batch_op, int ()(char, char*))’:
attr_fn_acl.c:502:20: error: this statement may fall through [-Werror=implicit-fallthrough=]
502 | pas->as_next = pas->as_buf;
| ~^
attr_fn_acl.c:506:5: note: here
…
-DHAVE_CONFIG_H -I. -I…/…/…/src/include -I…/…/…/src/include xml2-config --cflags -g -D_LARGEFILE64_SOURCE -fstack-protector -Wformat -Wformat-security -DFORTIFY_SOURCE=2 -W -Wall -Wextra -Wno-unused-parameter -Wno-long-long -Wpedantic -Werror -Wno-sign-compare -MT attr_fn_acl.o -MD -MP -MF .deps/attr_fn_acl.Tpo -c -o attr_fn_acl.o attr_fn_acl.c
attr_fn_acl.c: In function ‘int set_allacl(pbs_attribute*, pbs_attribute*, batch_op, int ()(char, char*))’:
attr_fn_acl.c:502:20: error: this statement may fall through [-Werror=implicit-fallthrough=]
502 | pas->as_next = pas->as_buf;
| ~^
attr_fn_acl.c:506:5: note: here
506 | case INCR_OLD:
| ^~~~
cc1plus: all warnings being treated as errors
make[4]: *** [Makefile:623: attr_fn_acl.o] Error 1
make[4]: Leaving directory ‘/opt/torque/src/lib/Libattr’
make[3]: *** [Makefile:677: all-recursive] Error 1
make[3]: Leaving directory ‘/opt/torque/src/lib/Libattr’
make[2]: *** [Makefile:489: all-recursive] Error 1
make[2]: Leaving directory ‘/opt/torque/src/lib’
make[1]: *** [Makefile:500: all-recursive] Error 1
make[1]: Leaving directory ‘/opt/torque/src’
configure: WARNING: This compilation has strict compiler options enabled that cause
the build to fail if any compiler warnings are emitted. If this build fails
because of a harmless warning, please report the problem to torqueusers@supercluster.org
and run configure again without --enable-gcc-warnings.
You posted the solution yourself. Just do what the warning says.
II installed Slurm23 only on debian 11
so far. I downloaded the tarball and added the missing libraries. I launched it. configure make mske_install. tomorrow I will try to install it on Rocky. I have Torque running 11 years old on Centos 6 continuously without shutdown and failures up to this day
I installed Slurm without problems on Rocky from tarball. Extract the tarball then ./configure then make then make install.And Torque probably died like CentOS 8
The convenience of rpmbuild -ta xyz.tar.bz2 is that one gets xyz.rpm (if the tarball has support fro RPM builds, which the slurm does) and then the benefits of package manager are yours.
(Note: EPEL has SLURM RPM’s. I do exclude those, because I want to control when
SLURM gets upgraded – their docs describe the “special needs” of the upgrade process.)
The make install of source build has potentially two issues:
It could overwrite files of packages
Does it have “make uninstall” for the day you want to upgrade to new version?
That said, I do some source (and proprietary blob) installs, but when I do
they go to distinct prefixes (that usually are on shared NFS volume) so that
they can’t overwrite anything nor will be overwritten by any other version.
The “uninstall” becomes “remove directory (tree)”.
The added benefit of distinct paths is that one can have multiple versions.
That is something that RPM does not neatly support, although Red Hat
has Software Collections (SCL). One probably does not need more than one
version of SLURM at a time.
Non-standard locations are not on PATH? True. For that there are environment modules. We did shift to Lmod (from EPEL) with el9
while in el7 we have environment-modules.
The scl utility (of SCL) is similar to the module implementations.
I am engaged in parallel computing and such details do not interest me. I installed slurm and it works and that’s enough for me
See:
The simplest way to build and install this package is:
‘cd’ to the directory containing the package’s source code and type
‘./configure’ to configure the package for your system. If you’re
using ‘csh’ on an old version of System V, you might need to type
‘sh ./configure’ instead to prevent ‘csh’ from trying to execute
‘configure’ itself.
Running ‘configure’ takes awhile. While running, it prints some
messages telling which features it is checking for.
Type ‘make’ to compile the package.
Optionally, type ‘make check’ to run any self-tests that come with
the package.
Type ‘make install’ to install the programs and any data files and
documentation.
