Labview 8 installation on Ubuntu, libdb.so.2

[omvargas]

I had that same problem trying to install Labview 7.1 on Ubuntu 6.06 (Dapper). I solved it  by installing the package "libdb1-compat".

type the following command on the terminal:

  sudo apt-get install libdb1-compat

or run Synaptic and search it there.

Note: libdb1-compat is not an official Ubuntu packet, so you must have Universe / Multiverse repositories enabled. Refer to the Ubuntu documentation to learn how to do that.

[rseal]

There is a simple fix for your problems:   copy /usr/bin/rpmquery to /tmp/..../bin/rpmq and all of the other rpm binaries.

This will install the system flawlessly. The problem then becomes libOSMesa.so.4 is not found. Someone here claimed they made  a link and it works, but I am running the 64-bit version and it does not work. This library is two years old and is sure to move into the obsolete pile as X11 moves forward into the 7.x series. If anyone has any other suggestions - I am all ears.

--rseal

[fowie]

I'm using Ubuntu edgy (6.10) and got labview installed and working.  When running the installer (make sure you get rpm through package manager first) it would fail with most of the packages saying it failed the dependecy of /bin/sh which I have.  The work around was to rpm -ivh each rpm by hand instead of using the installer.  If the rpm fails with the only dependency failure being /bin/sh, just add --nodeps to the end of the rpm command

rpm -ivh labview82-package-name.rpm --nodeps

and the package will install.  Be careful about making sure to satisfy the other dependencies, it's not normally recommended to use --nodeps.

Fowie

[iyhernandezo]

Hi,

I was seeing the thread, and I had a big surprise when my installation just worked whitout problems. I'm using ubuntu 6.10

$uname -a
Linux yesidh-laptop 2.6.17-12-generic #2 SMP Mon Jul 16 19:37:58 UTC 2007 i686 GNU/Linux

I installed rpm, from synaptic, then copy the entire cd contents to /media/labview and then run INSTALL by using:
$sudo ./INSTALL

Then the installation went perfect, just some warnings about a deprecated command:
sort: Warning: "+number" syntax is deprecated, please use "-k number"

Finally i ran:
/usr/local/natinst/LabVIEW-8.2/labview

And the program ran, I don't know if I will have that crashed in the future but the installation was good. I will let you all now.

Bye

[D. F. Kutz]

Most of the problems show up while trying to install Labview 7.x. On LV 8 the Support is better...
Anyway: there is a good tutorial installing Labview 7 Express on a Ubuntu (6 i think) Machine here : http://blog.360.yahoo.com/blog-CiyfVJ03dLTZhklNXsjpjIBV?tag=labview
I used the tutorial the first time i installed LV7.

Now i get stuck with the libOSMesa.so.4 error while trying to run DAQmxTestPanel which belongs to niDAQmx8.0; but LV7Express worsk fine...

If anyone has a good idea how to solve the libOSMesa.so.4 problem, please reply.



Eruphus

[dmontalvao]

Eruphus, that actually seems to be a good tutorial. However, with LabView71 and Ubuntu 7.04 it didn't work (at least with me).

Also, the tutorial from Forrest is with Ubuntu 7.04 and not 6 as you supposed. Anyway, thank you for the advice! I am already trying to contact him, because I have the same problem.

The most frustrating thing, is that labview seems to run, but after some seconds (15 to 30) it just closes. A message appears on the bottom: "Version 7.1 - Init tmp resource files", and it doesn't change. With Labview80 nothing happens at all with me.

I am looking forward to hearing from you!

Best regards,
Diogo Montalvão
(Lisbon, Portugal)

[Eruphus]

First i had similar problems using LV on a Debian 4 System.
After i tried to start LV the splash-screen appeared for a very short period of time.
Nothing further happened for 15-30 secs. After this i got an error message on the shell.
For some reason, the libc is incompatible to the LV code.

  -> Try to run LV from the console and wait for any error message to appear.

This was the point where i startet to change my Linux distri.

After several Version Test i finally got LV7 to start on a Ubuntu 6.06 LTS (Dapper Drake) Version; Kernel 2.6.15-26-386.
I've downloaded the ISO directly from http://www.ubuntu.com/getubuntu/download

This Linux-version has the glibc-version 2.3.6 compild by gcc 3.4.6.


Don't know how far you have to go, but i had to install the drivers for VXI/PXI support on this Linux Machine.
Therefor i had to download the current linux code. I suggest trying another Version, since Ubuntu and other diststributions
have a subversion suffix inside the Kernel Code  (i.e. Kernel Version 2.6.15 is displayed as 2.6.15-ubuntu1 here)
wich differs from the Version-Code inside the downloaded source. I DONT KNOW WHY, but I can only speculate that
the source code, downloaded by rpm, does not belong to Ubuntu since Ubuntu has not a RPM based package system.

Unfortunately, the install script for VISA drivers checks the installed kernel version against the used kernel source for
driver compilation and fails on the subversion suffix comparison.

If you have to do this step, i can tell you how to run PXI/VXI Modules on Ubuntu 6.06 LTS.
Pleas contact me for further information.



Today i received a message telling me that i will receive a brand new version of LV8.5 from my License Manager.
Therefor i look forward to a better Linux support


regards, Alexander

