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 gdb/18957] Error: static declaration of setns follows non-static declaration
Date: Mon, 14 Sep 2015 10:06:00 -0000	[thread overview]
Message-ID: <bug-18957-4717-JUSFhB2VUh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18957-4717@http.sourceware.org/bugzilla/>

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

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The gdb-7.10-branch branch has been updated by Gary Benson
<gary@sourceware.org>:

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

commit a8c636cb54328fb9a71dcf27b66a7e7ab5443d88
Author: Gary Benson <gbenson@redhat.com>
Date:   Mon Sep 14 11:02:06 2015 +0100

    Fix build issue with nat/linux-namespaces.c

    This commit fixes a build issue on systems with a prototype for setns
    in their header files but no working setns is detected by configure.

    gdb/ChangeLog:

        PR gdb/18957
        * nat/linux-namespaces.c (setns): Rename from this ...
        (do_setns): ... to this.  Support calling setns if it exists.
        (mnsh_handle_setns): Call do_setns.

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


  reply	other threads:[~2015-09-14 10:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-12 12:24 [Bug gdb/18957] New: " dcollinsn at gmail dot com
2015-09-14 10:06 ` cvs-commit at gcc dot gnu.org [this message]
2015-09-14 10:12 ` [Bug gdb/18957] " gbenson at redhat dot com
2021-11-09  8:28 ` johnsjvi95 at gmail 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-18957-4717-JUSFhB2VUh@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).