Issue building XRootD for O2/QC

O²
1

Hi experts,

While building O2 I run into some issue with XRootD. To me it seems to be some Python issue, I added the log below. I am running ubuntu 21.04 (Hirsute Hippo)

When I aliDoctor O2 I also get FreeType as package that could not be picked up from the system while I have apt-get installed libfreetype-dev, libfreetype6 and libfreetype6-dev. Also OpenSSL is there while I have installed libssl1.0 and libssl-dev

log.txt (68.0 KB)

2

@hristov As it concerns Ubuntu, perhaps you can help ?

3

From the log file it looks like a missing include:

/home/4168658@soliscom.uu.nl/alice/sw/BUILD/f45026d46ef45e18866a8104d8681cc3d9afeaff/XRootD/src/XrdPosix/XrdPosix.cc: In function ‘int XrdPosix_Fstat(int, stat*)’:
/home/4168658@soliscom.uu.nl/alice/sw/BUILD/f45026d46ef45e18866a8104d8681cc3d9afeaff/XRootD/src/XrdPosix/XrdPosix.cc:379:27: error: ‘_STAT_VER’ was not declared in this scope
379 | : Xunix.Fstat64(_STAT_VER, fildes, (struct stat64 *)buf));
| ^~~~~~~~~
/home/4168658@soliscom.uu.nl/alice/sw/BUILD/f45026d46ef45e18866a8104d8681cc3d9afeaff/XRootD/src/XrdPosix/XrdPosix.cc: In function ‘int XrdPosix_Lstat(const char*, stat*)’:
/home/4168658@soliscom.uu.nl/alice/sw/BUILD/f45026d46ef45e18866a8104d8681cc3d9afeaff/XRootD/src/XrdPosix/XrdPosix.cc:563:27: error: ‘_STAT_VER’ was not declared in this scope
563 | ? Xunix.Lstat64(_STAT_VER, path, (struct stat64 *)buf)
| ^~~~~~~~~
/home/4168658@soliscom.uu.nl/alice/sw/BUILD/f45026d46ef45e18866a8104d8681cc3d9afeaff/XRootD/src/XrdPosix/XrdPosix.cc: In function ‘int XrdPosix_Stat(const char*, stat*)’:
/home/4168658@soliscom.uu.nl/alice/sw/BUILD/f45026d46ef45e18866a8104d8681cc3d9afeaff/XRootD/src/XrdPosix/XrdPosix.cc:891:26: error: ‘_STAT_VER’ was not declared in this scope
891 | ? Xunix.Stat64(_STAT_VER, path, (struct stat64 *)buf)

Since Ubuntu 21.04 is quite new, we do not have experience with it. What is the g++ version there?

4

guys, i think that you might want to follow this: Issue compiling XRootD using aliBuild · Issue #1451 · xrootd/xrootd · GitHub
moreover, maybe the deciding factors can push more on the direction of upgrading xrootd to 5.X, see also this announcement: LISTSERV 16.5 - XROOTD-L Archives

1 Like
5

Hi Barthelemy and Peter,

Thanks for the reply! I also asked in the XRootD github and they also pointed to the new compiler: Issue compiling XRootD using aliBuild · Issue #1451 · xrootd/xrootd · GitHub

When I gcc -v I get this output:

Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/10/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 10.3.0-1ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-10/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-10 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-10-gDeRY6/gcc-10-10.3.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-10-gDeRY6/gcc-10-10.3.0/debian/tmp-gcn/usr,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu --with-build-config=bootstrap-lto-lean --enable-link-mutex
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1)
6

@bhofman you could try to use xrootd in development mode (tag 5.1.1) and recompile and see how it goes … the problem would be that you also need a root 6.22

7

Hi Adrian, thanks again for the reply. Do I do this by editing the tag variable in the alidist/xrootd.sh file?

8

Hi! no, i did not do alidist modifications … when i tried the xrootd 5.1 i used it in development mode, meaning that in the directory to be used as target for alibuild i had these:

tree
.
├── alidist -> /home/physics-tools/alice/alidist
├── AliPhysics -> /home/physics-tools/alice/physics-src
├── AliRoot -> /home/physics-tools/alice/trunk-src
├── ROOT -> /home/adrian/GIT-REPOS/root-mygit
└── XRootD -> /home/adrian/GIT-REPOS/xrootd

and the root was checkout to tag v6-22-08 and xrootd to v5.1.1
N.B. you need these exact names in order to be used instead of the versions from sw directory