public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/28555] uclibc compile failure since commit 4655f8509fd44e6efabefa373650d9982ff37fd6
Date: Tue, 09 Nov 2021 15:29:24 +0000	[thread overview]
Message-ID: <bug-28555-4717-7gvBddl9lu@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28555-4717@http.sourceware.org/bugzilla/>

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

--- Comment #7 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=0b03c6f03d51f441d999e0cee92f81af543d9373

commit 0b03c6f03d51f441d999e0cee92f81af543d9373
Author: Tom Tromey <tromey@adacore.com>
Date:   Wed May 12 12:39:22 2021 -0600

    Fix build on rhES5

    The rhES5 build failed due to an upstream import a while back.  The
    bug here is that, while the 'personality' function exists,
    ADDR_NO_RANDOMIZE is only defined in <linux/personality.h>, not
    <sys/personality.h>.

    However, <linux/personality.h> does not declare the 'personality'
    function, and <sys/personality.h> and <linux/personality.h> cannot
    both be included.

    This patch restores one of the removed configure checks and updates
    the code to check it.

    We had this as a local patch at AdaCore, because it seemed like there
    was no interest upstream.  However, now it turns out that this fixes
    PR build/28555, so I'm sending it now.

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

  parent reply	other threads:[~2021-11-09 15:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-06 12:20 [Bug build/28555] New: " ps.report at gmx dot net
2021-11-08 17:15 ` [Bug build/28555] " simark at simark dot ca
2021-11-08 17:15 ` simark at simark dot ca
2021-11-08 18:00 ` pedro at palves dot net
2021-11-08 19:16 ` simark at simark dot ca
2021-11-08 19:42 ` tromey at sourceware dot org
2021-11-08 20:42 ` simark at simark dot ca
2021-11-08 21:29 ` tromey at sourceware dot org
2021-11-09 15:29 ` cvs-commit at gcc dot gnu.org [this message]
2021-11-09 15:30 ` tromey at sourceware dot org
2021-11-09 18:01 ` ps.report at gmx dot net
2021-11-09 21:26 ` cvs-commit at gcc dot gnu.org
2021-11-09 21:26 ` tromey at sourceware dot org

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-28555-4717-7gvBddl9lu@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).