Elliott Mitchell
2020-Dec-04 07:22 UTC
[Pkg-xen-devel] ARM64 broken between 2573117d09 and cfbd7c2fe0?
I've been having to do local builds for a while due to needing some cutting-edge bits... It had been a while since the last time I'd updated my Debian build. My most recent build, based off of d7e2e40e2e and with a bunch of patches appears to have failed. The last point I'm pretty sure worked as a build point for ARM64 for me is 2573117d09. I've got a copy of 406942d4b4, but I'm not 100% sure I did sufficient testing to call it working. Right now this is tenative, but things are being sufficiently problematic for me to worry ARM64 may currently be broken. -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | ehem+sigmsg at m5p.com PGP 87145445 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
Elliott Mitchell
2020-Dec-09 02:36 UTC
[Pkg-xen-devel] ARM64 broken between 2573117d09 and cfbd7c2fe0?
On Thu, Dec 03, 2020 at 11:22:52PM -0800, Elliott Mitchell wrote:> The last point I'm pretty sure worked as a build point for ARM64 for me > is 2573117d09. I've got a copy of 406942d4b4, but I'm not 100% sure I > did sufficient testing to call it working. > > Right now this is tenative, but things are being sufficiently problematic > for me to worry ARM64 may currently be broken.For the curious, I discovered the problem is 5a37207df52066efefe419c677b089a654d37afc. Even though this fixed one problem for someone, it causes a different problem elsewhere. Submitted upstream, it seems a good candidate for the stable branch as that commit got into the stable branch (meaning the stable branch got broken for me). -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | ehem+sigmsg at m5p.com PGP 87145445 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445