Re: Is there a minimum version requirement for glibc and GCC using EPICS

["Johnson, Andrew N. via Tech-talk" <tech-talk at aps.anl.gov>]

Hi,

In a general if you are running different versions of Linux on your systems, you have to compile the software on the oldest OS version that you want to run it on. This isn’t an EPICS restriction, newer GLIBC versions contain compatibility code so that programs compiled against older versions can still run against it, but the reverse can’t be done. Using Maren’s example, building your EPICS code on RHEL-5 should allow the result to also run on RHEL-6 and 7.

HTH,

- Andrew

__ 

Complexity is free, you pay for Simplicity

---

From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Maren Purves via Tech-talk <tech-talk at aps.anl.gov>
Sent: Saturday, December 21, 2024 3:35:02 AM
To: shenzb at ihep.ac.cn <shenzb at ihep.ac.cn>
Cc: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: Re: Is there a minimum version requirement for glibc and GCC using EPICS

 

What is your operating system (in both systems)?

We (running CentOS5, 6, or 7), on different machines, some of which
probably aren't upgradable) have run into (not EPICS related, this is
for Chrome - none of the CentOS5 machines have Chrome, they're older
processing computers) :

Failed to build transaction:
google-chrome-stable-131.0.6778.204-1.x86_64 requires
libc.so.6(GLIBC_2.25)(64bit)

but installing that libc version would break the operating system on
those machines, so before you install a newer version of libc.so to
what it says you need you would have to check whether that would
require an operating system upgrade or possibly break the current one.

HTH, and aloha,
Maren Purves
Head of Instrument and Telescope Software
East Asian Observatory / JCMT


On Fri, Dec 20, 2024 at 4:59 PM Zhibang Shen via Tech-talk
<tech-talk at aps.anl.gov> wrote:
>
> Hi,
>
>
> I have developed a modbus protocol based motor submodule in my own environment. It is successfully compiled and running without any issue in my development setup.
>
>
> However, while migrating the module to the production environment, we encounter an error of low version library.
>
>
>
> [hp@localhost iocLeadshine]$ ./st.cmd
>
> ../../bin/linux-x86_64/leadshine: /usr/lib64/libc.so.6: version `GLIBC_2.34' not found (required by ../../bin/linux-x86_64/leadshine)
>
>
>
> The libc.so.6 can be found at directory /usr/lib64. It seems to be an issue that the glibc version is too low.
>
>
>
> [hp@localhost iocLeadshine]$ strings /usr/lib64/libc.so.6 | grep GLIBC_
>
> GLIBC_2.0
>
> GLIBC_2.1
>
> GLIBC_2.1.1
>
> GLIBC_2.1.2
>
> GLIBC_2.1.3
>
> GLIBC_2.2
>
> GLIBC_2.2.1
>
> GLIBC_2.2.2
>
> GLIBC_2.2.3
>
> GLIBC_2.2.4
>
> GLIBC_2.2.6
>
> GLIBC_2.3
>
> GLIBC_2.3.2
>
> GLIBC_2.3.3
>
> GLIBC_2.3.4
>
> GLIBC_2.4
>
> GLIBC_2.5
>
> GLIBC_2.6
>
> GLIBC_2.7
>
> GLIBC_2.8
>
> GLIBC_2.9
>
> GLIBC_2.10
>
> GLIBC_2.11
>
> GLIBC_2.12
>
> GLIBC_2.13
>
> GLIBC_2.14
>
> GLIBC_2.15
>
> GLIBC_2.16
>
> GLIBC_2.17
>
> GLIBC_PRIVATE
>
>
>
> Is there a minimum version requirement for glibc when using the synApps/motor package?
>
>
> We tried to compile the glibc from the source. But it is prompted that the gcc version is also not appropriate.
>
>
> As a reference, here are the version of the packages in the production environment.
>
>
> EPICS base 3.15.9
>
> asyn R4-41
>
> seq 2-2-5
>
> busy R1-7
>
> modbus R3-2
>
> motor R7-1
>
>
>
> Best regards,
>
> Zhibang