From: Sven Eckelmann <sven@narfation.org>
To: Alex Suykov <alex.suykov@gmail.com>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] musl build fixes
Date: Wed, 01 Apr 2015 22:02:14 +0200 [thread overview]
Message-ID: <1834234.ImvpviMFU3@sven-edge> (raw)
In-Reply-To: <20150401193550.GA24391@vostro>
[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]
On Wednesday 01 April 2015 22:35:50 Alex Suykov wrote:
[...]
> It's not that linux headers are not available in musl, they are.
> The problem is that musl provides its own standalone <netinet/if_ether.h>
> instead of including <linux/if_ether.h>, and if both get included at the
> same time, gcc complains about duplicate definitions.
>
> Can you please take a look at the patch below?
> That is enough to get a musl build, too, and it keeps packet.h intact.
>
> In glibc and uclibc at least, <netinet/if_ether.h> includes
> <linux/if_ether.h>, so those can be interchanged freely, and batctl already
> depends on netinet/* headers. With musl, that would break bitwise attribute
> of course,
> but only outside of the kernel, and that would be a musl issue anyway.
The linux/if_ether.h -> netinet/if_ether.h seems to be understandable (but
rather unfortunate).
I am not sure why why you include linux/types.h to the different source
files. Most likely because this include should actually be in packet.h as
mentioned in
https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2015-March/012930.html
https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/2015-March/012942.html
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-04-01 20:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 17:18 [B.A.T.M.A.N.] musl build fixes Alex Suykov
2015-04-01 17:36 ` Sven Eckelmann
2015-04-01 19:35 ` Alex Suykov
2015-04-01 20:02 ` Sven Eckelmann [this message]
2015-04-01 21:53 ` Alex Suykov
2015-04-02 6:39 ` Sven Eckelmann
2015-04-06 14:27 ` Alex Suykov
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=1834234.ImvpviMFU3@sven-edge \
--to=sven@narfation.org \
--cc=alex.suykov@gmail.com \
--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