11-17-2008 11:11 AM
Richard,
If you run ldd on the 8.0.1 executable, what are the results? Is it linked to liblvrt.so or liblvrt.so.8.0.1? Also, the issue with the VIPM extension would be handled by the MIME type dictionary on your machine. If you look up what is supposed to run when an item is run (double-clicked) with the VIPM extension, what does it say? You may need to look into the/usr/shard/mime/packages directory.
Randy Hoskin
LabVIEW R&D
11-17-2008 11:13 AM
Hi Claire,
> Just to update you. I downloaded and installed the VIPM...and everything seems to be working. (I think)
What is your system configuration, with respect to installed LabVIEW run-time engines and development environments?
For example, do you have the LabVIEW 8.5 development environment installed?
> Are you still having problems? Could you describe in more detail the steps to reproduce this problem.
Based on this post from Richard, yesterday, he seems to still be having issues.
Thanks,
-Jim
11-17-2008 11:18 AM
Randy H wrote:Richard,
If you run ldd on the 8.0.1 executable, what are the results? Is it linked to liblvrt.so or liblvrt.so.8.0.1? Also, the issue with the VIPM extension would be handled by the MIME type dictionary on your machine. If you look up what is supposed to run when an item is run (double-clicked) with the VIPM extension, what does it say? You may need to look into the/usr/shard/mime/packages directory.
Randy Hoskin
LabVIEW R&D
Hi Randy,
I'll let Richard report back on the ldd (shared object linkage) results.
FYI, the VIPM installer for linux is named vipm-1.0-linux and does not have a typical file extension (although it could be interpreted to have a "0-linux" file extension).
Thanks,
-Jim
11-17-2008 11:29 AM
Also, what happens if you try to run the executable from the command line instead of from the desktop interface?
Randy Hoskin
LabVIEW R&D
11-17-2008 03:24 PM
11-17-2008 03:55 PM
Richard,
OK. This is a know issue that we ran into in later distributions of Linux, but after we had already shipped LabVIEW 8.0. If you search the support for OSMesa, you get this post. There may be others as well. My suggestion is to copy the libOSMesa files from LabVIEW 8.2 and move them into the LabVIEW 8.0 directory (keeping the linux subdirectory). This should resolve your issue. If not, then you can also try placing them in /usr/local/lib, keeping the linux subdirectory here as well.
Randy Hoskin
LabVIEW R&D
11-17-2008 04:49 PM
Hi,
I have tried copying the /usr/local/lib/LabVIEW-8.2/linux directory into labview 8.01 and just into /usr/local/lib -- only the latter had any effect. Now when I try to run the program I get:
[physrin@physring05 vipm]$ ./vipm-1.0-linux
Can't load LabVIEW runtime library /usr/local/lib/liblvrt.so.8.0
/usr/local/lib/linux/libOSMesa.so.4: undefined symbol: _glapi_add_entrypoint
So it seems to me the library is being found now, but the version I have is not exactly right. Any idea where I can get exactly the right version of libOSMessa.so.4 ?
11-18-2008 03:30 PM
Richard,
Here is what I needed to do to get it working:
1) Delete all /usr/local/lib/linus/libOSMesa.so.4*
2) Copy the libLVMesa.so.4 from this post and place it in /usr/local/lib/linux
3) Run "ln -s libLVMesa.so.4 libOSMesa.so.4" as root from the /usr/local/lib/linux directory
4) Run "/usr/bin/chcon -f -t textrel_shlib_t /usr/local/lib/linux/libOSMesa.so.4" as root
5) Run vipm-1.0-linux
I got an error when running the executable about a VI not being executable. If that happens to you, I would direct that question to Jim Kring.
Randy Hoskin
LabVIEW R&D
11-18-2008 04:00 PM
Hi,
I followed your instructions, this time getting
[physrin@physring05 vipm]$ ./vipm-1.0-linux
Can't load LabVIEW runtime library /usr/local/lib/liblvrt.so.8.0
/usr/local/lib/liblvrt.so.8.0: cannot restore segment prot after reloc: Permission denied
And the same when trying to run as root. I feel I am getting closer .. I guess I need to fix the permissions of something, not sure what though. This is the contents of my /usr/local/lib/linux now:
drwxr-xr-x 2 root root 4096 Nov 19 10:45 .
drwxr-xr-x 6 root root 4096 Nov 18 11:40 ..
-rwxrwxrwx 1 root root 980616 Nov 19 10:44 libLVMesa.so.4
lrwxrwxrwx 1 root root 14 Nov 19 10:45 libOSMesa.so.4 -> libLVMesa.so.4
lrwxrwxrwx 1 root root 18 Nov 18 11:40 libstdc++.so.5 -> libstdc++.so.5.0.3
-rw-r--r-- 1 root root 720784 Nov 19 09:49 libstdc++.so.5.0.3
-rw-r--r-- 1 root root 1291 Nov 19 09:49 README.libs
perhaps also relevant:
[physrin@physring05 vipm]$ ld /usr/local/lib/liblvrt.so.8.0
ld: warning: libOSMesa.so.4, needed by /usr/local/lib/liblvrt.so.8.0, not found (try using -rpath or -rpath-link)
ld: warning: cannot find entry symbol _start; not setting start address
/usr/local/lib/liblvrt.so.8.0: undefined reference to `OSMesaDestroyContext'
/usr/local/lib/liblvrt.so.8.0: undefined reference to `OSMesaCreateContext'
/usr/local/lib/liblvrt.so.8.0: undefined reference to `OSMesaGetCurrentContext'
/usr/local/lib/liblvrt.so.8.0: undefined reference to `OSMesaPixelStore'
/usr/local/lib/liblvrt.so.8.0: undefined reference to `OSMesaMakeCurrent'
Thanks for all the help!
11-19-2008 09:52 AM
Richard,
I must have forgotten a step. Try running ""/usr/bin/chcon -f -t textrel_shlib_t /usr/local/lib/LabVIEW-8.0/liblvrt.so.8.0.1" as root as well. That should allow everything to run.
Randy Hoskin
LabVIEW R&D