[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 6 Oct 2015 18:09:15 +0200
From: Denys Vlasenko <vda.linux@...glemail.com>
To: Rich Felker <dalias@...ifal.cx>
Cc: Rob Landley <rob@...dley.net>, Aboriginal Linux <aboriginal@...ts.landley.net>,
musl <musl@...ts.openwall.com>
Subject: Re: musl and kernel headers [was Re: system-images 1.4.2: od is
broken; bzip2 is missing]
On Tue, Oct 6, 2015 at 3:44 AM, Rich Felker <dalias@...ifal.cx> wrote:
>> >
>> > #include <netinet/in.h>
>> > #include <linux/if_bridge.h>
>> > results in:
>> > In file included from /usr/include/linux/if_bridge.h:18,
>> > from networking/brctl.c:67:
>> > /usr/include/linux/in6.h:32: error: redefinition of 'struct in6_addr'
>> > /usr/include/linux/in6.h:49: error: redefinition of 'struct sockaddr_in6'
>> > /usr/include/linux/in6.h:59: error: redefinition of 'struct ipv6_mreq'
>> >
>> > and
>> >
>> > #include <linux/ethtool.h>
>> > #include <net/ethernet.h>
>> > results in:
>> > In file included from /usr/include/net/ethernet.h:10,
>> > from networking/ifplugd.c:41:
>> > /usr/include/netinet/if_ether.h:96: error: redefinition of 'struct ethhdr'
>> >
>>
>> That I leave to Rich. :)
>
> Including kernel headers is just really problematic. These days they
> try to make it work on glibc with a complex dance between glibc's
> headers and the kernel headers. You're likely to have the best luck by
> including the libc headers first.
brctl.c was including <linux/if_bridge.h> after <netinet/in.h>
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
