From: Tobias Klauser <tklauser@distanz.ch>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/libnet: fix compilation with musl
Date: Tue, 15 Nov 2016 12:32:56 +0100 [thread overview]
Message-ID: <20161115113256.GA3373@distanz.ch> (raw)
In-Reply-To: <20161115113858.1beeb768@free-electrons.com>
On 2016-11-15 at 11:38:58 +0100, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
> On Mon, 14 Nov 2016 12:29:47 +0100, Tobias Klauser wrote:
> > Patch taken from from upstream:
> > https://github.com/sam-github/libnet/commit/ffd7fab744a9ad2893169a8fb6244074604d5d0d
> >
> > Adjusted the file paths manually so the patch applies to the packaged
> > libnet sources.
> >
> > Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
> > ---
> > package/libnet/0001-support-musl-libc.patch | 50 +++++++++++++++++++++++++++++
> > 1 file changed, 50 insertions(+)
> > create mode 100644 package/libnet/0001-support-musl-libc.patch
>
> Adding the patch fixing the musl build issue is good... but if you
> don't adjust the Config.in file of this package to re-enable it for
> musl configurations, it's a bit useless, no?
>
> So I've fixed that, and applied your patch to next. Thanks!
Indeed, I forgot to stage that change in my local commit. Sorry about
that and thanks for fixing it up!
next prev parent reply other threads:[~2016-11-15 11:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 11:29 [Buildroot] [PATCH 0/2] musl support for libnet and netsniff-ng Tobias Klauser
2016-11-14 11:29 ` [Buildroot] [PATCH 1/2] package/libnet: fix compilation with musl Tobias Klauser
2016-11-15 10:38 ` Thomas Petazzoni
2016-11-15 11:32 ` Tobias Klauser [this message]
2016-11-14 11:29 ` [Buildroot] [PATCH 2/2] package/netsniff-ng: allow to build " Tobias Klauser
2016-11-15 10:39 ` Thomas Petazzoni
2016-11-15 11:35 ` Tobias Klauser
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=20161115113256.GA3373@distanz.ch \
--to=tklauser@distanz.ch \
--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