.symver under gcc 9.x and 10.x

[signalogic]

.symver under gcc 9.x and 10.x

[rocallahan]

I have no idea about this.

[signalogic]

Ok thanks. I documented the problem in detail in the comments section at:

https://maskray.me/blog/2020-11-26-all-about-symbol-versioning

it seems corrected under gcc 11.x and higher

[rocallahan]

-with just the version script, functionality is achieved, but I'm hoping there is way to avoid gcc version work-arounds

What do you mean "with just the version script"?

[signalogic]

cat > a.map <<e
GLIBC_2.2.5 { dlsym; };
e
gcc cmd line ... -Wl,--version-script=a.map -o a.so

[rocallahan]

So that works with all versions of gcc? Any reason to not use that all the time?

[signalogic]

with gcc 4.x thru 10.x and only the version script, objdump on the resulting lib shows:

0000000000000000 g DO ABS 0000000000000000 GLIBC_2.2.5 GLIBC_2.2.5

which looks odd to me. With 11.x, the .symver is required, and objdump shows:

0000000000000000 DF UND 0000000000000000 GLIBC_2.2.5 dlsym

which looks correct to me. I haven't tried 12.x yet, planning to do that