public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bneumeier at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
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	[thread overview]
Message-ID: <bug-89140-4-Ee0edMnpvY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-89140-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89140

Brett Neumeier <bneumeier at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #2 from Brett Neumeier <bneumeier at gmail dot com> ---
(In reply to Andrew Pinski from comment #1)
> >the configure script for libiberty finds that getrusage is not available but wait4 is.
> 
> 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.

      parent reply	other threads:[~2021-09-06  2:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-89140-4@http.gcc.gnu.org/bugzilla/>
2021-09-01  0:55 ` pinskia at gcc dot gnu.org
2021-09-06  2:42 ` bneumeier at gmail dot com [this message]

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-89140-4-Ee0edMnpvY@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).