From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 9666B3858004; Mon,  1 Nov 2021 12:01:21 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9666B3858004
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: Mon, 01 Nov 2021 12:01:21 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: libc
X-Bugzilla-Version: 2.32
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: critical
X-Bugzilla-Who: adhemerval.zanella at linaro dot org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-28499-131-zccCXW07WQ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-28499-131@http.sourceware.org/bugzilla/>
References: <bug-28499-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: glibc-bugs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Glibc-bugs mailing list <glibc-bugs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/glibc-bugs>,
 <mailto:glibc-bugs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/glibc-bugs/>
List-Help: <mailto:glibc-bugs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/glibc-bugs>,
 <mailto:glibc-bugs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Nov 2021 12:01:21 -0000

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

--- Comment #5 from Adhemerval Zanella <adhemerval.zanella at linaro dot or=
g> ---
(In reply to Vignesh from comment #4)
> Hi,
>=20
> The below commit causes the issue
>=20
> https://github.com/bminor/glibc/commit/
> 783e641fbae0cd1ab32d278216247a6f793dd722
>=20
> there should be a commit message which explains this works only from
> binutils 2.27.

Are you trying to use (In reply to Vignesh from comment #4)
> Hi,
>=20
> The below commit causes the issue
>=20
> https://github.com/bminor/glibc/commit/
> 783e641fbae0cd1ab32d278216247a6f793dd722
>=20
> there should be a commit message which explains this works only from
> binutils 2.27.

This still does not explain the issue you are seeing.  At least on x86_64
(which defines ELF_INITFINI to 1) with glibc built with gcc-10 and binutils
2.25:

x86_64-linux-gnu-binutils-2.25$ ./testrun.sh /bin/bash ./export.sh=20
5
5

And I did this same experiment on armhf (wihch defines ELF_INITFINI to 0):

arm-linux-gnueabihf-binutils-2.25$ ./testrun.sh /bin/bash ./export.sh=20
5
5

So I think it something else to your environment.

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