I'd be happy to try out a work in progress, btw.

I'd be happy to try out a work in progress, btw.

https://github.com/MasterDuke17/MoarVM/tree/use_more_libuv_dir_functions is what I have so far, but I just realized it also needs some work because '.' and '..' are handled differently. But it's probably fine for testing if large paths can in fact be create on Windows.

Build error on windows:

linking 3rdparty\libuv\uv.lib
linking moar.dll
   Creating library moar.dll.lib and object moar.dll.exp
dirops.obj : error LNK2001: unresolved external symbol S_ISDIR
moar.dll : fatal error LNK1120: 1 unresolved externals

which only appears here:

$ grep -r S_ISDIR
3rdparty/libuv/src/unix/fs.c:    if (rc == 0 && S_ISDIR(buf.st_mode)) {

Found https://www.davekb.com/browse_programming_tips:windows_isreg_isdir:txt

Maybe the issue is: why am I linking against unix/fs.c and not win/fs.c ?

Maybe the issue is: why am I linking against unix/fs.c and not win/fs.c ?

Oh - S_ISDIR is also in the new code, that's why I'm getting the error. I had a "moarvm-md" and a "moar-md" folder next to each other and was looking in one on git bash and the other on cmd and confused myself.

So, yes, the link with suggested implementation of S_ISDIR on windows is probably the way to go.

I locally added in the defines from the link above.

One the one hand, I'm able to build, but the rakudo install fails with:

+++ Preparing installation
NMAKE : fatal error U1077: 'C:\sandbox\rakudo-md\rakudo-m.exe' : return code '0xc0000005'
Stop.

On the other hand, rakudo-m.exe was installed, and I can run it. (e.g. -e "say 3" works)

On the gripping hand, when I run rakudo-m.exe on my failing test script, I get a segfault.

I went back and did a debug build (--debug on the MoarVM config), but VS is only showing me assembly, not C code, so I have no idea what the problem is.

@coke my most recent updates to https://github.com/MasterDuke17/MoarVM/tree/use_more_libuv_dir_functions (I force pushed, so you'll probably have to git reset --hard) should let you test creating a long dir. It annoyingly still segfaults when reading a dir, but it might let us know if this will in fact help once completed.