Hello @harmonic
As an after thought to what I said earlier try running this in the container before executing the Gross_test_01
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/full_path_of_libgross.so
Hello @harmonic
As I said earlier run this statement before running your code.
I have made a correction only folder path needs to be included not the filename.
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/full_path_of_folder_containing_libgross.so
Please run this immediately before running Gross_test_01. It should work. Then you would not need C++ in the container at all.
If your libraries are statically bound into Gross_test_01 and the OS in the host and docker is the same, I don't expect that C++ is needed in the container.
The basic principle is that C++ compiles a program to machine language. If all libraries are statically bound, then nothing should be needed as long as OS is the same.
The size of the executable would however be large.
However if the libraries are dynamically linked then libraries are needed.
I think this is not a Sas problem anymore, I don't know maybe is the virtual container the problem.
Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 25. Read more here about why you should contribute and what is in it for you!
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.