From: Sven Eckelmann <sven@narfation.org>
To: "B.A.T.M.A.N" <b.a.t.m.a.n@lists.open-mesh.net>
Subject: [B.A.T.M.A.N.] [PATCH 0/3] batctl: Use libnl(-tiny) for netlink communication
Date: Mon, 06 Jan 2014 20:35:33 +0100 [thread overview]
Message-ID: <6312194.LhI8hzXjyH@bentobox> (raw)
[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]
Hi,
the current release 2014.0.0 made some problems for me because Debian the new
function "rtnl_open" conflicted with libnl-3.0. libnl-3.0 was used in the
Debian package to follow the Debian policy chapter 4 about duplicated code.
Using libnl should not be a problem for any linux system because everyone uses
it when wireless configuration is done. For example libnl-tiny is already used
by the normal OpenWrt system in base system packages:
* netifd
* swconfig
* authsae
* hostapd
* iproute2
* iw
* iwinfo
So it is nearly impossible to not have installed ;)
An additional benefit is the already tested code, better type checks and more
linear code instead of lot of loops to parse the data.
The Makefile is written in such a way that it:
* tries to find pkg-config (can be overwritten by setting PKG_CONFIG as
environment variable/make parameter)
* tries to find the libnl CFLAGS + LDLIBS (can be avoided by setting
LIBNL_CFLAGS/LIBNL_LDLIBS as environment variable/make parameter)
** the search for the CFLAGS + LDLIBS is done using pkg-config using the
library name libnl-3.0 (this can be changed by setting LIBNL_NAME
as environment variable/make parameter)
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2014-01-06 19:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 19:35 Sven Eckelmann [this message]
2014-01-06 19:37 ` [B.A.T.M.A.N.] [PATCH 1/3] batctl: Avoid name clash "rtnl_open" with libnl Sven Eckelmann
2014-01-06 19:37 ` [B.A.T.M.A.N.] [PATCH 2/3] batctl: Use libnl to implement mac resolver Sven Eckelmann
2014-01-23 8:21 ` Marek Lindner
2014-01-06 19:37 ` [B.A.T.M.A.N.] [PATCH 3/3] batctl: Use libnl to implement vlan parent device resolver Sven Eckelmann
2014-01-27 6:22 ` Marek Lindner
2014-01-23 7:28 ` [B.A.T.M.A.N.] [PATCH 1/3] batctl: Avoid name clash "rtnl_open" with libnl Marek Lindner
2014-01-16 21:11 ` [B.A.T.M.A.N.] [PATCH 0/3] batctl: Use libnl(-tiny) for netlink communication Antonio Quartulli
2014-01-17 9:37 ` Sven Eckelmann
2014-01-19 10:20 ` Antonio Quartulli
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=6312194.LhI8hzXjyH@bentobox \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.net \
--cc=b.a.t.m.a.n@lists.open-mesh.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