符号的@ GLIBC_2.2.5后缀有什么作用? [英] What does the @GLIBC_2.2.5 suffix on symbols do?

问题描述

@ GLIBC_2.2.5 用glibc内的符号做什么/意味着什么?

What does the@GLIBC_2.2.5 do/mean with symbols inside glibc?

我正在尝试在64位CLFS系统上构建软件包.我遇到了多个符号链接到/lib64/libc-2.15.so的未解决符号问题，但是，所有未解决的符号都有后缀 @ GLIBC_2.2.5 .

I'm attempting to build a package on a 64bit CLFS system. I'm getting unresolved symbol issues with multiple symbols linking against /lib64/libc-2.15.so, however, everything that is unresolved has a @GLIBC_2.2.5 suffix.

0000000000107910 T xdr_accepted_reply@GLIBC_2.2.5
0000000000112290 T xdr_array@GLIBC_2.2.5
0000000000109650 T xdr_authdes_cred@GLIBC_2.2.5

所以看起来像xc例程存在于libc-2.15中，但是我不能真正使用它们.我的目标文件中的符号没有该后缀.例如，.o上的nm仅显示'xdr_accepted_reply'.

So it LOOKS like the xdr routines exist in libc-2.15 but I can't really use them. The symbols in my object files do not have that suffix. For example, an nm on the .o shows just 'xdr_accepted_reply'.

我想首先了解这一点，因为我正被引导去追寻替换库.libtirpc获取XDR例程，其他库获取tirpc需要的缺少的加密例程.

I would like to understand this first since I'm being led down a path of chasing replacement libraries otherwise. libtirpc to get the XDR routines and the some other library to get the missing crypto routines that tirpc needs.

推荐答案

它们看起来像 共享库的版本符号(glibc)

随着链接后面内容的指出，您可以使用:

As the content behind the link will point out, you can use:

objdump -x wrapper-linux-x86-32  //and possibly -64

要获取有关可执行文件的很多信息...

To get a lot of information about the executable...

例如:

...
Version References:
required from libpthread.so.0:
0x0d696912 0x00 05 GLIBC_2.2
0x0d696911 0x00 04 GLIBC_2.1
0x0d696910 0x00 03 GLIBC_2.0
required from libc.so.6:
0x0d696913 0x00 08 GLIBC_2.3
0x0d696911 0x00 07 GLIBC_2.1
0x0d696912 0x00 06 GLIBC_2.2
0x0d696910 0x00 02 GLIBC_2.0
...

这篇关于符号的@ GLIBC_2.2.5后缀有什么作用?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！