Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Peter Bergner <bergner@vnet.ibm.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Gary Benson <gbenson@redhat.com>
Subject: [PATCH] Fix build issue due to Introduce nat/linux-namespaces.[ch] patch
Date: Thu, 09 Jul 2015 20:36:00 -0000	[thread overview]
Message-ID: <1436474110.5367.27.camel@otta> (raw)

I have a toolchain that dies building gdb with the following error:

/home/bergner/binutils/binutils-gdb/gdb/nat/linux-namespaces.c:39:1: error: static declaration of ‘setns’ follows non-static declaration
 setns (int fd, int nstype)
 ^
In file included from /opt/at7.0/include/sched.h:41:0,
                 from /home/bergner/binutils/binutils-gdb/gdb/nat/linux-namespaces.c:30:
/opt/at7.0/include/bits/sched.h:91:12: note: previous declaration of ‘setns’ was here
 extern int setns (int __fd, int __nstype) __THROW;
            ^
make[2]: *** [linux-namespaces.o] Error 1

My configure doesn't define HAVE_SETNS because my glibc defines __stub_setns,
so nat/linux-namespaces.c defines its own setns routine.  However, my glibc
also has its sched.h with a extern prototype for setns, which conflicts with
this static version linux-namespaces.c is creating, so we get the error above.
How about the following patch to work around the error?  I can confirm that
it fixes the problem on my multiple systems that do and do not have setns.

Ok for trunk?

Peter

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

diff --git a/gdb/nat/linux-namespaces.c b/gdb/nat/linux-namespaces.c
index a7a3e4d..c2f0d2e 100644
--- a/gdb/nat/linux-namespaces.c
+++ b/gdb/nat/linux-namespaces.c
@@ -34,18 +34,20 @@ int debug_linux_namespaces;

 /* Handle systems without setns.  */

-#ifndef HAVE_SETNS
-static int
-setns (int fd, int nstype)
+static inline int
+do_setns (int fd, int nstype)
 {
-#ifdef __NR_setns
-  return syscall (__NR_setns, fd, nstype);
+#ifdef HAVE_SETNS
+  return setns (fd, nstype);
 #else
+# ifdef __NR_setns
+  return syscall (__NR_setns, fd, nstype);
+# else
   errno = ENOSYS;
   return -1;
+# endif
 #endif
 }
-#endif

 /* Handle systems without MSG_CMSG_CLOEXEC.  */

@@ -495,7 +497,7 @@ mnsh_recv_message (int sock, enum mnsh_msg_type *type,
 static ssize_t
 mnsh_handle_setns (int sock, int fd, int nstype)
 {
-  int result = setns (fd, nstype);
+  int result = do_setns (fd, nstype);

   return mnsh_return_int (sock, result, errno);
 }



             reply	other threads:[~2015-07-09 20:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09 20:36 Peter Bergner [this message]
2015-07-14 14:46 ` Gary Benson
2015-07-14 15:50   ` Peter Bergner
2015-07-15 12:32     ` Gary Benson

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=1436474110.5367.27.camel@otta \
    --to=bergner@vnet.ibm.com \
    --cc=gbenson@redhat.com \
    --cc=gdb-patches@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