p.s. I hope any reader can follow my poor english language

[Shawn B.]

---

@Eruphus wrote:
Now i get stuck with the libOSMesa.so.4 error while trying to run DAQmxTestPanel which belongs to niDAQmx8.0; but LV7Express worsk fine...

If anyone has a good idea how to solve the libOSMesa.so.4 problem, please reply.

---

Well, I don't have a Linux machine with LabVIEW 7 around so I'm working from memory, but you should be able to create a symbolic link to LabVIEW's libOSMesa.so.4 under /usr/local/lib/linux/.  Here is what I would do as root:

find /usr/local/ -iname "*mesa*"
# Hopefully this will return libOSMesa.so.4 (This may be called libLVMesa.so.4, or something similar)
mkdir -p /usr/local/lib/linux/
cd /usr/local/lib/linux/
ln -s /path/to/libMesa/returned/from/find libOSMesa.so.4

Hope that helps.

Shawn B.
National Instruments

[dmontalvao]

On Ubuntu 7.04 this is what I got:

root@DMS-Ubuntu:/home/dmontalvao# find /usr/local/ -iname "*mesa*"
/usr/local/lv71/linux/README.Mesa
/usr/local/lv71/linux/libLVMesaGL.so.3
/usr/local/lib/LabVIEW-7.0/libLVMesaGL.so.3
/usr/local/lib/libLVMesaGL.so.3
/usr/local/lib/LabVIEW-7.1/libLVMesaGL.so.3

So... Where can I download libOSMesa.so.4? In Synaptic I can see Mesa6 is installed!

I am almost installing Ubuntu 6.06, and copying the file libOSMesa.so.4! As far as I can recall, I had LV71 working there (or was it 6.10?). So frustrating!

Message Edited by dmontalvao on 09-11-2007 08:42 AM

[Shawn B.]

---

@dmontalvao wrote:
On Ubuntu 7.04 this is what I got:

/usr/local/lib/LabVIEW-7.0/libLVMesaGL.so.3
/usr/local/lib/libLVMesaGL.so.3
/usr/local/lib/LabVIEW-7.1/libLVMesaGL.so.3

---

Did you put these files here, or was that the LabVIEW installer?  If LabVIEW did it then my memory must be fuzzier than I thought

---

So... Where can I download libOSMesa.so.4? In Synaptic I can see Mesa6 is installed!

---

As confusing as it may sound libLVMesaGL.so.3 that you found is libOSMesa.so.4.  I'm not a LabVIEW developer, but I believe what happened was that we used to rename libOSMesa.so.3 to libLVMesaGL.so.3 so that it wouldn't conflict with your systems libOSMesa.so.3.  This may also be why it was put under /usr/local/lib/ where every application could see it.  At some point the version shipping with distributions changed to libOSMesa.so.4 and thus we make LabVIEW look for libOSMesa.so.4 in case your system has a better libOSMesa.so.4 (Perhaps yours has better 3D support).  Of course internally LabVIEW is built and linked against that old libLVMesaGL.so.3 just renamed to libOSMesa.so.4.  Additionally since LabVIEW now looks for libOSMesa.so.4 in addition to the normal library paths we also set the RPATH which shows the additional locations that LabVIEW will look for libOSMesa.so.4.

Here is what I would recommend:
1. Which application is giving an error looking for libOSMesa.so.4?  If it is LabVIEW then we need to go find the LabVIEW binary ("which labview" should show you the path).  If it is a seperate utility like the DAQmx Test Panels then it is likely a LabVIEW built application and thus the LabVIEW Run-time Engine is what is looking for libOSMesa.so.4 and not finding it.  You can find the LabVIEW Run-time Engine (liblvtr.so.*) under /usr/local/lib/.

2. Using either labview or liblvrt.so.* from step one run "objdump -p liblvrt.so.8.0"  For example from my machine you should see something like:

  NEEDED      libOSMesa.so.4
  NEEDED      libGL.so.1
  NEEDED      libX11.so.6
  NEEDED      libXext.so.6
  NEEDED      libm.so.6
  NEEDED      libdl.so.2
  NEEDED      libpthread.so.0
  NEEDED      libc.so.6
  SONAME      liblvrt.so.8.0
  SYMBOLIC    0x0
  RPATH       $ORIGIN:$ORIGIN/linux:$ORIGIN/resource:/usr/X11R6/lib

So in my case liblvrt.so.8.0 (the LabVIEW 8.0 run-time engine) needs a file named libOSMesa.so.4.  In addition to looking in the normal library locations for this file it will first look in the RPATH to see if it can find the library.  $ORIGIN is a relative location of liblvrt.so.8.0 (or whatever file you happen to be looking at), so if I have /usr/local/lib/liblvrt.so.8.0 it will first look in /usr/local/lib:/usr/local/lib/linux:/usr/local/lib/resource:/usr/X11R6/lib in that order.

3.  Using your knowledge from step 2 you can create a symbolic link, copy/rename or whatever you want to put libLVMesaGL.so.3 into the proper location and with the proper name.  I would recommend putting it in $ORIGIN/linux so that it is unlikely to collide with your systems Mesa libraries.

Hope that helps.  Newer versions of LabVIEW (8+) are much better about handling this by the way.

Shawn B.
National Instruments