Going through the Configure steps while building Perl on Debian (-Dprefix=/opt/perl-5.8.8), I'm hoping someone can explain or comment on few parts that I was unsure about, or that just seemed curious.
``Does your kernel have *secure* setuid scripts? [n]''
What does this mean? How do I discover if my OS supports these? How does this setting affect the resulting Perl?
``Installation prefix to use for add-on modules and utilities? (~name ok)
[/opt/perl-5.8.8]''
What modules/utils are being referred to here? I don't think it's for site_perl stuff, because that gets mentioned in the subsequent configuration question.
``Pathname where the public executables will reside? (~name ok)
[/opt/perl-5.8.8/bin]
Directory /opt/perl-5.8.8/bin doesn't exist. Use that name anyway? [n]''
I went to a different terminal window and created that bin directory, then continued on with the config. Is that the usual way this step goes? Seems odd that the default isn't just for the build to automatically create the necessary bin directory.
``You are using the GNU C Library version 2.3.6
nm probably won't work on the GNU C Library.''
Just curious about this one: why would nm have an issue with extracting symbols from the GNU C library?
Finally, during the ``make test'' stage, I noticed a number of tests that were skipped. Besides the win32, threading, and 64-bit ones (all unrelated to my platform/configuration), these juicy-looking ones turned up as being skipped:
lib/ExtUtils/t/xs.........................skipping test on this platform
lib/Net/Ping/t/200_ping_tcp...............skipping test on this platform
lib/Net/Ping/t/250_ping_hires.............skipping test on this platform
lib/Net/Ping/t/300_ping_stream............skipping test on this platform
lib/Net/Ping/t/400_ping_syn...............skipping test on this platform
lib/Net/Ping/t/410_syn_host...............skipping test on this platform
lib/Net/t/ftp.............................skipping test on this platform
lib/Net/t/nntp............................skipping test on this platform
lib/Net/t/smtp............................skipping test on this platform
lib/Test/Harness/t/nonumbers..............skipping test on this platform
lib/Test/Harness/t/pod....................skipping test on this platform
lib/Test/Harness/t/prove-globbing.........skipping test on this platform
lib/Test/Harness/t/prove-switches.........skipping test on this platform
Should any of those be ringing a missing dependencies bell?