[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191126183451.GC29071@kernel.org>
Date: Tue, 26 Nov 2019 15:34:51 -0300
From: Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>
To: Toke Høiland-Jørgensen <toke@...hat.com>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>,
Andrii Nakryiko <andriin@...com>,
Adrian Hunter <adrian.hunter@...el.com>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Jiri Olsa <jolsa@...nel.org>, Martin KaFai Lau <kafai@...com>,
Namhyung Kim <namhyung@...nel.org>, bpf@...r.kernel.org,
netdev@...r.kernel.org, linux-perf-users@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] libbpf: Fix up generation of bpf_helper_defs.h
Em Tue, Nov 26, 2019 at 05:38:18PM +0100, Toke Høiland-Jørgensen escreveu:
> Arnaldo Carvalho de Melo <arnaldo.melo@...il.com> writes:
>
> > Em Tue, Nov 26, 2019 at 12:10:45PM -0300, Arnaldo Carvalho de Melo escreveu:
> >> Hi guys,
> >>
> >> While merging perf/core with mainline I found the problem below for
> >> which I'm adding this patch to my perf/core branch, that soon will go
> >> Ingo's way, etc. Please let me know if you think this should be handled
> >> some other way,
> >
> > This is still not enough, fails building in a container where all we
> > have is the tarball contents, will try to fix later.
>
> Wouldn't the right thing to do not be to just run the script, and then
> put the generated bpf_helper_defs.h into the tarball?
I would rather continue just running tar and have the build process
in-tree or outside be the same.
- Arnaldo
Powered by blists - more mailing lists