From 6d8f7c99d6105c3e91ba7907750682703fe0414b Mon Sep 17 00:00:00 2001 From: Jan Dubois Date: Wed, 21 Jul 2010 18:00:07 -0700 Subject: Get rid of obsolete PerlCRT.dll support PerlCRT.dll was a patched version of MSVCRT.dll that fixed/worked around a few known issues with Microsoft's C runtime library. These issues have long been fixed by updates to MSVCRT.dll, and AFAIK nobody has used PerlCRT.dll in almost 10 years now. --- pod/perlxstut.pod | 8 -------- 1 file changed, 8 deletions(-) (limited to 'pod/perlxstut.pod') diff --git a/pod/perlxstut.pod b/pod/perlxstut.pod index 62bef3b0c5..de5b32a512 100644 --- a/pod/perlxstut.pod +++ b/pod/perlxstut.pod @@ -198,14 +198,6 @@ been deleted): You can safely ignore the line about "prototyping behavior" - it is explained in L. -If you are on a Win32 system, and the build process fails with linker -errors for functions in the C library, check if your Perl is configured -to use PerlCRT (running B should show you if this is the -case). If Perl is configured to use PerlCRT, you have to make sure -PerlCRT.lib is copied to the same location that msvcrt.lib lives in, -so that the compiler can find it on its own. msvcrt.lib is usually -found in the Visual C compiler's lib directory (e.g. C:/DevStudio/VC/lib). - Perl has its own special way of easily writing test scripts, but for this example only, we'll create our own test script. Create a file called hello that looks like this: -- cgit v1.2.1