On Tue, Feb 02, 2021 at 01:29:20PM +, Niko Tyni wrote:
> On Sun, Nov 08, 2020 at 10:10:32PM +0100, John Paul Adrian Glaubitz wrote:
> > On 11/8/20 9:57 PM, Dominic Hargreaves wrote:
> > > Right, it looks like the issue described at #931641 has returned.
> > > This
hurry to get perl_5.32 to be built not to fall back in the
> transition *sigh*.
Hi, a late heads-up that Perl 5.32.1 failed to build on m68k and sh4,
probably because of this same issue.
It's just a mini-transition though (see #981232) so hopefully the hurry
is not quite as bad this time.
--
Niko Tyni nt...@debian.org
Hi m68k porters,
perl_5.32.0~rc1-1 in experimental failed to build on m68k with a
SIGSEGV in miniperl. Could somebody please look at this and see if it's
reproducible? Guess it could be either an actual source regression or
"just" a toolchain/platform problem.
Thanks for your work
On Sun, Jul 07, 2019 at 12:07:27PM +0200, John Paul Adrian Glaubitz wrote:
> So, some more information: This issue affects qemu-user only and can be
> reproduced
> on armhf as well. If this is an issue with Perl in general, it means that this
> particular version of Perl will not work on any vers
27;t figured it out yet.
Based on data from two uploads, this seems to be deterministic and
really only affecting these two architectures. Are there porter machines
available to test this on, or (even better) would somebody be willing
to dig into this and provide a patch?
Thanks for your work on D
5 matches
Mail list logo
