public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: "Горбешко Богдан" <bodqhrohro@gmail.com>
To: libc-help@sourceware.org
Subject: libstdc++ link errors in support/links-dso-program
Date: Fri, 15 Mar 2024 05:09:06 +0200	[thread overview]
Message-ID: <f6689a42-cfd3-495d-aaf1-a59fc4096c50@gmail.com> (raw)

Hi.

I attempt to build glibc 2.31 on Debian GNU/Linux 12 Bookworm. It fails at:

gcc 
-Wl,-rpath-link=/home/bodqhrohro/git/glibc-2.31-build:/home/bodqhrohro/git/glibc-2.31-build/math:/home/bodqhrohro/git/glibc-2.31-build/elf:/home/bodqhrohro/git/glibc-2.31-build/dlfcn:/home/bodqhrohro/git/glibc-2.31-build/nss:/home/bodqhrohro/git/glibc-2.31-build/nis:/home/bodqhrohro/git/glibc-2.31-build/rt:/home/bodqhrohro/git/glibc-2.31-build/resolv:/home/bodqhrohro/git/glibc-2.31-build/mathvec:/home/bodqhrohro/git/glibc-2.31-build/support:/home/bodqhrohro/git/glibc-2.31-build/crypt:/home/bodqhrohro/git/glibc-2.31-build/nptl 
-pie -Wl,-O1 -nostdlib -nostartfiles -o 
/home/bodqhrohro/git/glibc-2.31-build/support/links-dso-program 
-Wl,-z,combreloc -Wl,-z,relro -Wl,--hash-style=both 
/home/bodqhrohro/git/glibc-2.31-build/csu/Scrt1.o 
/home/bodqhrohro/git/glibc-2.31-build/csu/crti.o `gcc 
--print-file-name=crtbeginS.o` 
/home/bodqhrohro/git/glibc-2.31-build/support/links-dso-program.o 
-lstdc++ -lgcc -lgcc_s 
-Wl,-dynamic-linker=/home/bodqhrohro/git/glibc-2.31-build/lib/ld-linux-x86-64.so.2 
/home/bodqhrohro/git/glibc-2.31-build/libc.so.6 
/home/bodqhrohro/git/glibc-2.31-build/libc_nonshared.a -Wl,--as-needed 
/home/bodqhrohro/git/glibc-2.31-build/elf/ld.so -Wl,--no-as-needed 
-lgcc  `gcc  --print-file-name=crtendS.o` 
/home/bodqhrohro/git/glibc-2.31-build/csu/crtn.o
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/12/libstdc++.so: undefined 
reference to `fstat64@GLIBC_2.33'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/12/libstdc++.so: undefined 
reference to `pthread_key_create@GLIBC_2.34'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/12/libstdc++.so: undefined 
reference to `pthread_rwlock_unlock@GLIBC_2.34'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/12/libstdc++.so: undefined 
reference to `pthread_detach@GLIBC_2.34'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/12/libstdc++.so: undefined 
reference to `pthread_setspecific@GLIBC_2.34'
/usr/bin/ld: 
/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libgcc_s.so.1: 
undefined reference to `_dl_find_object@GLIBC_2.35'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/12/libstdc++.so: undefined 
reference to `arc4random@GLIBC_2.36'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/12/libstdc++.so: undefined 
reference to `__libc_single_threaded@GLIBC_2.32'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/12/libstdc++.so: undefined 
reference to `pthread_join@GLIBC_2.34'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/12/libstdc++.so: undefined 
reference to `pthread_rwlock_wrlock@GLIBC_2.34'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/12/libstdc++.so: undefined 
reference to `pthread_getspecific@GLIBC_2.34'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/12/libstdc++.so: undefined 
reference to `pthread_key_delete@GLIBC_2.34'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/12/libstdc++.so: undefined 
reference to `lstat@GLIBC_2.33'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/12/libstdc++.so: undefined 
reference to `stat@GLIBC_2.33'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/12/libstdc++.so: undefined 
reference to `pthread_once@GLIBC_2.34'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/12/libstdc++.so: undefined 
reference to `pthread_rwlock_rdlock@GLIBC_2.34'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/12/libstdc++.so: undefined 
reference to `pthread_create@GLIBC_2.34'
collect2: error: ld returned 1 exit status
make[2]: *** [../Rules:215: 
/home/bodqhrohro/git/glibc-2.31-build/support/links-dso-program] Error 1


Is that because it attempts to link against the system libstdc++, which 
is too new and requires symbols not present in this glibc version? Do I 
need to compile it myself? Or maybe even the whole GCC? I attempted to 
configure it without the SELinux support, but there's still the same 
problem.


             reply	other threads:[~2024-03-15  3:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15  3:09 Горбешко Богдан [this message]
2024-03-15  7:27 ` Florian Weimer
2024-03-15 11:51   ` Горбешко Богдан
2024-03-15 17:07     ` Florian Weimer
2024-03-15 19:22       ` Горбешко Богдан
2024-04-10 12:03         ` Florian Weimer
2024-04-10 12:50           ` Горбешко Богдан
2024-04-10 13:22             ` Konstantin Kharlamov
2024-04-10 13:30               ` Горбешко Богдан
2024-04-10 13:55                 ` Konstantin Kharlamov
2024-04-10 14:02                   ` Горбешко Богдан
2024-04-10 14:11                     ` Konstantin Kharlamov
2024-04-10 14:24                       ` Горбешко Богдан

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f6689a42-cfd3-495d-aaf1-a59fc4096c50@gmail.com \
    --to=bodqhrohro@gmail.com \
    --cc=libc-help@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).