From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] swupdate: add upstream patch to fix musl build issue
Date: Thu, 18 Jan 2018 22:12:12 +0100 [thread overview]
Message-ID: <20180118221212.19e9303d@windsurf.lan> (raw)
In-Reply-To: <20180118125121.28953-1-joerg.krause@embedded.rocks>
Hello,
On Thu, 18 Jan 2018 13:51:21 +0100, J?rg Krause wrote:
> Add upstream patch to fix build issue with the musl C library, as musl
> does not provide the GNU extension `strndupa()` breaking the build with
> an undefined reference:
>
> ```
> ipc/lib.a(network_ipc.o): In function `ipc_postupdate':
> network_ipc.c:(.text.ipc_postupdate+0x39): undefined reference to `strndupa'
> ```
>
> The upstream patch provides a compatibility header file adding a definition
> of `strndupa` if it is not already defined.
>
> Backported from:
> https://github.com/sbabic/swupdate/commit/9867a9d6a21e6b0b9bcba57c3e2398fe671cea17
>
> Fixes:
> http://autobuild.buildroot.net/results/f674219225d0b67d0bc78fd10b47a865250746f4/
> http://autobuild.buildroot.net/results/d2b0cfcfec583d203af1b26152f14ded3ebd3eee/
> http://autobuild.buildroot.net/results/1d0cbd1eb9b1b70bd9f4d1c4fae431baee9d105c/
>
> Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> ---
> ...1-compat.h-introduce-compatibility-header.patch | 87 ++++++++++++++++++++++
> 1 file changed, 87 insertions(+)
> create mode 100644 package/swupdate/0001-compat.h-introduce-compatibility-header.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2018-01-18 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 12:51 [Buildroot] [PATCH] swupdate: add upstream patch to fix musl build issue Jörg Krause
2018-01-18 21:12 ` Thomas Petazzoni [this message]
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=20180118221212.19e9303d@windsurf.lan \
--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