From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/irda-utils: fix musl build
Date: Sun, 7 Feb 2016 22:16:50 +0100 [thread overview]
Message-ID: <20160207221650.2ee89791@free-electrons.com> (raw)
In-Reply-To: <1454148798-28228-2-git-send-email-bernd.kuhls@t-online.de>
Dear Bernd Kuhls,
On Sat, 30 Jan 2016 11:13:18 +0100, Bernd Kuhls wrote:
> diff --git a/package/irda-utils/0004-musl.patch b/package/irda-utils/0004-musl.patch
> new file mode 100644
> index 0000000..e3e766f
> --- /dev/null
> +++ b/package/irda-utils/0004-musl.patch
> @@ -0,0 +1,37 @@
> +Fix musl build
> +
> +Downloaded from
> +http://cgit.openembedded.org/openembedded-core/plain/meta/recipes-connectivity/irda-utils/irda-utils-0.9.18/musl.patch
> +
> +Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
This...
> +
> +
> +Replace use of <net/if_packet.h> with <linux/if_packet.h>.
> +
> +kernel headers <linux/if_packet.h> already provides the
> +needed definitions, moreover not all libc implementations
> +provide if_packet.h e.g. musl
> +
> +Signed-off-by: Khem Raj <raj.khem@gmail.com>
> +Upstream-Status: Pending
... should have been here.
Applied after fixing this.
Can you check if the patch has really been submitted upstream? I
quickly looked in the irda-utils archives, and couldn't find it. Also,
if you could submit upstream the other patches we have, it would be
great.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-07 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 10:13 [Buildroot] [PATCH 1/1] package/ipsec-tools: fix broken download URL Bernd Kuhls
2016-01-30 10:13 ` [Buildroot] [PATCH 1/1] package/irda-utils: fix musl build Bernd Kuhls
2016-02-07 21:16 ` Thomas Petazzoni [this message]
2016-02-07 21:08 ` [Buildroot] [PATCH 1/1] package/ipsec-tools: fix broken download URL Thomas Petazzoni
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=20160207221650.2ee89791@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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