Beginning of configuration questions for perl5. Checking echo to see how to suppress newlines... ...using -n. The star should be here-->* First let's make sure your kit is complete. Checking... Looks good... Would you like to see the instructions? [n] Locating common programs... awk is in /usr/bin/awk. cat is in /bin/cat. comm is in /usr/bin/comm. cp is in /bin/cp. echo is in /bin/echo. expr is in /usr/bin/expr. grep is in /usr/bin/grep. ls is in /bin/ls. make is in /usr/bin/make. mkdir is in /bin/mkdir. rm is in /bin/rm. sed is in /usr/bin/sed. sort is in /usr/bin/sort. touch is in /bin/touch. tr is in /usr/bin/tr. uniq is in /usr/bin/uniq. Don't worry if any of the following aren't found... I don't see Mcc out there, offhand. ar is in /usr/bin/ar. bison is in /usr/bin/bison. I don't see byacc out there, either. cpp is in /usr/bin/cpp. csh is in /bin/csh. date is in /bin/date. egrep is in /usr/bin/egrep. gzip is in /bin/gzip. less is in /usr/bin/less. ln is in /bin/ln. more is in /bin/more. nm is in /usr/bin/nm. nroff is in /usr/bin/nroff. I don't see pg out there, either. test is in /usr/bin/test. uname is in /bin/uname. zip is in /usr/bin/zip. Using the test built into your sh. Using the test built into your sh. Checking compatibility between /bin/echo and builtin echo (if any)... They are compatible. In fact, they may be identical. Symbolic links are supported. Checking how to test for symbolic links... You can test for symbolic links with 'test -h'. Good, your tr supports [:lower:] and [:upper:] to convert case. Using [:upper:] and [:lower:] to convert case. First time through, eh? I have some defaults handy for some systems that need some extra help getting the Configure answers right: 3b1 dynix isc nonstopux stellar aix dynixptx isc_2 openbsd sunos_4_0 altos486 epix linux opus sunos_4_1 amigaos esix4 lynxos os2 svr4 apollo fps machten os390 svr5 aux_3 freebsd machten_2 posix-bc ti1500 beos genix mint powerux titanos bsdos gnu mips qnx ultrix_4 convexos greenhills mpc rhapsody umips cxux hpux mpeix sco unicos cygwin i386 ncr_tower sco_2_3_0 unicosmk darwin irix_4 netbsd sco_2_3_1 unisysdynix dcosx irix_5 newsos4 sco_2_3_2 utekv dec_osf irix_6 next_3 sco_2_3_3 uts dgux irix_6_0 next_3_0 sco_2_3_4 uwin dos_djgpp irix_6_1 next_4 solaris_2 vmesa You may give one or more space-separated answers, or "none" if appropriate. A well-behaved OS will have no hints, so answering "none" or just "Policy" is a good thing. DO NOT give a wrong version or a wrong OS. Which of these apply, if any? [linux] You appear to have ELF support. I'll try to use it for dynamic loading. If dynamic loading doesn't work, read hints/linux.sh for further information. You appear to have a working bash. Good. Your csh is really tcsh. Good. Configure uses the operating system name and version to set some defaults. The default value is probably right if the name rings a bell. Otherwise, since spelling matters for me, either accept the default or answer "none" to leave it blank. Operating system name? [linux] Operating system version? [2.4.18] Perl can be built to take advantage of threads on some systems. To do so, Configure can be run with -Dusethreads. Note that threading is a highly experimental feature, and some known race conditions still remain. If you choose to try it, be very sure to not actually deploy it for production purposes. README.threads has more details, and is required reading if you enable threads. If this doesn't make any sense to you, just accept the default 'n'. Build a threading Perl? [n] Perl can be built so that multiple Perl interpreters can coexist within the same Perl executable. If this doesn't make any sense to you, just accept the default 'n'. Build Perl for multiplicity? [n] Hmm... Looks kind of like a Version 7 system, but we'll see... Congratulations. You aren't running Eunice. It's not Xenix... Nor is it Venix... Use which C compiler? [cc] Checking for GNU cc in disguise and/or its version number... You are using GNU cc 2.95.3 20010315 (release). Now, how can we feed standard input to your C preprocessor... Maybe "gcc -E" will work... Nope...maybe "gcc -E -" will work... Yup, it does. Hmm... Doesn't look like a MIPS system. Some systems have incompatible or broken versions of libraries. Among the directories listed in the question below, please remove any you know not to be holding relevant libraries, and add any that are needed. Say "none" for none. Directories to use for library searches? [/usr/local/lib /lib /usr/lib] On some systems, shared libraries may be available. Answer 'none' if you want to suppress searching of shared libraries for the remainder of this configuration. What is the file extension used for shared libraries? [so] Perl can be built to use the SOCKS proxy protocol library. To do so, Configure must be run with -Dusesocks. If this doesn't make any sense to you, just accept the default 'n'. Build Perl for SOCKS? [n] Checking for optional libraries... No -lsfio. No -lsocket. No -lbind. No -linet. Found -lnsl (shared). No -lnm. No -lndbm. Found -lgdbm (shared). No -ldbm. Found -ldb. No -lmalloc. Found -ldl (shared). No -ldld. No -lld. No -lsun. Found -lm (shared). Found -lc (shared). No -lcposix. No -lposix. No -lndir. No -ldir. Found -lcrypt (shared). No -lsec. No -lucb. No -lBSD. No -lPW. No -lx. No -liconv. Found -lutil (shared). In order to compile perl5 on your machine, a number of libraries are usually needed. Include any other special libraries here as well. Say "none" for none. The default list is almost always right. What libraries to use? [-lnsl -lgdbm -ldb -ldl -lm -lc -lcrypt -lutil] By default, perl5 compiles with the -O flag to use the optimizer. Alternately, you might want to use the symbolic debugger, which uses the -g flag (on traditional Unix systems). Either flag can be specified here. To use neither flag, specify the word "none". What optimizer/debugger flag should be used? [-O2] Checking if your compiler accepts -fno-strict-aliasing Yes, it does. Your C compiler may want other flags. For this question you should include -I/whatever and -DWHATEVER flags and any other flags used by the C compiler, but you should NOT include libraries or ld flags like -lwhatever. If you want perl5 to honor its debug switch, you should include -DDEBUGGING here. Your C compiler might also need additional flags, such as -D_POSIX_SOURCE. To use no flags, specify the word "none". Any additional cc flags? [-fno-strict-aliasing -I/usr/local/include] Let me guess what the preprocessor flags are... They appear to be: -fno-strict-aliasing -I/usr/local/include Your C linker may need flags. For this question you should include -L/whatever and any other flags used by the C linker, but you should NOT include libraries like -lwhatever. Make sure you include the appropriate -L/path flags if your C linker does not normally search all of the directories you specified above, namely /usr/local/lib /lib /usr/lib To use no flags, specify the word "none". Any additional ld flags (NOT including libraries)? [ -L/usr/local/lib] Checking your choice of C compiler and flags for coherency... OK, that should do. Checking to see how big your integers are... Your integers are 4 bytes long. Your long integers are 4 bytes long. Your short integers are 2 bytes long. Looking for the type used for lseek's offset on this system. off_t found. Checking to see how big your file offsets are... Your file offsets are 4 bytes long. Looking for the type for file position used by fsetpos(). fpos_t found. Checking the size of fpos_t... Your fpos_t is 12 bytes long. Perl can be built to understand large files (files larger than 2 gigabytes) on some systems. To do so, Configure can be run with -Duselargefiles. If this doesn't make any sense to you, just accept the default 'y'. Try to understand large files, if available? [y] Your platform has some specific hints for large file builds, using them... Rechecking to see how big your file offsets are... Your file offsets are now 8 bytes long. Rechecking the size of fpos_t... 16 bytes. Perl can be built to take advantage of 64-bit integer types on some systems. To do so, Configure can be run with -Duse64bitint. Choosing this option will most probably introduce binary incompatibilities. If this doesn't make any sense to you, just accept the default 'n'. Try to use 64-bit integers, if available? [n] You may also choose to try maximal 64-bitness. It means using as much 64-bitness as possible on the platform. This in turn means even more binary incompatibilities. On the other hand, your platform may not have any more 64-bitness available than what you already have chosen. If this doesn't make any sense to you, just accept the default 'n'. Try to use maximal 64-bit support, if available? [n] Checking for GNU C Library... You are using the GNU C Library nm probably won't work on the GNU C Library. I can use /usr/bin/nm to extract the symbols from your C libraries. This is a time consuming task which may generate huge output on the disk (up to 3 megabytes) but that should make the symbols extraction faster. The alternative is to skip the 'nm' extraction part and to compile a small test program instead to determine whether each symbol is present. If you have a fast C compiler and/or if your 'nm' output cannot be parsed, this may be the best solution. You probably shouldn't let me use 'nm' if you are using the GNU C Library. Shall I use /usr/bin/nm to extract C symbols from the libraries? [n] sqrtl() found. Perl can be built to take advantage of long doubles which (if available) may give more accuracy and range for floating point numbers. If this doesn't make any sense to you, just accept the default 'n'. Try to use long doubles if available? [n] Checking to see how big your double precision numbers are... Your double is 8 bytes long. Checking to see if you have long double... You have long double. Checking to see how big your long doubles are... Your long doubles are 12 bytes long. What is your architecture name [i686-linux] Multiplicity selected. ...setting architecture name to i686-linux-multi. By default, perl5 will be installed in /usr/local/bin, manual pages under /usr/local/man, etc..., i.e. with /usr/local as prefix for all installation directories. Typically this is something like /usr/local. If you wish to have binaries under /usr/bin but other parts of the installation under /usr/local, that's ok: you will be prompted separately for each of the installation directories, the prefix being only used to set the defaults. Installation prefix to use? (~name ok) [/usr/local] AFS does not seem to be running... In some special cases, particularly when building perl5 for distribution, it is convenient to distinguish between the directory in which files should be installed from the directory (/usr) in which they will eventually reside. For most users, these two directories are the same. What installation prefix should I use for installing files? (~name ok) [/usr] Getting the current patchlevel... (You have perl5 version 6 subversion 1.) There are some auxiliary files for perl5 that need to be put into a private library directory that is accessible by everyone. Pathname where the private library files will reside? (~name ok) [/usr/lib/perl5/5.6.1] Perl5 contains architecture-dependent library files. If you are sharing libraries in a heterogeneous environment, you might store these files in a separate location. Otherwise, you can just include them with the rest of the public library files. Where do you want to put the public architecture-dependent libraries? (~name ok) [/usr/lib/perl5/5.6.1/i686-linux-multi] Some kernels have a bug that prevents setuid #! scripts from being secure. Some sites have disabled setuid #! scripts because of this. First let's decide if your kernel supports secure setuid #! scripts. (If setuid #! scripts would be secure but have been disabled anyway, don't say that they are secure if asked.) If you are not sure if they are secure, I can check but I'll need a username and password different from the one you are using right now. If you don't have such a username or don't want me to test, simply enter 'none'. Other username to test security of setuid scripts with? [none] Well, the recommended value is *not* secure. Does your kernel have *secure* setuid scripts? [n] Some systems have disabled setuid scripts, especially systems where setuid scripts cannot be secure. On systems where setuid scripts have been disabled, the setuid/setgid bits on scripts are currently useless. It is possible for perl5 to detect those bits and emulate setuid/setgid in a secure fashion. This emulation will only work if setuid scripts have been disabled in your kernel. Do you want to do setuid/setgid emulation? [n] Computing filename position in cpp output for #include directives... Your cpp writes the filename in the third field of the line. found. found. Do you wish to attempt to use the malloc that comes with perl5? [n] Your system wants malloc to return 'void *', it would seem. Your system uses void free(), it would seem. After perl5 is installed, you may wish to install various add-on modules and utilities. Typically, these add-ons will be installed under /usr with the rest of this package. However, you may wish to install such add-ons elsewhere under a different prefix. If you do not wish to put everything under a single prefix, that's ok. You will be prompted for the individual locations; this siteprefix is only used to suggest the defaults. The default should be fine for most people. Installation prefix to use for add-on modules and utilities? (~name ok) [/usr] The installation process will create a directory for site-specific extensions and modules. Most users find it convenient to place all site-specific files in this directory rather than in the main distribution directory. Pathname for the site-specific library files? (~name ok) [/usr/lib/perl5/site_perl/5.6.1] The installation process will also create a directory for architecture-dependent site-specific extensions and modules. Pathname for the site-specific architecture-dependent library files? (~name ok) [/usr/lib/perl5/site_perl/5.6.1/i686-linux-multi] The installation process will also create a directory for vendor-supplied add-ons. Vendors who supply perl with their system may find it convenient to place all vendor-supplied files in this directory rather than in the main distribution directory. This will ease upgrades between binary-compatible maintenance versions of perl. Of course you may also use these directories in whatever way you see fit. For example, you might use them to access modules shared over a company-wide network. The default answer should be fine for most people. This causes further questions about vendor add-ons to be skipped and no vendor-specific directories will be configured for perl. Do you want to configure vendor-specific add-on directories? [n] Lastly, you can have perl look in other directories for extensions and modules in addition to those already specified. These directories will be searched after /usr/lib/perl5/site_perl/5.6.1/i686-linux-multi /usr/lib/perl5/site_perl/5.6.1 Enter a colon-separated set of extra paths to include in perl's @INC search path, or enter 'none' for no extra paths. Colon-separated list of additional directories for perl to search? [none] Checking out function prototypes... Your C compiler appears to support function prototypes. Pathname where the public executables will reside? (~name ok) [/usr/bin] Looking for a previously installed perl5.005 or later... Using /usr/bin/perl. In order to ease the process of upgrading, this version of perl can be configured to use modules built and installed with earlier versions of perl that were installed under $prefix. Specify here the list of earlier versions that this version of perl should check. If Configure detected no earlier versions of perl installed under $prefix, then the list will be empty. Answer 'none' to tell perl to not search earlier versions. The default should almost always be sensible, so if you're not sure, just accept the default. List of earlier versions to include in @INC? [none] NOT found. dlopen() found. Do you wish to use dynamic loading? [y] The following dynamic loading files are available: ext/DynaLoader/dl_aix.xs ext/DynaLoader/dl_mac.xs ext/DynaLoader/dl_beos.xs ext/DynaLoader/dl_mpeix.xs ext/DynaLoader/dl_dld.xs ext/DynaLoader/dl_next.xs ext/DynaLoader/dl_dllload.xs ext/DynaLoader/dl_none.xs ext/DynaLoader/dl_dlopen.xs ext/DynaLoader/dl_vmesa.xs ext/DynaLoader/dl_dyld.xs ext/DynaLoader/dl_vms.xs ext/DynaLoader/dl_hpux.xs Source file to use for dynamic loading [ext/DynaLoader/dl_dlopen.xs] Some systems may require passing special flags to gcc -c to compile modules that will be used to create a shared library. To use no flags, say "none". Any special flags to pass to gcc -c to compile shared library modules? [-fpic] Some systems use ld to create libraries that can be dynamically loaded, while other systems (such as those using ELF) use gcc. You appear to have ELF support. I'll use gcc to build dynamic libraries. What command should be used to create dynamic libraries? [gcc] Some systems may require passing special flags to gcc to create a library that can be dynamically loaded. If your ld flags include -L/other/path options to locate libraries outside your loader's normal search path, you may need to specify those -L options here as well. To use no flags, say "none". Any special flags to pass to gcc to create a dynamically loaded library? [-shared -L/usr/local/lib] Some systems may require passing special flags to gcc to indicate that the resulting executable will use dynamic linking. To use no flags, say "none". Any special flags to pass to gcc to use dynamic linking? [-rdynamic] The perl executable is normally obtained by linking perlmain.c with libperl.a, any static extensions (usually just DynaLoader), and any other libraries needed on this system (such as -lm, etc.). Since your system supports dynamic loading, it is probably possible to build a shared libperl.so. If you will have more than one executable linked to libperl.so, this will significantly reduce the size of each executable, but it may have a noticeable affect on performance. The default is probably sensible for your system. Build a shared libperl.so (y/n) [n] I need to select a good name for the shared libperl. If your system uses library names with major and minor numbers, then you might want something like libperl.so.6.1. Alternatively, if your system uses a single version number for shared libraries, then you might want to use libperl.so.601. Or, your system might be quite happy with a simple libperl.so. Since the shared libperl will get installed into a version-specific architecture-dependent directory, the version number of the shared perl library probably isn't important, so the default should be o.k. What name do you want to give to the shared libperl? [libperl.so] Ok, I'll use libperl.so Adding -Wl,-rpath,/usr/lib/perl5/5.6.1/i686-linux-multi/CORE to the flags passed to gcc so that the perl executable will find the installed shared libperl.so. System manual is in /usr/man/man1. Perl5 has manual pages available in source form. If you don't want the manual sources installed, answer 'none'. Where do the main Perl5 manual pages (source) go? (~name ok) [/usr/man/man1] What suffix should be used for the main Perl5 man pages? [1] You can have filenames longer than 14 characters. Perl5 has manual pages for many of the library modules. If you don't want the manual sources installed, answer 'none'. Where do the perl5 library man pages (source) go? (~name ok) [/usr/man/man3] What suffix should be used for the perl5 library man pages? [3] Figuring out host name... Maybe "hostname" will work... Your host name appears to be "typhoon". Right? [y] What is your domain name? [.rider.gr.jp] I need to get your e-mail address in Internet format if possible, i.e. something like user@host.domain. Please answer accurately since I have no easy means to double check it. The default value provided below is most probably close to reality but may not be valid from outside your organization... What is your e-mail address? [kojima@typhoon.linet.gr.jp] If you or somebody else will be maintaining perl at your site, please fill in the correct e-mail address here so that they may be contacted if necessary. Currently, the "perlbug" program included with perl will send mail to this address in addition to perlbug@perl.org. You may enter "none" for no administrator. Perl administrator e-mail address [kojima@linet.gr.jp] Do you want to install only the version-specific parts of the perl distribution? Usually you do *not* want to do this. Do you want to install only the version-specific parts of perl? [n] I can use the #! construct to start perl on your system. This will make startup of perl scripts faster, but may cause problems if you want to share those scripts and perl is not in a standard place (/usr/bin/perl) on all your platforms. The alternative is to force a shell by starting the script with a single ':' character. What shall I put after the #! to start up perl ("none" to not use #!)? [/usr/bin/perl] I'll use #!/usr/bin/perl to start perl scripts. Some installations have a separate directory just for executable scripts so that they can mount it across multiple architectures but keep the scripts in one spot. You might, for example, have a subdirectory of /usr/share for this. Or you might just lump your scripts in with all your other executables. Where do you keep publicly executable scripts? (~name ok) [/usr/bin] Pathname where the add-on public executables should be installed? (~name ok) [/usr/bin] Previous version of perl5 used the standard IO mechanisms as defined in . Versions 5.003_02 and later of perl allow alternate IO mechanisms via a "PerlIO" abstraction, but the stdio mechanism is still the default. This abstraction layer can use AT&T's sfio (if you already have sfio installed) or regular stdio. Using PerlIO with sfio may cause problems with some extension modules. Using PerlIO with stdio is safe, but it is slower than plain stdio and therefore is not the default. If this doesn't make any sense to you, just accept the default 'n'. Use the experimental PerlIO abstraction layer? [n] Ok, doing things the stdio way qgcvt() found. Checking how to print long doubles... We will use %llf. Checking for an efficient way to convert floats to strings. Trying gconvert... gconvert NOT found. Trying gcvt... gcvt() found. I'll use gcvt to convert floats into a string. fwalk() NOT found. access() found. defines the *_OK access constants. accessx() NOT found. alarm() found. atolf() NOT found. atoll() found. Checking whether your compiler can handle __attribute__ ... Your C compiler supports __attribute__. bcmp() found. bcopy() found. found. getpgrp() found. Checking to see which flavor of getpgrp is in use... You have to use getpgrp() instead of getpgrp(pid). setpgrp() found. Checking to see which flavor of setpgrp is in use... You have to use setpgrp() instead of setpgrp(pid,pgrp). bzero() found. You have void (*signal())(). Checking whether your C compiler can cast large floats to int32. Nope, it can't. Checking whether your C compiler can cast negative float to unsigned. Yup, it can. vprintf() found. Your vsprintf() returns (int). chown() found. chroot() found. chsize() NOT found. Checking to see if your C compiler knows about "const"... Yup, it does. crypt() found. cuserid() found. found. found. DBL_DIG found. difftime() found. found. Your directory entries are struct dirent. Your directory entry does not know about the d_namlen field. dlerror() found. found. On a few systems, the dynamically loaded modules that perl generates and uses will need a different extension than shared libs. The default will probably be appropriate. What is the extension of dynamically loaded modules [so] Checking whether your dlsym() needs a leading underscore ... dlsym doesn't need a leading underscore. drand48() prototype found. dup2() found. eaccess() NOT found. endgrent() found. endhostent() found. endnetent() found. endprotoent() found. endpwent() found. endservent() found. defines the O_* constants... and you have the 3 argument form of open(). Using instead of . Figuring out the flag used by open() for non-blocking I/O... Seems like we can use O_NONBLOCK. Let's see what value errno gets from read() on a O_NONBLOCK file... A read() system call with no data present returns -1. Your read() sets errno to EAGAIN when no data is available. And it correctly returns 0 to signal EOF. fchmod() found. fchown() found. fcntl() found. Checking if fcntl-based file locking works... Yes, it seems to work. Hmm... Looks like you have Berkeley networking support. socketpair() found. Checking the availability of certain socket constants... found. Testing to see if we should include , or both. I'm now running the test program...... Succeeded with -DI_TIME -DI_SYSTIME -DS_TIMEVAL We'll include . We'll include . Checking to see how well your C compiler handles fd_set and friends ... Hmm, your compiler has some difficulty with fd_set. Checking further... Well, your system has some sort of fd_set available... and you have the normal fd_set macros. fgetpos() found. flock() found. fork() found. pathconf() found. fpathconf() found. Checking to see if you have fpos64_t... You do not have fpos64_t. frexpl() found. found. found. found. Checking to see if your system supports struct fs_data... No, it doesn't. fseeko() found. fsetpos() found. fstatfs() found. statvfs() found. fstatvfs() found. fsync() found. ftello() found. getcwd() found. getespwnam() NOT found. getfsstat() NOT found. getgrent() found. gethostbyaddr() found. gethostbyname() found. gethostent() found. gethostname() found. uname() found. Every now and then someone has a gethostname() that lies about the hostname but can't be fixed for political or economic reasons. If you wish, I can pretend gethostname() isn't there and maybe compute hostname at run-time thanks to the 'hostname' command. Shall I ignore gethostname() from now on? [n] found. gethostent() prototype found. getlogin() found. getmnt() NOT found. getmntent() found. getnetbyaddr() found. getnetbyname() found. getnetent() found. getnetent() prototype found. getpagesize() found. getprotobyname() found. getprotobynumber() found. getprotoent() found. getpgid() found. getpgrp2() NOT found. getppid() found. getpriority() found. getprotoent() prototype found. getprpwnam() NOT found. getpwent() found. getservbyname() found. getservbyport() found. getservent() found. getservent() prototype found. getspnam() found. gettimeofday() found. found. hasmntopt() found. found. found. htonl() found. iconv() found. strchr() found. inet_aton() found. found. Checking to see if you have int64_t... You have int64_t. isascii() found. isnan() found. isnanl() found. killpg() found. lchown() found. LDBL_DIG found. link() found. localeconv() found. lockf() found. Checking to see if you have long long... You have long long. Checking to see how big your long longs are... Your long longs are 8 bytes long. lseek() prototype found. lstat() found. madvise() found. mblen() found. mbstowcs() found. mbtowc() found. memchr() found. memcmp() found. memcpy() found. memmove() found. memset() found. mkdir() found. mkdtemp() found. mkfifo() found. mkstemp() found. mkstemps() NOT found. mktime() found. found. mmap() found. and it returns (void *). modfl() found. mprotect() found. msgctl() found. msgget() found. msgsnd() found. msgrcv() found. You have the full msg*(2) library. msync() found. munmap() found. nice() found. Checking which 64-bit integer type we could use... We could use 'long long' for 64-bit integers. Checking to see how big your characters are (hey, you never know)... What is the size of a character (in bytes)? [1] Checking to see if your C compiler knows about "volatile"... Yup, it does. Choosing the C types to be used for Perl's internal types... (IV will be long, 4 bytes) (UV will be unsigned long, 4 bytes) (NV will be double, 8 bytes) Checking how many bits of your UVs your NVs can preserve... Your NVs can preserve all 32 bits of your UVs. Checking to see if you have off64_t... You do not have off64_t. (Your off_t is 64 bits, so you could use that.) found. pause() found. pipe() found. poll() found. found. readdir() found. seekdir() found. telldir() found. rewinddir() found. readlink() found. rename() found. rmdir() found. found. We won't be including . Checking to see if your bcopy() can do overlapping copies... Yes, it can. Checking to see if your memcpy() can do overlapping copies... It can't, sorry. But that's Ok since you have memmove(). Checking if your memcmp() can compare relative magnitude... Yes, it can. sbrk() prototype found. select() found. semctl() found. semget() found. semop() found. You have the full sem*(2) library. You do not have union semun in . You can use union semun for semctl IPC_STAT. You can also use struct semid_ds* for semctl IPC_STAT. setegid() found. seteuid() found. setgrent() found. sethostent() found. setlinebuf() found. setlocale() found. setnetent() found. setprotoent() found. setpgid() found. setpgrp2() NOT found. setpriority() found. setproctitle() NOT found. setpwent() found. setregid() found. setresgid() found. setreuid() found. setresuid() found. setrgid() NOT found. setruid() NOT found. setservent() found. setsid() found. setvbuf() found. NOT found. libs = -lnsl -lgdbm -ldb -ldl -lm -lc -lcrypt -lutil shmctl() found. shmget() found. shmat() found. and it returns (void *). shmdt() found. You have the full shm*(2) library. sigaction() found. POSIX sigsetjmp found. socks5_init() NOT found. found. Checking to see if your struct stat has st_blocks field... found. found. Checking to see if your system supports struct statfs... Yes, it does. Checking to see if your struct statfs has f_flags field... No, it doesn't. (Looks like you have stdio.h from Linux.) Checking how std your stdio is... Your stdio acts pretty std. Checking to see what happens if we set the stdio ptr... Increasing ptr in your stdio decreases cnt by the same amount. Good. And its _base field acts std. Checking how to access stdio streams by file descriptor number... I can't figure out how to access stdio streams by file descriptor number. strcoll() found. Checking to see if your C compiler can copy structs... Yup, it can. strerror() found. (You also have sys_errlist[], so we could roll our own strerror.) strtod() found. strtol() found. strtold() found. strtoll() found. Checking whether your strtoll() works okay... Your strtoll() seems to be working okay. strtoul() found. strtoull() found. Checking whether your strtoull() works okay... Your strtoull() seems to be working okay. strtouq() found. strxfrm() found. symlink() found. syscall() found. sysconf() found. system() found. tcgetpgrp() found. tcsetpgrp() found. telldir() prototype found. found. times() found. Looking for the type returned by times() on this system. clock_t found. truncate() found. tzname[] found. umask() found. ustat() found. vfork() found. Perl can only use a vfork() that doesn't suffer from strict restrictions on calling functions or modifying global data in the child. For example, glibc-2.1 contains such a vfork() that is unsuitable. If your system provides a proper fork() call, chances are that you do NOT want perl to use vfork(). Do you still want to use vfork()? [n] Ok, we won't use vfork(). found. NOT found. closedir() found. Checking whether closedir() returns a status... Yes, it does. wait4() found. waitpid() found. wcstombs() found. wctomb() found. Checking alignment constraints... Doubles must be aligned on a how-many-byte boundary? [4] In the following, larger digits indicate more significance. A big-endian machine like a Pyramid or a Motorola 680?0 chip will come out to 4321. A little-endian machine like a Vax or an Intel 80?86 chip would be 1234. Other machines may have weird orders like 3412. A Cray will report 87654321, an Alpha will report 12345678. If the test program works the default is probably right. I'm now running the test program... (The test program ran ok.) byteorder=1234 Checking to see how your cpp does stuff like catenate tokens... Oh! Smells like ANSI's been here. We can catify or stringify, separately or together! found. Checking Berkeley DB version ... You have Berkeley DB Version 2 or greater db.h is from Berkeley DB Version 3.2.9 libdb is from Berkeley DB Version 3.2.9 db.h and libdb are compatible Looks OK. Checking return type needed for hash for Berkeley DB ... Your version of Berkeley DB uses u_int32_t for hash. Checking return type needed for prefix for Berkeley DB ... Your version of Berkeley DB uses size_t for prefix. Checking to see how well your C compiler groks the void type... Good. It appears to support void to the level perl5 wants. Looking for a random number function... Good, found drand48(). Use which function to generate random numbers? [drand48] Determining whether or not we are on an EBCDIC system... Nope, no EBCDIC, probably ASCII or some ISO Latin. Or UTF8. Checking how to flush all pending stdio output... Your fflush(NULL) works okay for output streams. Let's see if it clobbers input pipes... fflush(NULL) seems to behave okay with input streams. Looking for the type for group ids returned by getgid(). gid_t found. Checking the size of gid_t... Your gid_t is 4 bytes long. Checking the sign of gid_t... Your gid_t is unsigned. Checking how to print 64-bit integers... We will use the %lld style. Checking the format strings to be used for Perl's internal types... Checking the format string to be used for gids... getgroups() found. setgroups() found. What type of pointer is the second argument to getgroups() and setgroups()? Usually this is the same as group ids, gid_t, but not always. What type pointer is the second argument to getgroups() and setgroups()? [gid_t] Checking if your /usr/bin/make program sets $(MAKE)... Yup, it does. Looking for the type used for file modes for system calls (e.g. fchmod()). mode_t found. Looking for the type used for the length parameter for string functions. size_t found. Checking to see what type of arguments are accepted by gethostbyaddr(). Your system accepts const void * for the first arg. ...and size_t for the second arg. Checking to see what type of argument is accepted by gethostbyname(). Your system accepts const char *. Checking to see what type of 1st argument is accepted by getnetbyaddr(). Your system accepts in_addr_t. What pager is used on your system? [/usr/bin/less] Looking for the type of process ids on this system. pid_t found. Checking to see how big your pointers are... Your pointers are 4 bytes long. Checking how to generate random libraries on your machine... /usr/bin/ar appears to generate random libraries itself. Checking to see what type of arguments are accepted by select(). Your system accepts fd_set *. Checking to see on how many bits at a time your select() operates... Your select() operates on 32 bits at a time. Generating a list of signal names and numbers... The following 64 signals are available: SIGZERO SIGHUP SIGINT SIGQUIT SIGILL SIGTRAP SIGABRT SIGBUS SIGFPE SIGKILL SIGUSR1 SIGSEGV SIGUSR2 SIGPIPE SIGALRM SIGTERM SIGSTKFLT SIGCHLD SIGCONT SIGSTOP SIGTSTP SIGTTIN SIGTTOU SIGURG SIGXCPU SIGXFSZ SIGVTALRM SIGPROF SIGWINCH SIGIO SIGPWR SIGSYS SIGRTMIN SIGNUM33 SIGNUM34 SIGNUM35 SIGNUM36 SIGNUM37 SIGNUM38 SIGNUM39 SIGNUM40 SIGNUM41 SIGNUM42 SIGNUM43 SIGNUM44 SIGNUM45 SIGNUM46 SIGNUM47 SIGNUM48 SIGNUM49 SIGNUM50 SIGNUM51 SIGNUM52 SIGNUM53 SIGNUM54 SIGNUM55 SIGNUM56 SIGNUM57 SIGNUM58 SIGNUM59 SIGNUM60 SIGNUM61 SIGNUM62 SIGRTMAX SIGIOT SIGCLD SIGPOLL SIGUNUSED Checking the size of size_t... Your size_t size is 4 bytes. Checking to see if you have socklen_t... You have socklen_t. NOT found. Checking to see what type is the last argument of accept(). Your system accepts 'socklen_t *' for the last argument of accept(). I'll be using ssize_t for functions returning a byte count. Your stdio uses signed chars. time() found. Looking for the type returned by time() on this system. time_t found. Looking for the type for user ids returned by getuid(). uid_t found. Checking the size of uid_t... Your uid_t is 4 bytes long. Checking the sign of uid_t... Your uid_t is unsigned. Checking the format string to be used for uids... Which compiler compiler (yacc or bison -y) shall I use? [yacc] dbmclose() found. NOT found. NOT found. found. We'll be including . found. We don't need to include if we include . found. NOT found. NOT found. found. found. found. NOT found. NOT found. found. found. NOT found. Guessing which symbols your C compiler and preprocessor define... Your C compiler and pre-processor define these symbols: __ELF__ __GNUC__ i386 linux unix Your C pre-processor also defines the following symbols: _FILE_OFFSET_BITS __GNUC_MINOR__ _LARGEFILE_SOURCE _POSIX_C_SOURCE _POSIX_SOURCE __STDC__ __i386 __i386__ __linux __linux__ __unix __unix__ Your C compiler further defines the following cpp symbols: __GNUC_MINOR__=95 __i386 __i386__ __linux __linux__ __unix __unix__ cpu=i386 machine=i386 system=posix tcsetattr() found. You have POSIX termios.h... good! found. found. found. We'll include to get va_dcl definition. found. NOT found. NOT found. NOT found. found. found. NOT found. found. NOT found. found. found. found. found. found. found. found. found. found. gdbm_open() found. Looking for extensions... A number of extensions are supplied with perl5. You may choose to compile these extensions for dynamic loading (the default), compile them into the perl5 executable (static loading), or not include them at all. Answer "none" to include no extensions. Note that DynaLoader is always built and need not be mentioned here. What extensions do you wish to load dynamically? [B ByteLoader DB_File Data/Dumper Devel/DProf Devel/Peek Fcntl File/Glob GDBM_File IO IPC/SysV Opcode POSIX SDBM_File Socket Sys/Hostname Sys/Syslog attrs re] What extensions do you wish to load statically? [none] End of configuration questions. Stripping down executable paths... Creating config.sh... If you'd like to make any changes to the config.sh file before I begin to configure things, do it as a shell escape now (e.g. !vi config.sh). Press return or use a shell escape to edit config.sh: Press return or use a shell escape to edit config.sh: Doing variable substitutions on .SH files... Extracting Makefile (with variable substitutions) Extracting Policy.sh (with variable substitutions) Extracting cflags (with variable substitutions) Extracting config.h (with variable substitutions) Extracting makeaperl (with variable substitutions) Extracting makedepend (with variable substitutions) Extracting makedir (with variable substitutions) Extracting myconfig (with variable substitutions) Extracting pod/Makefile (with variable substitutions) Extracting writemain (with variable substitutions) Extracting x2p/Makefile (with variable substitutions) Extracting x2p/cflags (with variable substitutions) Now you need to generate make dependencies by running "make depend". You might prefer to run it in background: "make depend > makedepend.out &" It can take a while, so you might not want to run it right now. Run make depend now? [y] sh ./makedepend MAKE=make make[1]: 入ります ディレクトリ `/home/kojima/perl-5.6.1' sh writemain lib/auto/DynaLoader/DynaLoader.a > writemain.tmp sh mv-if-diff writemain.tmp perlmain.c File perlmain.c not changed. echo av.c scope.c op.c doop.c doio.c dump.c hv.c mg.c perl.c perly.c pp.c pp_hot.c pp_ctl.c pp_sys.c regcomp.c regexec.c utf8.c gv.c sv.c taint.c toke.c util.c deb.c run.c universal.c xsutils.c globals.c perlio.c perlapi.c miniperlmain.c perlmain.c | tr ' ' '\n' >.clist make[1]: 出ます ディレクトリ `/home/kojima/perl-5.6.1' Finding dependencies for av.o. Finding dependencies for scope.o. Finding dependencies for op.o. Finding dependencies for doop.o. Finding dependencies for doio.o. Finding dependencies for dump.o. Finding dependencies for hv.o. Finding dependencies for mg.o. Finding dependencies for perl.o. Finding dependencies for perly.o. Finding dependencies for pp.o. Finding dependencies for pp_hot.o. Finding dependencies for pp_ctl.o. Finding dependencies for pp_sys.o. Finding dependencies for regcomp.o. Finding dependencies for regexec.o. Finding dependencies for utf8.o. Finding dependencies for gv.o. Finding dependencies for sv.o. Finding dependencies for taint.o. Finding dependencies for toke.o. Finding dependencies for util.o. Finding dependencies for deb.o. Finding dependencies for run.o. Finding dependencies for universal.o. Finding dependencies for xsutils.o. Finding dependencies for globals.o. Finding dependencies for perlio.o. Finding dependencies for perlapi.o. Finding dependencies for miniperlmain.o. Finding dependencies for perlmain.o. make[1]: 入ります ディレクトリ `/home/kojima/perl-5.6.1' echo Makefile.SH cflags.SH config_h.SH makeaperl.SH makedepend.SH makedir.SH myconfig.SH writemain.SH pod/Makefile.SH | tr ' ' '\n' >.shlist make[1]: 出ます ディレクトリ `/home/kojima/perl-5.6.1' Updating makefile... test -s perlmain.c && touch perlmain.c cd x2p; make depend make[1]: 入ります ディレクトリ `/home/kojima/perl-5.6.1/x2p' sh ../makedepend MAKE=make make[2]: 入ります ディレクトリ `/home/kojima/perl-5.6.1/x2p' echo hash.c str.c util.c walk.c | tr ' ' '\n' >.clist make[2]: 出ます ディレクトリ `/home/kojima/perl-5.6.1/x2p' Finding dependencies for hash.o. Finding dependencies for str.o. Finding dependencies for util.o. Finding dependencies for walk.o. make[2]: 入ります ディレクトリ `/home/kojima/perl-5.6.1/x2p' echo Makefile.SH cflags.SH | tr ' ' '\n' >.shlist make[2]: 出ます ディレクトリ `/home/kojima/perl-5.6.1/x2p' Updating makefile... make[1]: 出ます ディレクトリ `/home/kojima/perl-5.6.1/x2p' Now you must run 'make'. If you compile perl5 on a different machine or from a different object directory, copy the Policy.sh file from this object directory to the new one before you run Configure -- this will help you with most of the policy defaults.