From: Peter Seiderer <ps.report@gmx.net>
To: "José Pekkarinen" <jose.pekkarinen@unikie.com>
Cc: buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] New packages question
Date: Thu, 2 Dec 2021 19:30:49 +0100 [thread overview]
Message-ID: <20211202193049.13ceb96e@gmx.net> (raw)
In-Reply-To: <CAJPV9MrzFk0obQYSyFKeF-PgQfnOi6GKow3tSPomtLcmdor3Yw@mail.gmail.com>
Hello José,
On Thu, 2 Dec 2021 12:41:30 +0200, José Pekkarinen <jose.pekkarinen@unikie.com> wrote:
> Hi,
>
> I'm reading a package for bmx7 to be upstreamed.
>
> I found the following error in one of the toolchains
> (bootlin-x86-64-musl), and I wonder whether it is an issue
> in the toolchain, and if it can be a blocker for the package to
> be merged:
>
> In file included from
> /home/debian/br-test-pkg/bootlin-x86-64-musl/host/x86_64-buildroot-linux-musl/sysroot/usr/include/net/ethernet.h:10,
> from
> /home/debian/br-test-pkg/bootlin-x86-64-musl/host/x86_64-buildroot-linux-musl/sysroot/usr/include/iwlib.h:29,
> from ip.c:51:
> /home/debian/br-test-pkg/bootlin-x86-64-musl/host/x86_64-buildroot-linux-musl/sysroot/usr/include/netinet/if_ether.h:116:8:
> error: redefinition of ‘struct ethhdr’
> 116 | struct ethhdr {
> | ^~~~~~
>
> Best regards.
Sometimes the musl build failure is fixable, search the git history for
examples, e.g. [1], or at least resort disable for musl...
Regards,
Peter
[1] https://git.buildroot.net/buildroot/commit/?id=e0c1ce019f8a5aaf9f54ae85e18821048b23d940
>
>
> José Pekkarinen.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-12-02 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 10:41 [Buildroot] New packages question José Pekkarinen
2021-12-02 18:30 ` Peter Seiderer [this message]
2021-12-03 6:02 ` José Pekkarinen
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=20211202193049.13ceb96e@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@buildroot.org \
--cc=jose.pekkarinen@unikie.com \
/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