01-16-2013 06:45 AM
01-16-2013 06:59 AM
01-16-2013 08:17 AM
Uh, nothing is attached...
Mike...
01-16-2013 11:25 PM
01-17-2013 12:09 AM
01-17-2013 05:00 AM
01-18-2013 09:46 AM
Hello, Which Linux distribution exactly are you using?
Regards
01-20-2013 12:01 AM
I'm using Centos 5.5
01-21-2013 02:39 AM - edited 01-21-2013 02:40 AM
Have you contacted the creator of that library? He is a competent programmer and should be able to find out quickly if it is a LabVIEW version problem or something with your Linux distribution. I'm pretty sure he tested it with LabVIEW 2011 too, so changes are that it is something with CentOS that screws up.
And if I had a guess, I would point at some C runtime library versioning issues. Using shared libraries in LabVIEW can be a little tricky as LabVIEW has its own linkage to the C runtime library and the shared library can define a strict C runtime version dependency too. If they both end up using different versions, you can end up in a bit of a mess if you happen to pass C runtime objects (allocated memory buffers, file objects, etc.) between the different runtime libraries.
It could be as easy as upgrading your runtime libraries or as complicated as upgrading/recompiling your kernel with a different GCC compiler toolchain version.
01-21-2013 04:38 AM
I created the library, after it failed to work with the library distributed with the sqlite Api package.<br />
On same Centos computer I have both LV2009 and LV2011.<br />
I tested the libraries on each LV version both libraryies worked with LV2009 and faild on LV2011.