On Tue, Jun 15, 2021 at 9:00 PM Andrii Nakryiko <andrii.nakryiko@xxxxxxxxx> wrote: > > On Tue, Jun 15, 2021 at 9:42 AM Geyslan G. Bem <geyslan@xxxxxxxxx> wrote: > > > > On Tue, 15 Jun 2021 at 12:58, KP Singh <kpsingh@xxxxxxxxxx> wrote: > > > > > > On Tue, Jun 15, 2021 at 4:57 PM Geyslan G. Bem <geyslan@xxxxxxxxx> wrote: > > > > > > > > On Tue, 15 Jun 2021 at 11:33, KP Singh <kpsingh@xxxxxxxxxx> wrote: > > > > > > > > > > On Tue, Jun 15, 2021 at 2:34 PM Geyslan G. Bem <geyslan@xxxxxxxxx> wrote: [...] > > > > > > [...] > > > > > > It seems like arch does not have them: > > > > > > https://bbs.archlinux.org/viewtopic.php?id=245303 > > > > Indeed. > > > > > > > > and they don't plan to either. So you can either build the library locally > > > or possibly move to a distribution that provides static linking. > > > > I think this would keep things in different host environments > > complicated. I'm more likely to create a proper VM to handle kernel > > source and bpf tests, since bpf also demands llvm13 (cutting edge) > > which is conflicting with other projects. > > > > KP, how do you feel about teaching vmtest.sh to (optionally, if > requested or if we detect that environment clang is too old) checkout > clang and build it before building selftests? So many people would be > grateful for this, I imagine! ;) I agree, I also want to do it for pahole. It will save a lot of time when a build error could simply be solved by updating clang and pahole. > > > > > > > [incase we decide to use the static linking for vmtest.sh] > > > > It's still a good decision for environments with readily available > > static binaries. > > yeah, it's a good option to have at the very least Cool, will send a patch for this. - KP > > > > > Thanks a million for your attention. > > > > -- > > Regards, > > > > Geyslan G. Bem
