From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 73C7B3858D3C; Mon, 6 Sep 2021 02:42:51 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 73C7B3858D3C From: "bneumeier at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/89140] libiberty/pex-unix.c fails to compile in aarch64-to-x86_64 cross build Date: Mon, 06 Sep 2021 02:42:51 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: bootstrap X-Bugzilla-Version: 8.2.0 X-Bugzilla-Keywords: build X-Bugzilla-Severity: normal X-Bugzilla-Who: bneumeier at gmail dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Sep 2021 02:42:51 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D89140 Brett Neumeier changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Brett Neumeier --- (In reply to Andrew Pinski from comment #1) > >the configure script for libiberty finds that getrusage is not available= but wait4 is. >=20 > Both should be there. Hello Andrew Pinski! Thank you for looking at this. I experimentally removed the patch from my build process and find that the issue no longer occurs with current versions of the GNU toolchain components (binutils 2.37, glibc 2.34, gcc 11.2.0). So there is probably no point in leaving this bug open. I'm marking it as resolved.=