Re: MSVC build test results

[J. Grant]

Hi Paul,

[...]
> Maybe Perl is noticing that the arguments are empty and so isn't failing
> like it should.  Try this:
>
>   perl -e 'if (eval { symlink("foo","bar"); 1 }) { print "symlinks ok\n"; }'
>
> and see what it says then.  If it says "symlinks ok", look in the
> directory to see if any files (or whatever!) named "foo" or "bar" have
> been created.

address@hidden ~
$ perl -e 'if (eval { symlink("foo","bar"); 1 }) { print "symlinks 
ok\n"; }'
symlinks ok

>   jg> I have ran through all the tests and zipped up the results:
>
> Was this with the very latest CVS code, downloaded recently (within the
> last few days)?

Yep, I did it 24hrs ago, and did "cvs update" before I did the tests, 
and there had been no changes since my last "cvs co make" the day before 
that.

> Because, I tried to fix the cwd problem by adding code to use the
> POSIX::getwd() function in Perl.
>
> If it IS the latest CVS code, please try this and see that it says:
>
>   perl -e 'require "POSIX.pm"; my $cwd = POSIX::getcwd(); print "cwd = $cwd\n"'

address@hidden ~
$ perl -e 'require "POSIX.pm"; my $cwd = POSIX::getcwd(); print "cwd = 
$cwd\n"'
cwd = /home/now3d

address@hidden ~
$

I guess this problem is because of the mix between MinGW/MSVC build and 
MSYS unix wrapping shell stuff.

Any suggestions Earnie?

Kind regards
JG