public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] How to compile BATMAN V against linux backports cfg80211
Date: Wed, 08 Jun 2016 13:20:40 +0200	[thread overview]
Message-ID: <3964079.xB3saelhBu@bentobox> (raw)
In-Reply-To: <5757ED74.2010109@tu-bs.de>

[-- Attachment #1: Type: text/plain, Size: 914 bytes --]

On Wednesday 08 June 2016 12:03:32 Harms, Hannes wrote:
> 
> Hi,
> 
> I want to test the new batman V with throughput based metric, but I
> could not find out how to compile batman-adv against cfg80211 from linux 
> backports.

You cannot build against the backports modules with the batman-adv Makefile.
This is only for systems which don't replace cfg80211 with an incompatible
version. But you should have a look at the OpenWrt compile rules (especially
NOSTDINC_FLAGS [1]). It basically uses its own compat-hack header and uses
the rest from the backports compat layer + the new cfg80211 headers.

Most important here is that you don't compile against cfg80211.h of your
kernel when your backports stuff uses complete different struct definitions
(this is most likely what causes the crash on your system).

Kind regards,
	Sven 

[1] https://github.com/openwrt-routing/packages/blob/master/batman-adv/Makefile

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-06-08 11:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-08 10:03 [B.A.T.M.A.N.] How to compile BATMAN V against linux backports cfg80211 Harms, Hannes
2016-06-08 11:20 ` Sven Eckelmann [this message]
2016-06-09 13:44   ` Harms, Hannes
2016-06-10  8:15     ` Sven Eckelmann

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=3964079.xB3saelhBu@bentobox \
    --to=sven@narfation.org \
    --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