public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "suratiamol at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug build/26360] glibc 2.32 fails to crosscompile to ppc64le-linux-gnu using gcc 10.2.0 Date: Fri, 23 Oct 2020 21:39:34 +0000 [thread overview] Message-ID: <bug-26360-131-iFqBhWYqET@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26360-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26360 suratiamol at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |suratiamol at gmail dot com --- Comment #3 from suratiamol at gmail dot com --- Got the same error here too. The error, at least in the case of __asprintf, seems to occur because there are two declarations: // emitted by libio/bits/stdio-ldbl.h // __LDBL_REDIR2_DECL (asprintf) // commit: e4a399921390509418826e8e8995d2441f29e243 extern __typeof (__asprintf) __asprintf __asm ("" "__nldbl___" "asprintf"); // emitted by include/stdio.h // libc_hidden_ldbl_proto (__asprintf) // commit: 45ae17dd7ed3b9dea0d698d1c37a978d8d0a9aa2 extern __typeof (__asprintf) __asprintf __asm__ ("" "__GI___asprintf") __attribute__ ((visibility ("hidden"))); It is likely that the same two commits are involved in the errors about other symbols. Can reproduce the error with this dummy sample: extern int __asprintf(void); extern __typeof(__asprintf) __asprintf __asm("__nldbl___" "asprintf"); extern __typeof(__asprintf) __asprintf __asm__("__GI___asprintf") __attribute__((visibility("hidden"))); int main(){return 0;} //cc a.c -Werror -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-10-23 21:39 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-10 3:45 [Bug build/26360] New: " bero at lindev dot ch 2020-08-10 14:21 ` [Bug build/26360] " carlos at redhat dot com 2020-08-10 15:54 ` bero at lindev dot ch 2020-10-23 21:39 ` suratiamol at gmail dot com [this message] 2020-12-06 23:35 ` bero at lindev dot ch 2020-12-07 18:15 ` joseph at codesourcery dot com
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-26360-131-iFqBhWYqET@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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: 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).