I am trying to compile O2 on a remote machine running CentOS 7.
The error occurs while building DDS.
When I am logged in on the remote machine I am in a group called domänen-benutzer and apparently this leads to a problem while translating this name to UTF-8.
CMake Error: archive_write_header: Can't translate gname 'domänen-benutzer' to UTF-8
CMake Error: Problem creating tar: dds-wrk-bin-2.0-Linux-amd64.tar.gz
The way I’m building O2 is just as described online using aliBuild.
aliBuild init O2 --defaults o2
aliBuild build O2 --defaults o2
The full logfile and the output of ‘aliDoctor O2 --defaults o2’ can be found with the following link.
Thank you very much!
I think that the best would be to contact the DDS people directly, for example here : https://github.com/FairRootGroup/DDS/issues
Alright, thank you for your help!
the DDS people say it’s a cmake problem and possibly provided a fix including some minor changes in the cmake source files. Am I right assuming the cmake source files that are used are in $ALIBUILD_WORK_DIR/SOURCES/CMake/v3.11.0/v3.11.0/Source?
Then I would need to build cmake again before attempting to build DDS. However, when I type aliBuild build O2 --defaults o2, cmake is not built again using my changes but the cached cmake is used.
So how can I trigger aliBuild to build the modified cmake even though it has a cached build already?
oh, so it is a cmake bug ? interesting.
If you want to modify cmake and rebuild it you would have to
init cmake :
aliBuild init CMake
A directory with the source files is created. Modify the source code and whenever you will rebuild O2 it should rebuild cmake and use it.
Ah so this is easier than I thought.