-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot open shared object file #134
Comments
@Mark-Anderton try running it from the terminal, prepend a blank LD_LIBRARY_PATH i.e. |
@makeclean thank you very much for your quick reply! Unfortunately, that's not made any difference, I'm still getting the same error. |
ok, could you list the contents of the svalinn plugin directory? showing the various .so or .dylib files? |
I believe the problem might come from a change in the Cubit root folder: when we build the plugin for linux, the path to various lib are hardcoded into the libs... using We need to build a new version of the plugin for |
a temporary fix might be to run :
then run as |
Thank you both for your input, I have tried building the plugin from source and have tried running it with the suggestions made by @bam241. Unfortunately, this made no difference. @makeclean as per your request, please see the contense of the svalinn plugin directory listed below:
In the mean time, is there a docker container that I could use that has coreform cubit and the DAGMC plugin setup? Thanks all! |
Maybe your system is being super picky, make a symbolic link between libMOAB.so and libMOAB.so.5
Get Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Mark-Anderton ***@***.***>
Sent: Monday, July 18, 2022 2:20:14 PM
To: svalinn/Cubit-plugin ***@***.***>
Cc: Davis, Andrew ***@***.***>; Mention ***@***.***>
Subject: Re: [svalinn/Cubit-plugin] Cannot open shared object file (Issue #134)
Thank you both for your input,
I have tried building the plugin from source and have tried running it with the suggestions made by @bam241<https://github.com/bam241>. Unfortunately, this made no difference.
@makeclean<https://github.com/makeclean> as per your request, please see the contense of the svalinn plugin directory listed below:
***@***.***:/opt/Coreform-Cubit-2022.6/bin/plugins/svalinn$ ls libcfplugincmd.so libmakeWatertight.so libpyne_dagmc.so libdagmc.so libmaterial_commands.so libsvalinn_plugin.so libhdf5.so libmcnp2cad.so libuwuw.so libiGeom.so libMOAB.so libworkspacecmd.so
In the mean time, is there a docker container that I could use that has coreform cubit and the DAGMC plugin setup?
Thanks all!
—
Reply to this email directly, view it on GitHub<#134 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AASTUSSAGGYTEHTTZFJM563VUVKY5ANCNFSM53O4MV6A>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I decided to start again and setup a new VM running ubuntu 20.04 and try and install the 2021.11 plugin on Coreform Cubit 2022.6. I also decided to run the commands listed by @bam241 for all of the files in the
While this is hard for me to make sense of, what I understand is that the DAGMC plugin has been loaded correctly but it fails with a SIGSEGV signal and a SEGV_MAPER filed id. I haven't been able to figure out what might be causing these problems do you have any ideas? |
I've been trying to build the DAGMC plugin from source when following the instructions on this page I get the error |
@Mark-Anderton we are working on building the plugin for cubit 2022.6. those have been built correctly but have not been tested, so they might not work :) |
Because I need to use a non-commercial license I need to use Corefoam Cubit 2022.6. Fully knowing that there isn't a DAGMC plugin for this version yet I've tried running 2022.6 with the 2021.11 plugin and run into the following error:
dlopen ERROR /opt/Coreform-Cubit-2022.6/bin/./plugins/libsavlinn_plugin.so : libMOAB.so.5 : cannot open shared object file : No such file or directory
Is this error likely the result of the fact that I'm trying to use the 2021.11 plugin with Cubit 2022.6 or something else? If its something else, how could I go about fixing it?
The text was updated successfully, but these errors were encountered: