From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jakub Kicinski <jakub.kicinski@netronome.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Thomas Richter <tmricht@linux.ibm.com>,
Hendrik Brueckner <brueckner@linux.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Networking Development Mailing List
<netdev@vger.kernel.org>
Subject: Re: libbpf build broken on musl libc (Alpine Linux)
Date: Tue, 11 Sep 2018 14:24:53 -0700 [thread overview]
Message-ID: <20180911212451.hvnyfwyvcs4yojqy@ast-mbp> (raw)
In-Reply-To: <20180911121543.GB22689@kernel.org>
On Tue, Sep 11, 2018 at 09:15:43AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, Sep 11, 2018 at 12:22:18PM +0200, Jakub Kicinski escreveu:
> > On Mon, 10 Sep 2018 14:29:03 -0300, Arnaldo Carvalho de Melo wrote:
> > > After lunch I'll work on a patch to fix this,
>
> > Hi Arnaldo!
>
> > Any luck?
>
> Well, we need to apply the patch below and make tools/lib/str_error_r.c
> live in a library that libbpf and perf is linked to.
do you want us to take the patch or you're applying it yourself?
next prev parent reply other threads:[~2018-09-12 2:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 17:29 libbpf build broken on musl libc (Alpine Linux) Arnaldo Carvalho de Melo
2018-09-11 10:22 ` Jakub Kicinski
2018-09-11 12:15 ` Arnaldo Carvalho de Melo
2018-09-11 21:24 ` Alexei Starovoitov [this message]
2018-09-13 18:32 ` [RFC/fix] " Arnaldo Carvalho de Melo
2018-09-13 18:56 ` Alexei Starovoitov
2018-09-13 19:44 ` Arnaldo Carvalho de Melo
2018-09-17 15:16 ` Arnaldo Carvalho de Melo
2018-09-18 0:52 ` Alexei Starovoitov
2018-09-18 2:39 ` Jakub Kicinski
2018-09-18 4:18 ` Alexei Starovoitov
2018-09-18 13:15 ` Arnaldo Carvalho de Melo
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=20180911212451.hvnyfwyvcs4yojqy@ast-mbp \
--to=alexei.starovoitov@gmail.com \
--cc=acme@kernel.org \
--cc=brueckner@linux.ibm.com \
--cc=daniel@iogearbox.net \
--cc=jakub.kicinski@netronome.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tmricht@linux.ibm.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