LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW 8.0.1 RTE Red Hat Linux

Solved!
Go to solution
Highlighted

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

0 Kudos
Message 11 of 22
(2,652 Views)

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

JKI Blog
0 Kudos
Message 12 of 22
(2,651 Views)

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

JKI Blog
0 Kudos
Message 13 of 22
(2,648 Views)

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

0 Kudos
Message 14 of 22
(2,642 Views)
Hello,

Thanks everyone for all the help.

To answer the questions, setting the vipm to executable and running from the console yields

[physrin@physring05 vipm]$ ./vipm-1.0-linux
Can't load LabVIEW runtime library /usr/local/lib/liblvrt.so.8.0
libOSMesa.so.4: cannot open shared object file: No such file or directory

And using ldd yields

[physrin@physring05 vipm]$ ldd vipm-1.0-linux
linux-gate.so.1 => (0x0011a000)
libdl.so.2 => /lib/libdl.so.2 (0x00860000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00866000)
libc.so.6 => /lib/libc.so.6 (0x006f2000)
/lib/ld-linux.so.2 (0x006cf000)

Running ldd on the library which will not load yields:

ldd /usr/local/lib/liblvrt.so.8.0
ldd: warning: you do not have execution permission for `/usr/local/lib/liblvrt.so.8.0'
linux-gate.so.1 => (0x00193000)
libOSMesa.so.4 => not found
libGL.so.1 => /usr/lib/libGL.so.1 (0x00548000)
libX11.so.6 => /usr/lib/libX11.so.6 (0x00194000)
libXext.so.6 => /usr/lib/libXext.so.6 (0x00110000)
libm.so.6 => /lib/libm.so.6 (0x00120000)
libdl.so.2 => /lib/libdl.so.2 (0x00346000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00147000)
libc.so.6 => /lib/libc.so.6 (0x0034a000)
libXxf86vm.so.1 => /usr/lib/libXxf86vm.so.1 (0x0015e000)
libdrm.so.2 => /usr/lib/libdrm.so.2 (0x00163000)
libXau.so.6 => /usr/lib/libXau.so.6 (0x002b5000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x0016b000)
/lib/ld-linux.so.2 (0x006cf000)

I seem to only have the required file in the directory for the Labview 8.20 runtime.

[physrin@physring05 vipm]$ locate libOSMesa.so.4
/usr/local/lib/LabVIEW-8.2/linux/libOSMesa.so.4
/usr/local/lib/LabVIEW-8.2/linux/libOSMesa.so.4.0

Some other packages I have installed which may be relevant:

[physrin@physring05 LabVIEW-8.0]$ yum list installed | grep mesa
mesa-libGL.i386 6.5.1-7.5.el5 installed
mesa-libGL-devel.i386 6.5.1-7.5.el5 installed
mesa-libGLU.i386 6.5.1-7.5.el5 installed
mesa-libGLU-devel.i386 6.5.1-7.5.el5 installed
mesa-libOSMesa.i386 6.5.1-7.5.el5 installed

As to the configuration of my system it is centos 5, with labview 8.5 installed plus labview 8.0 and 8.20 RTE's. This should tell you all you need to know:

[physrin@physring05 LabVIEW-8.0]$ yum list installed | grep labview

labview-rte-aal.i386 1.1-1 installed
labview80-rte.i386 8.0.1-1 installed
labview82-rte.i386 8.2.1-2 installed
labview85-core.i386 8.5.1-1 installed
labview85-desktop.i386 8.5.1-1 installed
labview85-examples.i386 8.5.1-1 installed
labview85-help.i386 8.5.1-1 installed
labview85-ref.i386 8.5.1-1 installed
labview85-rte.i386 8.5.1-1 installed
labview85-vxi.i386 8.5.1-1 installed
nidaqmxbase-labview85-VIs.i386 3.2.0-f1 installed
niexfinder-labview85.i386 1.0-9 installed

[physrin@physring05 LabVIEW-8.0]$ yum list installed | grep ^ni

nicvirte.i386 8.0-7 installed
nidaqmxbase-board-support.i386 3.2.0-f1 installed
nidaqmxbase-cinterface.i386 3.2.0-f1 installed
nidaqmxbase-common.i386 3.2.0-f1 installed
nidaqmxbase-labview85-VIs.i386 3.2.0-f1 installed
nidaqmxbase-usb-support.i386 3.2.0-f1 installed
nidimi.i386 1.9.0-f0 installed
niexfinder-base.i386 1.0-9 installed
niexfinder-labview85.i386 1.0-9 installed
nikali.noarch 1.8.0-f0 installed
niorbi.i386 1.9.0-f0 installed
nipali.i386 2.3.0-f1 installed
nipalki.i386 2.3.0-f1 installed
nipxirmi.i386 1.6.0-f0 installed
nirpci.i386 4.0.0-f1 installed
nispyi.i386 2.6.0-f0 installed
nivisa.i386 4.4.0-f0 installed
nivisa-config.i386 4.4.0-f0 installed
nivisa-devel.i386 4.4.0-f0 installed
nivisak.i386 4.4.0-f0 installed
nivisaserver.i386 4.4.0-f0 installed
niwebpipeline20_dep.i586 2.0-5 installed

[physrin@physring05 LabVIEW-8.0]$ cat /proc/version
Linux version 2.6.18-92.1.13.el5 (mockbuild@builder16.centos.org) (gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)) #1 SMP Wed Sep 24 19:33:52 EDT 2008
0 Kudos
Message 15 of 22
(2,610 Views)

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

0 Kudos
Message 16 of 22
(2,606 Views)

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 ?

0 Kudos
Message 17 of 22
(2,596 Views)

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 

0 Kudos
Message 18 of 22
(2,564 Views)

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!

0 Kudos
Message 19 of 22
(2,559 Views)
Solution
Accepted by rdg

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

0 Kudos
Message 20 of 22
(2,539 Views)