Jump to content
Richard

cant install vipm on labview 8.5 linux

Recommended Posts

Hi,

 

I am having a problem installing VIPM 1.0 on my labview 8.5 installation on linux (centos / red hat 5). I have the labview 8.0.1 runtime installed.

When I open vipm-1.0-linux, it open up labview 8.5 LLB manager. I am unable to run setup.vi or anything inside of there.

 

--

Richard

Edited by Richard

Share this post


Link to post
Share on other sites

Hi Richard,

 

I haven't seen this problem. It sounds like an issue with the OS and the 8.0.1 run-time and 8.5 development environment installations. I don't have a test system with your configuration, so it will be hard for me to try to reproduce your issue. First, a few background questions:

 

Did you install the 8.0.1 run-time engine before or after installing 8.5?

 

Have you tried re-installing the run-time engine?

 

Does it do this if you exit LabVIEW (so that LabVIEW 8.5 is not running) while you try to run vipm-1.0-linux?

 

I hate to ask this, but have you tried contacting NI technical support? They might have seen this problem and know of a simple solution.

 

Thanks,

 

-Jim

Share this post


Link to post
Share on other sites

Hi,

 

Sorry for the late reply. Yes I think it is an issue with the 8.0.1 run time. I installed the packages for it after installing labview (though that should not make any difference), and I have tried reinstalling them. Basically when I just click on the vipm-1.0-linux installer it will open up with labview 8.5 llb manager .. I need to open it with the labview 8.0.1 RTE. The only executable in this package is named lvdark and installs to usr/local/lib/LabVIEW-8.0/ I presume this is what I need to use, though I can't run it directly, I get the error

/usr/local/lib/liblvrtdark.so.8.0: cannot restore segment prot after reloc: Permission denied

even when running as root.

 

I guess I will try the NI forums. Kind of annoying, I am pretty keen to try the easy xml tools.

 

-- Richard

Share this post


Link to post
Share on other sites
Hi,

 

Sorry for the late reply. Yes I think it is an issue with the 8.0.1 run time. I installed the packages for it after installing labview (though that should not make any difference), and I have tried reinstalling them. Basically when I just click on the vipm-1.0-linux installer it will open up with labview 8.5 llb manager .. I need to open it with the labview 8.0.1 RTE. The only executable in this package is named lvdark and installs to usr/local/lib/LabVIEW-8.0/ I presume this is what I need to use, though I can't run it directly, I get the error

/usr/local/lib/liblvrtdark.so.8.0: cannot restore segment prot after reloc: Permission denied

even when running as root.

 

I guess I will try the NI forums. Kind of annoying, I am pretty keen to try the easy xml tools.

 

-- Richard

 

Hi Richard,

 

I've subscribed to the thread that you started on the NI forums and will keep my eye on it.

 

Thanks,

 

-Jim

Share this post


Link to post
Share on other sites

Hi,

 

I haven't had any luck on the NI forums so far, I was wondering if it is possible to install OpenG tools without the vipm? (The dictionary tools would be extremely useful for me right now..). I figure since these tools are open source it must be possible to install them separately, but I don't see how. Also I was wondering if there are any plans for an updated vipm for linux any time soon?

 

--

Richard

Share this post


Link to post
Share on other sites
Hi,

 

I haven't had any luck on the NI forums so far, I was wondering if it is possible to install OpenG tools without the vipm? (The dictionary tools would be extremely useful for me right now..). I figure since these tools are open source it must be possible to install them separately, but I don't see how. Also I was wondering if there are any plans for an updated vipm for linux any time soon?

 

--

Richard

 

Hi Richard,

 

> I haven't had any luck on the NI forums so far

 

I've sent a message to some "higher-ups" at NI to see if they can escalate the issue. We'll see if that helps.

 

> I was wondering if it is possible to install OpenG tools without the vipm? (The dictionary tools would be extremely useful for me right now..). I figure since these tools are open source it must be possible to install them separately, but I don't see how.

 

Yes, it's possible, but it's neither easy nor recommended...

 

You can download the individual OpenG package files from SourceForge here. They are zip formatted archives and you should be able to extract the VIs.

 

> Also I was wondering if there are any plans for an updated vipm for linux any time soon?

 

Yes, we're actively working on this and hope to have something available, soon. There are no official announcements, yet, though.

 

Thanks,

 

-Jim

Share this post


Link to post
Share on other sites
> I haven't had any luck on the NI forums so far

 

I've sent a message to some "higher-ups" at NI to see if they can escalate the issue. We'll see if that helps.

 

Richard,

 

Randy Hoskin from the LabVIEW R&D team has responded (here) to your post on the NI forums. He has some troubleshooting steps that he'd like you to take.

 

Thanks,

 

-Jim

Share this post


Link to post
Share on other sites

Hi Jim,

 

Thanks for all the help so far. I now have the labview 8.01 RTE set up and vipm installer executing.

 

The installer starts up and runs to about 70%, then I get an error:

 

LabVIEW: The VI is not executable. VI Path: /tmp/lvzlib.llb/ZLIB Extract All Files To Dir__ogtk__SFE.vi

 

And then the installer quits. Digging down into the VI in the LLB indicated I see the problem. There is a question mark box where the 'Common Path to Specific Path__SFE.vi' should be and labview indicates this VI is simply missing.

 

There are also some other errors .. ZLIB Enumerate File Contents__ogtk is not executable for example, and digging down through the VI's and can find several which are missing and causing the problem:

 

Common Path to Specific Path__SFE.vi

compatOverwrite_SFE.vi

LV70DateRecToU32__SFE.vi

GetDateTimeInSecsCompatVI__SFE.vi

LV70U32ToDateRec__SFE.vi

 

