ROOT CLING stopped working after underlying system change

jkusnier · November 13, 2020, 2:17pm

ROOT Version: 6.22.0 with patches
Platform: AWS Linux 2
Compiler: g++ ? (I used -DCMAKE_CXX_COMPILER=/usr/bin/g++ flag, but I’m not sure what’s the compiler nor how to check which is used)

Context: I have created a custom ROOT compilation for AWS Lambda and was able to successfully run it on Python3.8 Lambda a month ago after compiling ROOT on dockerized amazonlinux:2.

The command I use for downloading ROOT:
git clone --branch v6-22-00-patches https://github.com/root-project/root.git

However, since then some underlying change inside linux broke cling. Here’s a stacktrace (very long):

This stacktrace is coming from executing this script:

github.com

vepadulano/PyRDF/blob/master/tutorials/local/sequential/df001_introduction.py

## \file
## \ingroup tutorial_dataframe
## \notebook -nodraw
## This tutorial illustrates the basic features of the RDataFrame class,
## a utility which allows to interact with data stored in TTrees following
## a functional-chain like approach.
##
## \macro_code
##
## \date May 2017
## \author Danilo Piparo

import ROOT, PyRDF

# A simple helper function to fill a test tree: this makes the example stand-alone.
def fill_tree(treeName, fileName):
    tdf = ROOT.ROOT.RDataFrame(10)
    tdf.Define("b1", "(double) tdfentry_")\
       .Define("b2", "(int) tdfentry_ * tdfentry_").Snapshot(treeName, fileName)

This file has been truncated. show original

As mentioned, previously this worked fine both on AWS Lambda and on docker container based on amazonlinux:2. The issue happened only on AWS Lambda without any input from my side: I changed nothing in my deployment package, so it must be something with underlying system difference. I’m kind of lost how to solve this stacktrace due to my mediocre C++ experience. Any clues how I could debug it?

jblomer · November 14, 2020, 3:04pm

@vvassilev Do you have an idea?

vvassilev · November 14, 2020, 4:22pm

If the default compiler was changed it could be the reason of seeing this. Can you recompile ROOT and see if the issue persists?

jkusnier · November 21, 2020, 11:43am

I recompiled ROOT in cmake DEBUG mode to use Clang as compiler, and now I got this specific message:

python3.7: /root_src/interpreter/cling/lib/Interpreter/CIFactory.cpp:587: {anonymous}::collectModuleMaps(clang::CompilerInstance&, llvm::SmallVectorImpl<std::__cxx11::basic_string<char> >&)::<lambda(llvm::StringRef, const string&, const string&, std::__cxx11::string&)>: Assertion llvm::sys::fs::exists(SystemDir) && “Must exist!”’ failed.`

Context:

/root_src is where git repo was cloned
/mnt/cern_root/root is where i run cmake with this flag: -DCMAKE_INSTALL_PREFIX=/mnt/cern_root/root_install
/mnt/cern_root/root_install is where it should install (?) according to this flag^

I tested on docker with only /mnt/cern_root/root_install existing out of these and it worked.
In Lambda environment it failed with error as you can see above.

My thoughts:

For some reason, the installed ROOT still targets original /root_src dir which i removed, as I thought root_install (install location) would sufffice.
I might need to copy some more things from source code dir/compilation dir to install dir, but I have no idea why they were left behind.

For more info how I compiled a docker script:

@vvassilev Can you tell me how can I fix that exception? All help is greatly appreciated.

Edit: In original (docker) location it works correctly even after removing both /root_src and /mnt/cern_root/root, but for some reason on Lambda it fails as you can see.

vvassilev · November 21, 2020, 3:03pm

Could you break with the debugger and print SystemDir? I suspect it is /usr/include, if that’s the case you need to install libc.

jkusnier · November 21, 2020, 5:24pm

That was it, I needed to a) provide libcxx with my installation and b) target CPATH to include it from nonstandard location (at my /mnt/… dir) . Thank you very much for help @vvassilev

vvassilev · November 21, 2020, 5:59pm

Glad to help!

system · December 5, 2020, 5:59pm

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.