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.] Compiling for Beaglebone
Date: Tue, 03 Nov 2015 13:59:26 +0100 [thread overview]
Message-ID: <6264428.4oiRdRIpY5@bentobox> (raw)
In-Reply-To: <CAFJkCXrOyDam2BHpUbcW9Qcd8ZBxOSbTeU6_kORkw6R3qELfLQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]
On Tuesday 03 November 2015 07:05:16 Justin Oursler wrote:
> Hello,
>
> Can someone help get me started in cross-compiling batman-adv and
> batctl? Specifically, I'm wanting to run it on a Beaglebone running
> Debian (http://beagleboard.org/project/debian/). I already have the
> arm-gnueabihf toolchain.
Why not compiling batctl and batman-adv on the beagleboard? This would make
the whole procedure a looooo[...]ooot easier. Just install build-essential,
libnl-3-dev, pkg-config and the linux-headers for your kernel.
I don't know what kernel you currently have installed and where it comes from.
But one of the kernels for this board comes from paulliu [1] and he gives you
the kernel headers for his kernel in the linux-headers package [2].
Otherwise you would need the same toolchain used to build the kernel, kernel
headers, config, libraries, ... and a lot of time and nerves. And when kernel
headers and toolchain is not provided for your kernel then you have to build
your own kernel anyway and then you can build your module against it [3].
Kind regards,
Sven
[1] https://wiki.debian.org/InstallingDebianOn/TI/BeagleBone
[2] https://people.debian.org/~paulliu/beaglebone/
[3] http://azkeller.com/blog/?p=129 (REMARK: KDIR is called KERNELPATH in
batman-adv)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-11-03 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 12:05 [B.A.T.M.A.N.] Compiling for Beaglebone Justin Oursler
2015-11-03 12:44 ` Simon Wunderlich
2015-11-03 12:59 ` Sven Eckelmann [this message]
2015-11-03 23:36 ` jens
2015-11-04 23:34 ` tjhowse
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=6264428.4oiRdRIpY5@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