diff options
author | Gurusamy Sarathy <gsar@cpan.org> | 2000-01-10 05:11:03 +0000 |
---|---|---|
committer | Gurusamy Sarathy <gsar@cpan.org> | 2000-01-10 05:11:03 +0000 |
commit | 5a3e78123e3b27b54e7f651bd5fa051044f04189 (patch) | |
tree | 03ec8fde909443adba0cc1bb6d9e0412d6824207 /pod/perlxstut.pod | |
parent | bed74ed023e76af1d7db4934c366decdfe105c17 (diff) | |
download | perl-5a3e78123e3b27b54e7f651bd5fa051044f04189.tar.gz |
pod typos (from Abigail <abigail@delanet.com>)
p4raw-id: //depot/perl@4781
Diffstat (limited to 'pod/perlxstut.pod')
-rw-r--r-- | pod/perlxstut.pod | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/pod/perlxstut.pod b/pod/perlxstut.pod index 8a96c891fc..35edd05ac0 100644 --- a/pod/perlxstut.pod +++ b/pod/perlxstut.pod @@ -24,7 +24,7 @@ them. If you find something that was missed, please let me know. This tutorial assumes that the make program that Perl is configured to use is called C<make>. Instead of running "make" in the examples that follow, you may have to substitute whatever make program Perl has been -configured to use. Running "perl -V:make" should tell you what it is. +configured to use. Running B<perl -V:make> should tell you what it is. =head2 Version caveat @@ -190,7 +190,7 @@ You can safely ignore the line about "prototyping behavior". 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 "perl -V:libc" should show you if this is the +to use PerlCRT (running B<perl -V:libc> 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 |