Compile/build EOS on a Rocky host


Can you please give me some pointers how to compile and build EOS from source on a Rocky host? I think I should at lines 433-456 in

but if you could confirm that would be great.



Hi Gerge,

You have a step by step workflow here on how to build eos:

Indeed, the lines that you referenced are also a good start for compiling it yourself from source. Furthermore, you have the actual build steps in the file at the top of EOS repository.


Hi Elvin,

Thanks for this. Combining stuff from the yml and the eos-docs, I followed these steps which worked nicely and resulted in the generation of rpms.

Can you please confirm the options for the cmake3 step? It is mentioned that “To build EOS, you need gcc (>=7) with C++17 features and CMake installed on your system”. Even after specifying -DCMAKE_CXX_STANDARD=17 for the generation of the srpm, I did see warnings during compilation (but none of which was fatal for compilation)

  • git clone dss / eos · GitLab

  • cd eos/

  • git checkout tags/4.8.103

  • git submodule sync --recursive && git submodule update --init -f --recursive

  • mkdir build; cd build

  • cmake3 …/ -DPACKAGEONLY=1 -DCMAKE_CXX_STANDARD=17 -Wno-dev

  • make srpm

  • Create cat /etc/yum.repos.d/eos-depend.repo

name=EOS dependencies
baseurl=Index of /storage-ci/eos/citrine-depend/el-8/x86_64

  • yum-builddep --nogpgcheck --setopt=“cern*.exclude=xrootd*” -y build/SRPMS/*

  • rpmbuild --rebuild --with server --define “_rpmdir build/RPMS/” --define “_build_name_fmt %%{NAME}-%%{VERSION}-%%{RELEASE}.%%{ARCH}.rpm” build/SRPMS/* | ts

Hi George,

Yes, all looks correct. The warnings that you see at compilation are expected.


Thanks Elvin. Managed, also to build EOS5 following the above procedure. I noticed the following

what is the difference between them (el-8 vs el-8s).

  • When I run the yum-builddep step, no xrootd packages (xrootd-lib, etc) were installed unlike the case of EOS4. Is this expected.

  • These are the rpms I generated. Does look like the full list to you?

[root@host-172-16-110-108 eos]# ls -lrt build/RPMS/
total 609900
-rw-r–r-- 1 root root 199955788 Sep 15 11:08 eos-server-5.1.8-1.el8.x86_64.rpm
-rw-r–r-- 1 root root 32295792 Sep 15 11:08 eos-ns-inspect-5.1.8-1.el8.x86_64.rpm
-rw-r–r-- 1 root root 6248 Sep 15 11:09 eos-fusex-5.1.8-1.el8.x86_64.rpm
-rw-r–r-- 1 root root 35069504 Sep 15 11:09 eos-client-5.1.8-1.el8.x86_64.rpm
-rw-r–r-- 1 root root 29090872 Sep 15 11:09 eos-fusex-core-5.1.8-1.el8.x86_64.rpm
-rw-r–r-- 1 root root 8588 Sep 15 11:09 eos-fusex-selinux-5.1.8-1.el8.x86_64.rpm
-rw-r–r-- 1 root root 50801404 Sep 15 11:09 eos-quarkdb-5.1.8-1.el8.x86_64.rpm
-rw-r–r-- 1 root root 7416 Sep 15 11:09 eos-testkeytab-5.1.8-1.el8.x86_64.rpm
-rw-r–r-- 1 root root 50404 Sep 15 11:09 eos-archive-5.1.8-1.el8.x86_64.rpm
-rw-r–r-- 1 root root 277218728 Sep 15 11:11 eos-test-5.1.8-1.el8.x86_64.rpm
-rw-r–r-- 1 root root 8460 Sep 15 11:11 eos-cleanup-5.1.8-1.el8.x86_64.rpm

Thanks again,


Hi George,

The el-8s was aimed at CentosStream8 builds (which we won’t provide anymore) and the el-8 covers Alma/Rocky/RHEL8. What was the error that you were getting when using the el-8 one? This should work in principle.

Yes, in EOS 5 we rely only on eos-xrootd by default to build the eos packages so it’s normal.

The list of packages that you got is complete so everything looks fine from my point of view.