Perhaps you can see something in common these have .. perhaps I need to install another library or something?

btw, I also see some log files in the /tmp directory .. vipm-1.0-linux_8.0.1_physrin_cur.txt and vipm-1.0-linux_8.0.1_physrin_log.txt don't know if they are useful, but anyway contain:

 

####

#Date: Thu, Nov 20, 2008 09:43:18 AM

#OSName: Linux

#OSVers: 2.6.18-92.1.13.el5

#AppName: ./vipm-1.0-linux

#Version: 8.0.1

#AppKind: AppLib

 

Thanks a lot, seems I am almost there.

Share this post


Link to post
Share on other sites
Hi Jim,

 

Thanks for all the help so far. I now have the labview 8.01 RTE set up and vipm installer executing.

 

The installer starts up and runs to about 70%, then I get an error:

 

LabVIEW: The VI is not executable. VI Path: /tmp/lvzlib.llb/ZLIB Extract All Files To Dir__ogtk__SFE.vi

 

And then the installer quits. Digging down into the VI in the LLB indicated I see the problem. There is a question mark box where the 'Common Path to Specific Path__SFE.vi' should be and labview indicates this VI is simply missing.

 

There are also some other errors .. ZLIB Enumerate File Contents__ogtk is not executable for example, and digging down through the VI's and can find several which are missing and causing the problem:

 

Common Path to Specific Path__SFE.vi

compatOverwrite_SFE.vi

LV70DateRecToU32__SFE.vi

GetDateTimeInSecsCompatVI__SFE.vi

LV70U32ToDateRec__SFE.vi

 

Perhaps you can see something in common these have .. perhaps I need to install another library or something?

btw, I also see some log files in the /tmp directory .. vipm-1.0-linux_8.0.1_physrin_cur.txt and vipm-1.0-linux_8.0.1_physrin_log.txt don't know if they are useful, but anyway contain:

 

####

#Date: Thu, Nov 20, 2008 09:43:18 AM

#OSName: Linux

#OSVers: 2.6.18-92.1.13.el5

#AppName: ./vipm-1.0-linux

#Version: 8.0.1

#AppKind: AppLib

 

Thanks a lot, seems I am almost there.

 

Hi Richard,

 

It's good to hear that we're making progress.

 

You can ignore these files as they are created by the LabVIEW run-time engine:

  • vipm-1.0-linux_8.0.1_physrin_cur.txt
  • vipm-1.0-linux_8.0.1_physrin_log.txt

Regarding the missing VIs, I'm not sure if this is the real problem. This installer works fine and there are no missing VIs on other platforms. My guess is that the problem has something to do with the unzipping shared library. Is there also a file located here: /tmp/lvzlib.so ? When you try to open /tmp/lvzlib.llb is it correctly linked to lvzlib.so ?

 

Thanks,

 

-Jim

Share this post


Link to post
Share on other sites
I certainly have the /tmp/lvzlib.so file. I can open /tmp/lvzlib.llb in the labview llb manager ... how can I check what this is linked to?

 

When you open "/tmp/lvzlib.llb/ZLIB Extract All Files To Dir__ogtk__SFE.vi" does the LabVIEW error list say anything about missing lvzlib.so?

Share this post


Link to post
Share on other sites
When you open "/tmp/lvzlib.llb/ZLIB Extract All Files To Dir__ogtk__SFE.vi" does the LabVIEW error list say anything about missing lvzlib.so?

 

No it doesn't, I have browsed through all the vi's in the llb trying to run them, never seeing any error about a missing lvzlib.so. The errors are all of the form vi is not executable, and drilling down they all appear to be due to 'missing' vi's.

Share this post


Link to post
Share on other sites

Hi Richard,

 

Digging down into the VI in the LLB indicated I see the problem. There is a question mark box where the 'Common Path to Specific Path__SFE.vi' should be and labview indicates this VI is simply missing.

 

I think you can ignore this missing VI error. This is a result of you opening the VI in the LabVIEW 8.5.1 development environment. This is not possible, since some of the VIs in that LLB are saved in 8.0.1 without block diagrams. This is intentional and is part of how the installer is built -- it's not meant to be opened in LabVIEW 8.5.1, it's meant to be opened by the VIPM installer that is running in the 8.0.1 RTE.

 

So, the problem remains that the installer executable is unable to open this VI:

 

LabVIEW: The VI is not executable. VI Path: /tmp/lvzlib.llb/ZLIB Extract All Files To Dir__ogtk__SFE.vi

 

Now, is this error coming from the LabVIEW 8.5 development environment or from the installer running in 8.0.1 RTE?

 

The only reason I can think of that this VI would seem to be "not executable" by the installer running in 8.0.1 would be that it's having trouble loading the lvzlib.so file.

 

Thanks,

 

-Jim

Share this post


Link to post
Share on other sites

I follow your reasoning Jim. As far as I can tell it is the installer running in the labview 8.01 RTE which is giving this error, although I could not figure out a way to tell for sure. I can't think how it could be that it is not finding the /tmp/lvzlib.so file, it seems to be there in /tmp when the installer is running. I also tried copying it out and putting it in the same directory as the installer, as well as running as root - same result in all cases.

Share this post


Link to post
Share on other sites
I follow your reasoning Jim. As far as I can tell it is the installer running in the labview 8.01 RTE which is giving this error, although I could not figure out a way to tell for sure. I can't think how it could be that it is not finding the /tmp/lvzlib.so file, it seems to be there in /tmp when the installer is running. I also tried copying it out and putting it in the same directory as the installer, as well as running as root - same result in all cases.

 

Hi Richard,

 

I'll try to get you up and running another way. I'll send you an email, off-line.

 

Thanks,

 

-Jim

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.