Re: Bug#1003847: binutils breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and others)
On 2022-02-01 16:02, Tulio Magno Quites Machado Filho wrote:
> Aurelien Jarno <aurel32@debian.org> writes:
>
> > On 2022-01-19 22:08, John Paul Adrian Glaubitz wrote:
> >> Hi Aurelien!
> >>
> >> Unfortunately, glibc no longer builds with this change on powerpc and ppc64
> >> and kernel builds still fails on both targets:
> >>
> >> > https://buildd.debian.org/status/fetch.php?pkg=glibc&arch=powerpc&ver=2.33-3&stamp=1642542048&raw=0
> >> > https://buildd.debian.org/status/fetch.php?pkg=glibc&arch=ppc64&ver=2.33-3&stamp=1642542055&raw=0
> >
> > The ppc64el fix is not the cause for those failures. Previous glibc
> > versions also do not build on powerpc and ppc64 following the binutils
> > snapshot upload to sid. It's just that more code got broken on powerpc
> > and ppc64 than on ppc64el. I have queued the backported fixes from
> > upstream for the next upload.
>
> Are these issues happening when building glibc upstream too?
No, upstream built fine, and same now for the 2.33 and 2.34 branches
after I backported ee874f44fd55988808a4a162ef21bfa2cc8dc6f7.
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
Reply to: