public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drvignesh1992 at gmail dot com" <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 10:48:28 +0000	[thread overview]
Message-ID: <bug-28499-131-650RPJ4pFL@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28499-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28499

--- Comment #6 from Vignesh <drvignesh1992 at gmail dot com> ---
Hi,

I hope we need to pass --enable-initfini-array configure option to either
binutils or gcc

I have tried with gcc 9.3 binutils 2.25.1 and glibc 2.32 without
--enable-initfini-array configure option passed to binutils and failed

in the same build passed --enable-initfini-array to binutils and could print
5,5

the same configure option works with gcc too

Is your binutils/gcc configured with --enable-initfini-array by default, if so
it will work.

check my below build matrix
glibc 2.32 bin 2.25.1 gcc 9.3 - without config option - FAIL
glibc 2.32 bin 2.25.2 gcc 9.3 - with config option to binutils - PASS
glibc 2.32 bin 2.25.2 gcc 9.3 - with config option to gcc - PASS

glibc 2.32 bin 2.26 gcc 6.5 - without config option - FAIL
glibc 2.32 bin 2.27 gcc 6.5 - without config option - PASS

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-11-02 10:48 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 [this message]
2021-11-02 12:47 ` adhemerval.zanella at linaro dot org
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-650RPJ4pFL@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: link
Be 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).