Can you show us the output of perlbug or perl -V? It includes all information that's needed on how you compiled Perl.

I'm not surprised that ../cpan/IPC-SysV/ tests fail, as most likely the Unix subsystem doesn't really have SysV IPC and maybe needs some better skipping logic in its tests.

Net::Ping failing is a tiny bit surprising, but maybe it needs root permissions in the WSL system and its detection goes wrong on whether it is root or not.

Can you also show the detailed output of a failing (socket) test? Run it maybe as

/path/to/hollis/fresh/bin/perl t/socket.t

[download]

In reply to Re: Compiling Perl using Win10 Subsystem for Linux (WSL) by Corion
in thread Compiling Perl using Win10 Subsystem for Linux (WSL) by holli

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.