-
926a9f6d · upgpkg: 1:1.28-3, python 3.13 rebuild
-
cb737f87 · upgpkg: 1:1.27-3: Rebuild for Python 3.13
closed
issue
#1
"Upgrade from 1.26-2 to 1.27-1 breaks kernel compilation"
at
Arch Linux / Packaging / Packages / pahole
-
50522114 · 1:1.27-2: Cherry-pick fixes for Clang
commented on
issue #1
"Upgrade from 1.26-2 to 1.27-1 breaks kernel compilation"
at
Arch Linux / Packaging / Packages / pahole
Yes, you are right. Ive picked both into our branch....
commented on
issue #1
"Upgrade from 1.26-2 to 1.27-1 breaks kernel compilation"
at
Arch Linux / Packaging / Packages / pahole
If we want to support kernel builds with Clang, we also need https://lore.kernel.org/dwarves/ZnGZ71a4E29kPrvS@x1
opened
issue
#1
"Upgrade from 1.26-2 to 1.27-1 breaks kernel compilation"
at
Arch Linux / Packaging / Packages / pahole
commented on
issue #1
"Upgrade from 1.26-2 to 1.27-1 breaks kernel compilation"
at
Arch Linux / Packaging / Packages / pahole
@gromit...
commented on
issue #1
"Upgrade from 1.26-2 to 1.27-1 breaks kernel compilation"
at
Arch Linux / Packaging / Packages / pahole
Also reported on lkml and bisected: https://lore.kernel.org/all/20240613214019.GA1423015@thelio-3990X/
commented on
issue #1
"Upgrade from 1.26-2 to 1.27-1 breaks kernel compilation"
at
Arch Linux / Packaging / Packages / pahole
I have forwarded the issue to the Clangbuiltlinux community.
commented on
issue #1
"Upgrade from 1.26-2 to 1.27-1 breaks kernel compilation"
at
Arch Linux / Packaging / Packages / pahole
The amount of commits is also not too big between the two versions, maybe you can also narrow it down by doing a bisection