Any more suggestions?

In my version of Strawberry, when I build IO-React-1.03, there's no problem.
When I look at the generated Makefile I see:
DIRFILESEP = \\ DFSEP = $(DIRFILESEP)
Next I open up lib/ExtUtils/MM_Win32.pm and I find in it:
sub init_DIRFILESEP { my($self) = shift; # The ^ makes sure its not interpreted as an escape in nmake $self->{DIRFILESEP} = $self->is_make_type('nmake') ? '^\\' : $self->is_make_type('dmake') ? '\\\\' : '\\'; }
So I change the dmake setting (from 4 backslashes to 2) so that the sub now reads:
sub init_DIRFILESEP { my($self) = shift; # The ^ makes sure its not interpreted as an escape in nmake $self->{DIRFILESEP} = $self->is_make_type('nmake') ? '^\\' : $self->is_make_type('dmake') ? '\\' : '\\'; }
Now ... have another go at building IO-React-1.03 (having first run 'dmake realclean'):
C:\sisyphusion\IO-React-1.03>perl makefile.PL Checking if your kit is complete... Looks good Writing Makefile for IO::React Writing MYMETA.yml and MYMETA.json C:\sisyphusion\IO-React-1.03>dmake dmake: Error: -- `C:\_32\strawberry514\perl\libConfig.pm' not found, +and can't be made
Sure enough, when I look at the generated Makefile, I now find it's the same as yours wrt DIRFILESEP:
DIRFILESEP = \ DFSEP = $(DIRFILESEP)
Your generated Makefile is wrong ... plain and simple ... you need to remedy whatever it is that keeps generating this fucked Makefile.

In the above MM_Win32.pm sub, does $self->is_make_type('dmake') return true for you ?
In essence, you just need to modify that sub so that it returns \\\\ (4 backslashes) for you. Even if you just do it as:
sub init_DIRFILESEP { return '\\\\'; }
That should do it.

Cheers,
Rob

In reply to Re^6: Strawberry Perl 5.12.3, CPAN, make file problems (dmake.exe), DFSEP and backslash "\" by syphilis
in thread Strawberry Perl 5.12.3, CPAN, make file problems (dmake.exe), DFSEP and backslash "\" by jffry

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.