public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/103166] New: [12 regression] wrong dependency on getentropy on newlib-based targets Date: Wed, 10 Nov 2021 09:05:32 +0000 [thread overview] Message-ID: <bug-103166-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103166 Bug ID: 103166 Summary: [12 regression] wrong dependency on getentropy on newlib-based targets Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: clyon at gcc dot gnu.org Target Milestone: --- Since r12-5066, I've noticed numerous link failures on aarch64-none-elf like: FAIL: g++.dg/concepts/expression.C -std=gnu++17 (test for excess errors) Excess errors: /libstdc++-v3/src/c++11/random.cc:179: undefined reference to `getentropy' /libstdc++-v3/src/c++11/random.cc:179:(.text._ZNSt12_GLOBAL__N_117__libc_getentropyEPv+0x10): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `getentropy' /libstdc++-v3/src/c++11/random.cc:452: undefined reference to `getentropy' /libstdc++-v3/src/c++11/random.cc:452:(.text._ZNSt13random_device7_M_initERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x68): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `getentropy' /aci-gcc-fsf/sources/newlib/newlib/libc/stdlib/arc4random.c:89: undefined reference to `getentropy' /aci-gcc-fsf/sources/newlib/newlib/libc/stdlib/arc4random.c:89:(.text+0x558): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `getentropy' Maybe there's something wrong with the detection of HAVE_GETENTROPY in configure?
next reply other threads:[~2021-11-10 9:05 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-10 9:05 clyon at gcc dot gnu.org [this message] 2021-11-10 9:33 ` [Bug libstdc++/103166] " pinskia at gcc dot gnu.org 2021-11-10 9:43 ` redi at gcc dot gnu.org 2021-11-11 2:35 ` sandra at gcc dot gnu.org 2021-11-12 17:15 ` hp at gcc dot gnu.org 2021-11-12 19:02 ` redi at gcc dot gnu.org 2021-11-12 20:25 ` hp at gcc dot gnu.org 2021-11-13 0:46 ` cvs-commit at gcc dot gnu.org 2021-11-13 0:50 ` hp at gcc dot gnu.org 2021-11-13 0:58 ` hp at gcc dot gnu.org 2023-03-07 10:24 ` clyon at gcc dot gnu.org 2023-03-07 11:20 ` redi at gcc dot gnu.org
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=bug-103166-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).