RE: setting interpreter in EPICS

[Mark Rivers <rivers@cars.uchicago.edu>]

Hi Ana,

 

I will be interested to see if you can make this work.

 

This is a common problem on Linux: the vendor provides a library that is built with a more recent version of Linux, so it needs a more recent version of glibc than the one that is installed on some of the systems we want to use.  I am fighting this with the Point Grey SDK for their cameras at the present time.

 

Some vendors (like AVT for their cameras) provide multiple versions of the Linux libraries built with different versions of gcc.  This is very helpful.  I tried to encourage Point Grey to do this, but so far no luck.

 

Note that some things really DO require a more recent Linux version.  Point Grey USB-3.0 cameras, for example, require new kernel versions that have good USB-3.0 support.

 

Mark

 

 

From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of Ana Malagon
Sent: Monday, January 26, 2015 1:16 PM
To: tech-talk@aps.anl.gov
Subject: setting interpreter in EPICS

 

Hi,

 

I'm using an external library in EPICs application; this library requires a newer compiler version than I have on my system (needs glibc 2.15 to run but my Debian system has 2.13). Long story short, I have installed the newer compiler in a separate folder, but now need to figure out how to invoke this compiler when building the IOC. 

 

I've been following the instructions here to update my compiler and they suggest using a program called patchelf to set the interpreter correctly for programs. I'm not sure how this would translate to EPICS, as there is no executable - does anyone have experience using different versions of glibc with EPICS and know what I should do in this case?

 

Thanks very much,

Ana