[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: texinfo-6.8.90 pretest

From: pertusus
Subject: Re: texinfo-6.8.90 pretest
Date: Sun, 23 Oct 2022 11:45:02 +0200

On Sun, Oct 23, 2022 at 08:56:13AM +0300, Eli Zaretskii wrote:
> AFAIU, the Win32::API module is present in all native Perl versions
> for Windows (I'm using ActiveState Perl).  It is not clear to me which
> was the earliest version of Perl which came with it built-in (mine is
> 5.20.1, and it does have it), but it was available for installation
> since at least 5.5.3, according to this page:
>   http://computer-programming-forum.com/53-perl/d5e2471137461aea.htm


> > (My very wild guess is that perl on windows in
> > environement emulating GNU/Linux or another Unix, such as cygwin, MinGW
> > or the Windows Subsystem for Linux have langinfo.)
> I have two different versions of MSYS Perl here: 5.8.8 and 5.22.1.
> The former doesn't have I18N::Langinfo, the latter does.  But I cannot
> use any of these Perl versions in the native Windows port of Texinfo,
> because MSYS programs are not usually installed on Windows systems,
> except as part of the MinGW/MSYS development environment.  Moreover,
> if MinGW GCC is used to compile the Texinfo's XS modules, the MSYS
> Perl will be unable to load those modules, due to ABI
> incompatibilities (MSYS programs require the MSYS DLL, which is their
> version of libc runtime, and is incompatible with the Windows native
> runtime).
> So I think having a solution for native Windows ports of texi2any that
> doesn't rely on I18N:Langinfo is the way to go.

Indeed, but this remark was more to try to assess if I18N::Langinfo
would be present and work on non native Windows ports.  The MSYS Perl
5.8.8 is likely to fail too, if I18N::Langinfo is not present.  5.8.8 is
quite old, so I am not really concerned by this case, but if it was not
present in 5.16.0, for instance, it could be more problematic.  Let's
wait for user feedback on that.  If we do not have any for 3 years,
we'll be ok ;-).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]