diff options
author | Karl Williamson <khw@cpan.org> | 2016-04-22 13:00:22 -0600 |
---|---|---|
committer | Karl Williamson <khw@cpan.org> | 2016-04-22 13:08:10 -0600 |
commit | a95b3d6ada665e29ff33e3063306726e5ec40338 (patch) | |
tree | 07b90150d67aff5172c2681c07da6b74e0ae955a /INSTALL | |
parent | 319b236e2ed58e5be687a549dd0b94342cacd751 (diff) | |
download | perl-a95b3d6ada665e29ff33e3063306726e5ec40338.tar.gz |
Fix some pod errors
These were discovered while testing the Pod::Checker that is intended to
be used in 5.25.
Diffstat (limited to 'INSTALL')
-rw-r--r-- | INSTALL | 10 |
1 files changed, 5 insertions, 5 deletions
@@ -1922,11 +1922,11 @@ specify which target environment to use, as well as C<ar> and friends: Additionally, a cross-compilation toolchain will usually install it's own logical system root somewhere -- that is, it'll create a directory -somewhere which includes subdirectories like 'include' or 'lib'. For -example, you may end up with C</skiff/local/arm-linux>, where -C</skiff/local/arm-linux/bin> holds the binaries for cross-compilation, -C</skiff/local/arm-linux/include> has the headers, and -C</skiff/local/arm-linux/lib> has the library files. +somewhere which includes subdirectories like C<'include'> or C<'lib'>. For +example, you may end up with F</skiff/local/arm-linux>, where +F</skiff/local/arm-linux/bin> holds the binaries for cross-compilation, +F</skiff/local/arm-linux/include> has the headers, and +F</skiff/local/arm-linux/lib> has the library files. If this is the case, and you are using a compiler that understands C<--sysroot>, like gcc or clang, you'll want to specify the C<-Dsysroot> option for Configure: |