public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mathieu.malaterre at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104363] hppa: __asm__ directive .global and multiple .symver not supported Date: Thu, 03 Feb 2022 09:45:40 +0000 [thread overview] Message-ID: <bug-104363-4-yErc177Zdc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104363-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104363 --- Comment #2 from Mathieu Malaterre <mathieu.malaterre at gmail dot com> --- I've downgraded binutils to version from bullseye, and I am getting the exact same symptoms: ``` libtool: link: ( cd ".libs" && rm -f "libkcapi.la" && ln -s "../libkcapi.la" "libkcapi.la" ) /bin/bash ./libtool --tag=CC --mode=link hppa-linux-gnu-gcc -g -O2 -fpie -fPIE -DPIE -Wl,-z,relro,-z,now -pie -o bin/kcapi-rng apps/bin_kcapi_rng-kcapi-rng.o apps/bin_kcapi_rng-app-internal.o libkcapi.la libtool: link: hppa-linux-gnu-gcc -g -O2 -fpie -fPIE -DPIE -Wl,-z -Wl,relro -Wl,-z -Wl,now -pie -o bin/.libs/kcapi-rng apps/bin_kcapi_rng-kcapi-rng.o apps/bin_kcapi_rng-app-internal.o ./.libs/libkcapi.so /usr/lib/gcc-cross/hppa-linux-gnu/11/../../../../hppa-linux-gnu/bin/ld: apps/bin_kcapi_rng-kcapi-rng.o: in function `main': /tmp/libkcapi-1.3.1/apps/kcapi-rng.c:302: undefined reference to `kcapi_rng_generate' /usr/lib/gcc-cross/hppa-linux-gnu/11/../../../../hppa-linux-gnu/bin/ld: /tmp/libkcapi-1.3.1/apps/kcapi-rng.c:328: undefined reference to `kcapi_memset_secure' ``` % apt-cache policy binutils-hppa-linux-gnu binutils-hppa-linux-gnu: Installed: 2.35.2-2 Candidate: 2.37.90.20220130-2 Version table: 2.37.90.20220130-2 500 500 http://deb.debian.org/debian sid/main amd64 Packages *** 2.35.2-2 100 100 /var/lib/dpkg/status
next prev parent reply other threads:[~2022-02-03 9:45 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-03 9:34 [Bug c/104363] New: " mathieu.malaterre at gmail dot com 2022-02-03 9:38 ` [Bug target/104363] " pinskia at gcc dot gnu.org 2022-02-03 9:45 ` mathieu.malaterre at gmail dot com [this message] 2022-02-03 9:47 ` mathieu.malaterre at gmail dot com 2022-02-03 11:18 ` pinskia at gcc dot gnu.org 2022-02-03 11:19 ` pinskia at gcc dot gnu.org 2022-02-03 17:13 ` danglin at gcc dot gnu.org 2022-02-03 17:32 ` dave.anglin at bell dot net 2022-02-07 8:18 ` mathieu.malaterre at gmail dot com 2022-02-07 8:20 ` mathieu.malaterre at gmail dot com 2022-02-22 9:15 ` mathieu.malaterre at gmail dot com 2022-02-22 14:42 ` dave.anglin at bell dot net
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-104363-4-yErc177Zdc@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).