public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/28499] Couldn't export variable to sub process Date: Tue, 02 Nov 2021 12:47:16 +0000 [thread overview] Message-ID: <bug-28499-131-fMiicJaFhV@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28499-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28499 Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |NOTABUG --- Comment #7 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> --- The initfini support is assumed while building glibc because it has been support for a *long* time (since glibc 2.1/binutils 2.12). What you might be seeing is just only recently gcc enables it as default for cross-compiling (13a39886940331149173b25d6ebde0850668d8b9). We do had a test for initfini support, but it was removed on glibc 2.23 (a9224562cbe9cfb0bd8d9e637a06141141f9e6e3) with the same justification is has been supported for a long time and assumed as default. In any case, this is not an issue with glibc. You might want to bring this on libc-alpha to maybe reinstate the initfini configure check as a fail-safe, but I think the best option is to enable initfini support directly on configure. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-11-02 12:47 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-26 14:40 [Bug libc/28499] New: " drvignesh1992 at gmail dot com 2021-10-26 20:15 ` [Bug libc/28499] " adhemerval.zanella at linaro dot org 2021-10-27 13:40 ` drvignesh1992 at gmail dot com 2021-10-27 14:04 ` adhemerval.zanella at linaro dot org 2021-11-01 10:10 ` drvignesh1992 at gmail dot com 2021-11-01 12:01 ` adhemerval.zanella at linaro dot org 2021-11-02 10:48 ` drvignesh1992 at gmail dot com 2021-11-02 12:47 ` adhemerval.zanella at linaro dot org [this message] 2021-11-12 10:50 ` fweimer at redhat 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-28499-131-fMiicJaFhV@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).