Looking into the build failure of clisp on Ubuntu ppc64el, it looks like a difference in behavior of KASLR. Output from the failure log in the bug shows:
checking for the code address range... 0x000002AA39000000
Successive invocations on Ubuntu with a focal kernel show:
checking for the code address range... 0x000003E0F6000000
checking for the code address range... 0x00000654DF000000
And successive invocations on Debian show:
checking for the code address range... 0x0000000113000000
And the last successful build in Ubuntu had:
checking for the code address range... 0x0000000110000000
This is with focal 5.4.0 kernel.
And the build failure is also reproducible in a sid chroot on top of a focal kernel.
Looking into the build failure of clisp on Ubuntu ppc64el, it looks like a difference in behavior of KASLR. Output from the failure log in the bug shows:
checking for the code address range... 0x000002AA39000000
Successive invocations on Ubuntu with a focal kernel show:
checking for the code address range... 0x000003E0F6000000
checking for the code address range... 0x00000654DF000000
And successive invocations on Debian show:
checking for the code address range... 0x0000000113000000
And the last successful build in Ubuntu had:
checking for the code address range... 0x0000000110000000
This is with focal 5.4.0 kernel.
And the build failure is also reproducible in a sid chroot on top of a focal kernel.