[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191127013901.GE29071@kernel.org>
Date: Tue, 26 Nov 2019 22:39:01 -0300
From: Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>
To: Jakub Kicinski <jakub.kicinski@...ronome.com>
Cc: Stanislav Fomichev <sdf@...ichev.me>,
Andrii Nakryiko <andrii.nakryiko@...il.com>,
Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>,
Toke Høiland-Jørgensen <toke@...hat.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 <bpf@...r.kernel.org>,
Networking <netdev@...r.kernel.org>,
linux-perf-users@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Quentin Monnet <quentin.monnet@...ronome.com>
Subject: Re: [PATCH] libbpf: Fix up generation of bpf_helper_defs.h
Em Tue, Nov 26, 2019 at 03:52:28PM -0800, Jakub Kicinski escreveu:
> On Tue, 26 Nov 2019 15:10:30 -0800, Stanislav Fomichev wrote:
> > We are using this script with python2.7, works just fine :-)
> > So maybe doing s/python3/python/ is the way to go, whatever
> > default python is installed, it should work with that.
> That increases the risk someone will make a python2-only change
> and break Python 3.
> Python 2 is dead, I'm honestly surprised this needs to be said :)
It shouldn't have to be said, and probably it is old school to try and
keep things portable when there is no need to use new stuff for simple
tasks like this.
Anyway, it seems its just a matter of adding the python3 package to the
old container images and then most of them will work with what is in
that script, what doesn't work is really old and then NO_LIBBPF=1 is the
way to go.
In the end, kinda nothing to see here, go back to adding cool new stuff,
lets not hold eBPF from progressing ;-P
- Arnaldo
Powered by blists - more mailing lists