Aptech Systems, Inc. Worldwide Headquarters
Aptech Systems, Inc.
2350 East Germann Road, Suite #21
Chandler, AZ 85286
Ready to Get Started?
Request Quote & Product Information
Training & Events
Step-by-step, informative lessons for those who want to dive into GAUSS and achieve their goals, fast.
Have a Specific Question?
Q&A: Register and Login
Premier Support and Platinum Premier Support are annually renewable membership programs that provide you with important benefits including technical support, product maintenance, and substantial cost-saving features for your GAUSS System or the GAUSS Engine.
Join our community to see why our users are considered some of the most active and helpful in the industry!
Where to Buy
Recent Tagsapplications character vectors CML CMLMT Constrained Optimization datasets dates dlibrary dllcall econometrics error error codes error handling errors Excel file i/o floating network GAUSS Engine GAUSS Light graphics GUI hotkeys installation Java API license licensing linux loading data loops matrices matrix manipulation Maxlik MaxLikMT multidimensional array optimization Optmum output panel data PQG graphics procs random numbers strings structures threading writing data
Time Series 2.0 MT
Find out more now
Time Series MT 2.1
Find out more now
Find out more now
Error opening dynamic library
I tried to ran a gauss program that previously worked perfectly well in the earlier version of Gauss. But in the v.12 of Gauss, it stopped working and showed this error sign:
"/media/Data/Research/shak/SIMU/qrsimu_20121124.gau(82) : error G0432 : '/media/Data/Research/shak/SIMU/boladth.so' : Error opening dynamic library
Program execute failed"
Would you please advice?
The most common cause of this is having a 32-bit version of GAUSS and a 64-bit version of the dynamic library (.dll, .so, or .dylib) or the other way around. To find out the bit size of boladth.so on Linux, you can use the file command. From a Linux command prompt, change to the directory in which the shared library is located and enter:
This will return some information about the file including the bit size of the shared library. To find the bit-size of GAUSS 12 on your machine, from the GAUSS command-line enter:
This will return either a 32 or a 64 which indicates the bit size of GAUSS.
If the bit sizes do not match, then that is the cause of your problem. If they do match, post the output you received from the commands above in this thread on the forum and we can look further.
Thanks apteh80! Following your instruction I find the boladth.so is a 32 bit code, while the Gauss program is a 64 bid in my 64 machine. I'm happy that at least I find the source of the problem. Thanks again for your advice.
Would you please also tell me the way to change the boladth.so to 64 bit? I have boladth.dll.
I tried to read the User Guide on this but it's difficult to understand. Please advice.
To create a 64-bit shared library (.dll, .so, or .dylib), you need to recompile the library. Do you have the source code for the library? This would be one or more files that ends with .c, .cpp, .cxx, .h, .f, .f90?
If you have the source code it is no big deal to recompile on Linux. I would be happy to advise you on that.
I don't have the source code. Is it possible to recover the source code using .dll or .so?
Unfortunately, it is not possible to recover the source code from a shared library. It is also not possible to make a 32-bit shared library into a 64-bit shared library. This is not a limitation of GAUSS, but a general principle.
If locating the source code is not possible, your best bet is probably going to be installing a 32-bit version of GAUSS. However, if you have any information about where this .so file came from, you might be able to recover the source code from the original author.
It might also be helpful to look at what the shared library is doing. Is it possibly performing a function that was not in older versions of GAUSS, but is in the current version?