erro: /lib64/libc.so.6: version `GLIBC_2.34' not found

[automacaosamos]

Eu tenho um problema com uma aplicacao compilada em Lazarus 2.2.4 para rodar no AlmaLinux 8.6

que usa glibc 2.28.

Estou recebendo o erro: "/lib64/libc.so.6: versão `GLIBC_2.34' não encontrada (exigida por ./aplicacao)".

Como posso atualizar o GLIBC para a versão 2.34 no AlmaLinux 8.6 ? Não encontrei nada que funcione na NET.

Quando usava a versão do lazarus 2.0.12 o problema não ocorria.

alguem pode ajudar que resolveu esse problema ??


Obrigado

[zeljko]

https://forum.lazarus.freepascal.org/index.php/topic,58888.msg460742.html#msg460742,
I think it's fixed in fixes_3_2, so you should try with fixes_3_2 or trunk fpc

[automacaosamos]

I applied all the fixes still the problems persists.
root@localhost ~]# cd /home/samosadmin/apisamos
[root@localhost apisamos]# ./apisamos
./apisamos: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by ./apisamos)
[root@localhost apisamos]#

[zeljko]

You built your app with fixes_3_2 compiler and have same problem ? That's strange.

[automacaosamos]

I also think, I'm going to try to update the GLIBC on my server to 2.34, I'm looking for how to do it, but thanks for your attention in answering.

[dbannon]

https://forum.lazarus.freepascal.org/index.php/topic,58888.msg460742.html#msg460742,
I think it's fixed in fixes_3_2, so you should try with fixes_3_2 or trunk fpc

zeljko, I am extremely interested in why you think it is fixed in trunk, the forum discussion you point lead me to believe it was not something fixable within FPC. Be fantastic if it could be.

I searched FPC commits messages for  "`GLIBC_2.34' not found" but did not find it, can you confirm you think the issue of Apps compiled in a glibc_2.34 system won't run in a system with an earlier glibc are fixed in FPC trunk and even fixes ?

Davo

[zeljko]

Isn't this merge related to glibc problem ? https://gitlab.com/freepascal.org/fpc/source/-/commit/05480071e200e0454d6288c756490c493d695067

[PascalDragon]

I searched FPC commits messages for  "`GLIBC_2.34' not found" but did not find it, can you confirm you think the issue of Apps compiled in a glibc_2.34 system won't run in a system with an earlier glibc are fixed in FPC trunk and even fixes ?

Searching for GLIBC_2.34 in the issues will show you this fixed bug.

[PascalDragon]

Eu tenho um problema com uma aplicacao compilada em Lazarus 2.2.4 para rodar no AlmaLinux 8.6

que usa glibc 2.28.

Estou recebendo o erro: "/lib64/libc.so.6: versão `GLIBC_2.34' não encontrada (exigida por ./aplicacao)".

Como posso atualizar o GLIBC para a versão 2.34 no AlmaLinux 8.6 ? Não encontrei nada que funcione na NET.

Quando usava a versão do lazarus 2.0.12 o problema não ocorria.

alguem pode ajudar que resolveu esse problema ??

If you want to support a system with an older C library you need to compile your application at least with that version of the C library or older. This is by design and how it works in the C world as well.

[dbannon]

I searched FPC commits messages for  "`GLIBC_2.34' not found" but did not find it, can you confirm you think the issue of Apps compiled in a glibc_2.34 system won't run in a system with an earlier glibc are fixed in FPC trunk and even fixes ?

Searching for GLIBC_2.34 in the issues will show you this fixed bug.

Isn't this merge related to glibc problem ? https://gitlab.com/freepascal.org/fpc/source/-/commit/05480071e200e0454d6288c756490c493d695067

That is not related to the problem that the original poster mentions. The OP is worried that his binaries, compiled on a glibc_2.34 system will not run on an older system. Its similar to 39295, similar symptoms and similar mechanism but its fixable (and fixed). The OP's problem is not fixable. Sadly.

> alguem pode ajudar que resolveu esse problema ??

As PD says, you must keep a pre glibc_2.34 system around so you can build on that, the binaries will always (?) run on a future system but the reverse is not (and never was apparently) guaranteed. I do my final release building on a VM dedicated for just that purpose, its an Ubuntu 20.04 but any distro with an earlier glibc_2.34 will do. We'll need to do that as long as there are still supported pre glibc_2.34 around.

And, as Pascal Dragon has said elsewhere, no reason to believe something like this will happen in future releases of glibc_2.34 ! And it is NOT just a FPC issue.

Davo

[automacaosamos]

For testing I created an Almalinux 9.1 environment and the application ran normally, but when I went to access Zeos it refused with the following message: None of the dynamic libraries can be found or is not loadable: libcrypt.so.25, libcrypt.so, libcrypt.so !
Use TZConnection.LibraryLocation if the location is invalid

[Bogen85]

For testing I created an Almalinux 9.1 environment and the application ran normally, but when I went to access Zeos it refused with the following message: None of the dynamic libraries can be found or is not loadable: libcrypt.so.25, libcrypt.so, libcrypt.so !
Use TZConnection.LibraryLocation if the location is invalid

I'm also on AlmaLinux 9.1 and it is up to date.

Code: Pascal  [Select][+][-]

1. $ rpm -ql libxcrypt-4.4.18 | fgrep .so
2. /usr/lib64/fipscheck/libcrypt.so.2.0.0.hmac
3. /usr/lib64/fipscheck/libcrypt.so.2.hmac
4. /usr/lib64/libcrypt.so.2
5. /usr/lib64/libcrypt.so.2.0.0
6.  
7. $ rpm -qf /usr/lib64/libcrypt.so
8. libxcrypt-devel-4.4.18-3.el9.x86_64

What version of libxcrypt and libxcrypt-devel do you have installed?

[anderbelluno]

Tive o mesmo problema com o Cross do Windows para o Ubuntu.
Acontece que vc tem uma lib mais nova no Windows, o que causa esse problemas, é a libc6.
Como resolvi, instalei uma versão mais nova do Ubuntu, mas tem outra solução que ainda não testei, que seria vc apagar as libs do windows e baixar uma versão mais velha.

https://forum.lazarus.freepascal.org/index.php/topic,34645.2175.html

Nessa página vai entrar a solução.
Só seguir os passos.