I’m not a python guy, but generally speaking, your C cross compiler is complaining about an undefined symbol. That, in turn, says there is a library you have to link against, but the library is missing.
The “mangled” symbol is “_ZNSt16invalid_argumentD1Ev”. If you pipe that via echo through “c++filt”, then the unmangled function/method which is missing is: std::invalid_argument::~invalid_argument()
The particular method is a destructor. Depending on your Linux release, the declaration would be in “/usr/include/c++/...version.../stdexcept”. That’s actually for the local system, and not the cross tool install, but the destructor would be the same, and it shows as virtual. Thus your code must define the destructor to use it:
virtual ~invalid_argument() _GLIBCXX_NOTHROW;
If you have a library which actually implements this, then it would be from a cross install to an aarch64 version of the C++ standard library. Otherwise, the library might be there (and probably is), but the code has to define the destructor. Code behavior might depend on the release used, so this might work as is in some releases, but fail in others. I couldn’t tell you what the cause is for this case (the choice is that the release version is causing this to be an error, or that the cross library for C++ has something missing).
@developer.makarov@sarodeanil35 I also have a prototype pip server that caches the wheels built by jetson-containers now, you can find info about it here: