All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniele Forsi <dforsi@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH obexd] Fix compilation when NEED_G_SLIST_FREE_FULL is defined
Date: Thu,  4 Aug 2011 00:20:38 +0200	[thread overview]
Message-ID: <1312410038-21169-1-git-send-email-dforsi@gmail.com> (raw)

From: Daniele Forsi <daniele@forsi.it>

To use the replacement for g_slist_free_full() both compat.h and
glib-helper.h need to be included.

Fixes:
gobex/gobex.c:911: error: implicit declaration of function 'g_slist_free_full'
tools/test-server.c:344: error: implicit declaration of function ‘g_slist_free_full’
---
 gobex/gobex.c       |    5 +++++
 tools/test-server.c |    4 ++++
 2 files changed, 9 insertions(+), 0 deletions(-)

diff --git a/gobex/gobex.c b/gobex/gobex.c
index 2a64849..ff35830 100644
--- a/gobex/gobex.c
+++ b/gobex/gobex.c
@@ -19,11 +19,16 @@
  *
  */
 
+#ifdef HAVE_CONFIG_H
+# include "config.h"
+#endif
+
 #include <unistd.h>
 #include <string.h>
 #include <errno.h>
 
 #include "gobex.h"
+#include "glib-helper.h"
 
 #define G_OBEX_DEFAULT_MTU	4096
 #define G_OBEX_MINIMUM_MTU	255
diff --git a/tools/test-server.c b/tools/test-server.c
index 87742ec..6096737 100644
--- a/tools/test-server.c
+++ b/tools/test-server.c
@@ -19,6 +19,10 @@
  *
  */
 
+#ifdef HAVE_CONFIG_H
+# include "config.h"
+#endif
+
 #include <sys/types.h>
 #include <sys/socket.h>
 #include <fcntl.h>
-- 
1.7.1


             reply	other threads:[~2011-08-03 22:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-03 22:20 Daniele Forsi [this message]
2011-08-04  8:23 ` [PATCH obexd] Fix compilation when NEED_G_SLIST_FREE_FULL is defined Luiz Augusto von Dentz
2011-08-04  8:43 ` Johan Hedberg

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=1312410038-21169-1-git-send-email-dforsi@gmail.com \
    --to=dforsi@gmail.com \
    --cc=linux-bluetooth@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.