public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jcmvbkbc at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libbacktrace/114941] New: libbacktrace build is broken for FDPIC uclibc targets by gcc-14-5173-g2b64e4a54042 Date: Fri, 03 May 2024 20:08:58 +0000 [thread overview] Message-ID: <bug-114941-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114941 Bug ID: 114941 Summary: libbacktrace build is broken for FDPIC uclibc targets by gcc-14-5173-g2b64e4a54042 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libbacktrace Assignee: unassigned at gcc dot gnu.org Reporter: jcmvbkbc at gcc dot gnu.org CC: ian at gcc dot gnu.org Target Milestone: --- A fix for the https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111315 turned on the use of the dl_iterate_phdr interface in the libbacktrace, but since the type of the dl_phdr_info::dlpi_addr on FDPIC targets using uclibc is not compatible with uintptr_t the libstdc++-v3 build breaks for these targets with the following message: elf.c:7372:62: error: incompatible type for argument 6 of ‘elf_add’ 7372 | if (elf_add (pd->state, filename, descriptor, NULL, 0, info->dlpi_addr, | ~~~~^~~~~~~~~~~ | | | struct elf32_fdpic_loadaddr elf.c:6504:20: note: expected ‘uintptr_t’ {aka ‘unsigned int’} but argument is of type ‘struct elf32_fdpic_loadaddr’
next reply other threads:[~2024-05-03 20:08 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-03 20:08 jcmvbkbc at gcc dot gnu.org [this message] 2024-05-03 20:14 ` [Bug libbacktrace/114941] libbacktrace build is broken for FDPIC uclibc targets by r14-5173-g2b64e4a54042 pinskia at gcc dot gnu.org 2024-05-03 22:37 ` ian at airs dot com 2024-05-04 8:35 ` jcmvbkbc at gcc dot gnu.org 2024-05-27 7:17 ` jcmvbkbc 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-114941-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).