Friday, May 3, 2024
HomeGolangCompiling in opposition to outdated Glibc nonetheless ends in some symbols used...

Compiling in opposition to outdated Glibc nonetheless ends in some symbols used from Glibc 2.33 – Getting Assist


I’m attempting to compile a binary suitable with Debian Bullseye on Debian Bookworm. I’ve already unpacked outdated Glibc/OpenSSL for Bullseye and tried to hyperlink in opposition to them:

export CGO_LDFLAGS="-Xlinker -rpath=/residence/bodqhrohro/git/glibc/lib/x86_64-linux-gnu,-rpath=/residence/bodqhrohro/git/libssl/usr/lib/x86_64-linux-gnu,--dynamic-linker=/residence/bodqhrohro/git/glibc/lib64/ld-linux-x86-64.so.2 -L/residence/bodqhrohro/git/libssl/usr/lib/x86_64-linux-gnu -L/residence/bodqhrohro/git/glibc/lib/x86_64-linux-gnu -include /residence/bodqhrohro/git/force_link_glibc_2.27.h"

However within the ensuing binary there nonetheless are some symbols requiring Glibc 2.33:

0000000000000000       F *UND*  0000000000000000              lstat64@GLIBC_2.33
0000000000000000       F *UND*  0000000000000000              fstat64@GLIBC_2.33
0000000000000000       F *UND*  0000000000000000              stat64@GLIBC_2.33

How can I overcome this?

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

Recent Comments