Messages in this thread | | | From | Sedat Dilek <> | Date | Sun, 6 Mar 2022 16:31:24 +0100 | Subject | Re: [PATCH 1/3] [v3] Kbuild: move to -std=gnu11 |
| |
On Fri, Mar 4, 2022 at 5:25 PM Sedat Dilek <sedat.dilek@gmail.com> wrote: [ ... ] > When I saw the first patches in this area, I was thinking what about > the tools/ build-system? > This ECO system has its own rules. >
My other goal was to build perf with my selfmade or distro LLVM/Clang and -std=gnu11.
I was able to do so:
$ git log --oneline --no-merges v5.17-rc6..for-5.17/tools-std_gnu11-dileks-v2 2d99b1cfa897 (for-5.17/tools-std_gnu11-dileks-v2) perf: Use -std=gnu11 c345a183c4ef tools: libtraceevent: Use -std=gnu11 26f77082f233 tools: libsubcmd: Use -std=gnu11 aaba58ec81c8 tools: libbpf: Use -std=gnu11 ffc800af3be4 tools: libapi: Use -std=gnu11
For perf/libperl-support I needed an extra patch:
$ git log --oneline --no-merges v5.17-rc6..for-5.17/perf-libperl_support-clang-dileks 316a1917ec05 (for-5.17/perf-libperl_support-clang-dileks) perf: Fix libperl support with clang and perl v5.34
For details see [1].
I can send the patches if someone wants them.
[1] https://marc.info/?t=164646683300002&r=1&w=2
| |