From: Alexander Aring <alex.aring@gmail.com>
To: Stefan Schmidt <stefan@osg.samsung.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: [PATCH wpan-tools] build: avoid redefinition errors with libnl >= 3.2.27
Date: Mon, 9 Nov 2015 21:19:01 +0100 [thread overview]
Message-ID: <20151109201821.GA608@omega> (raw)
In-Reply-To: <1447092642-17115-1-git-send-email-stefan@osg.samsung.com>
Hi,
On Mon, Nov 09, 2015 at 07:10:42PM +0100, Stefan Schmidt wrote:
> From 3.2.17 onwards we have nla for s8, s16, etc defined directly in libnl.
> If we keep including this file anyway we run into redefinition errors. Better
> include use our own only for earlier versions.
>
> Happened to me on Fedora 22 after my last update.
>
> Signed-off-by: Stefan Schmidt <stefan@osg.samsung.com>
Acked-by: Alexander Aring <alex.aring@gmail.com>
I wonder how could that be when I do #ifndef on each declaration. So I
was in the hope to avoid such issues....
- Alex
next prev parent reply other threads:[~2015-11-09 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 18:10 [PATCH wpan-tools] build: avoid redefinition errors with libnl >= 3.2.27 Stefan Schmidt
2015-11-09 20:19 ` Alexander Aring [this message]
2015-11-09 21:11 ` Stefan Schmidt
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=20151109201821.GA608@omega \
--to=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=stefan@osg.samsung.com \
/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 NNTP newsgroup(s).