编译qt指定glibc_我如何链接到特定的glibc版本？

最新推荐文章于 2023-11-20 18:22:07 发布

叶泊枫

最新推荐文章于 2023-11-20 18:22:07 发布

阅读量1.2k

点赞数

CC 4.0 BY-SA版权

文章标签：编译qt指定glibc

本文链接：https://blog.csdn.net/weixin_31061573/article/details/111985939

当在Ubuntu Lucid 10.04上编译程序时，默认会链接到glibc 2.11。若在glibc版本较旧的系统上运行，程序可能失败。解决方案包括静态链接、在chroot环境中编译或使用跨编译器。根据博客，可以使用.glibc_2.2.5版本的realpath符号来确保链接旧版本。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

When I compile something on my Ubuntu Lucid 10.04 PC it gets linked against glibc. Lucid uses 2.11 of glibc. When I run this binary on another PC with an older glibc, the command fails saying there's no glibc 2.11...

As far as I know glibc uses symbol versioning. Can I force gcc to link against a specific symbol version?

In my concrete use I try to compile a gcc cross toolchain for ARM.

解决方案

You are correct in that glibc uses symbol versioning. If you are curious, the symbol versioning implementation introduced in glibc 2.1 is described here and is an extension of Sun's symbol versioning scheme described here.

One option is to statically link your binary. This is probably the easiest option.

You could also build your binary in a chroot build environment, or using a glibc-new => glibc-old cross-compiler.

According to the http://www.trevorpounds.com blog post Linking to Older Versioned Symbols (glibc), it is possible to to force any symbol to be linked against an older one so long as it is valid by using the the same .symver pseudo-op that is used for defining versioned symbols in the first place. The following example is excerpted from the blog post.

The following example makes use of glibc’s realpath, but makes sure it is linked against an older 2.2.5 version.

#include

__asm__(".symver realpath,realpath@GLIBC_2.2.5");

int main()

{

char* unresolved = "/lib64";

char resolved[PATH_MAX+1];

if(!realpath(unresolved, resolved))

{ return 1; }

printf("%s\n", resolved);

return 0;

}