Hi,

On Wed, Jan 10, 2024 at 6:22 AM Niko Tyni <[email protected]> wrote:
>
> On Wed, Dec 13, 2023 at 03:47:05PM +0800, Bo YU wrote:
> > Package: perl
> > Version: 5.36.0-10
> > Followup-For: Bug #1024636
> > Tags: patch
> > X-Debbugs-Cc: [email protected]
> >
> > Dear Maintainer,
> >
> > I have followed the instructions from debian/cross/README to generate
> > these files which support cross build from native build on loong64 host.
> > but it is unclear to me how to verify if this binary works like you
> > comment on -1[#10]. Could you give me a little hint?
> >
> > But I think it should be no problem.
> >
> > [#10]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024636#10
>
> Hi, thanks for your efforts. I only saw your message now as you mailed
> [email protected] which is not forwarded to the maintainer.
> Please use just [email protected] in the future.
okay.:)
>
> If the files are from a native build that passed the Perl test suite
> during the build, that's totally acceptable. My concern was about the
> previous hand crafted cross config files that looked like nobody had
> ever tested them at all. For such hand crafting, I suppose a minimal
> test would be to install the cross built binary perl packages on an
> actual loong64 host and run 'perl -V' or something like that.
>
> However, I'm afraid we have missed the train here: your patch is for
> Perl 5.36 but we're now moving to 5.38 (with perl_5.38.2-2 building in
> Debian unstable right now.) It makes little sense to include the 5.36
> config files now, so unfortunately you'll have to redo the process with
> the 5.38 package.
No worried. I will test these cross configs based on 5.38 on loong64
machines again.
Yeah, when I sent the patch I realized maybe we will transit to 5.38
because it was in experimental for a long time.

>
> Apologies for the awkward process. It's all workarounds for perl upstream
> not supporting cross configuration properly due to lots of historical
> baggage.
No problem.Many thanks for your work also.

BR,
Bo
> --
> Niko Tyni   [email protected]

Reply via email to