If the system doesn't provide the getaddrinfo function it is emulated by the Socket module.

Yes, but in my recent Socket ticket, I found that d_getaddrinfo (and others) can be defined without causing any failure in a current blead built using the same Strawberry toolchain as built your StrawberryPerl-5.32.1.
If the same fix were to take care of your issue, then the Socket module remains unaltered, and you just need to create a PR that appropriately amends the perl source files win32/config.gc and win32/config_H.gc.

The proposal in that "recent socket ticket" of mine is something I plan to implement during the perl-5.37 development cycle after 5.36.0 has been released.
If you have some feedback on that proposal, I'd love to hear it.

First fix I'll be nagging about immediately after the release of perl-5.36.0 will be in relation to https://github.com/Perl/perl5/issues/18911#issuecomment-1107197299.
This also involves an alteration to Socket.pm - albeit a fairly innocuous one that merely restricts a section of code to mingw runtime versions less than 9.
Any feedback on those proposals are also welcome.
(It's "innocuous" in that the current perl source won't even compile unless mingw runtime version is less than 9. Your StrawberryPerl-5.32.1 toolchain has runtime version 6; latest runtime version is 10. )

For anyone who wants to build perl using a mingw-w64 tool chain that is significantly more up to date than that offered by Strawberry Perl, go to https://winlibs.com.
For the 64-bit builds of perl I currently have https://github.com/brechtsanders/winlibs_mingw/releases/download/11.2.0-10.0.0-msvcrt-r1/winlibs-x86_64-posix-seh-gcc-11.2.0-mingw-w64msvcrt-10.0.0-r1.7z.
For the 32-bit builds of perl I currently have https://github.com/brechtsanders/winlibs_mingw/releases/download/11.2.0-10.0.0-msvcrt-r1/winlibs-i686-posix-dwarf-gcc-11.2.0-mingw-w64msvcrt-10.0.0-r1.7z.
But I see they've just released gcc-11.3.0 versions - to which I'll be switching later today.

Cheers,
Rob

In reply to Re^7: Socket::getaddrinfo and localized error messages on Windows by syphilis
in thread Socket::getaddrinfo and localized error messages on Windows by Yaribz

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.