>Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
>list-help: <mailto:[EMAIL PROTECTED]>
>list-unsubscribe: <mailto:[EMAIL PROTECTED]>
>list-post: <mailto:[EMAIL PROTECTED]>
>Delivered-To: mailing list [EMAIL PROTECTED]
>X-Authentication-Warning: mojo.covalent.net: dougm owned process doing -bs
>Date: Thu, 25 May 2000 12:57:33 -0700 (PDT)
>From: Doug MacEachern <[EMAIL PROTECTED]>
>To: Mark Murphy <[EMAIL PROTECTED]>
>cc: [EMAIL PROTECTED]
>Subject: Re: mod_perl 1.24 testing keeps failing
>MIME-Version: 1.0
>X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N
>
>On Thu, 25 May 2000, Mark Murphy wrote:
>
>> sh Configure -Dcc=gcc -Ubincompat5005
>
>hmm, i've seen a similar report related to largefile support, try once
>more with:
>
>sh Configure -Dcc=gcc -Ubincompat5005 -Uuselargefiles
>
I believe it already did by default. Here is the output from my perl -V
==========================================================================
bash(mark:opus)1201% perl -V
Summary of my perl5 (revision 5.0 version 6 subversion 0) configuration:
Platform:
osname=solaris, osvers=2.7, archname=sun4-solaris
uname='sunos opus 5.7 generic_106541-10 sun4u sparc sunw,ultra-5_10 '
config_args='-Dcc=gcc -Ubincompat5005'
hint=recommended, useposix=true, d_sigaction=define
usethreads=undef use5005threads=undef useithreads=undef
usemultiplicity=undef
useperlio=undef d_sfio=undef uselargefiles=define
use64bitint=undef use64bitall=undef uselongdouble=undef usesocks=undef
Compiler:
cc='gcc', optimize='-O', gccversion=2.95.2 19991024 (release)
cppflags='-fno-strict-aliasing -I/usr/local/include
-I/usr/local/BerkeleyDB.3.0/include'
ccflags ='-fno-strict-aliasing -I/usr/local/include
-I/usr/local/BerkeleyDB.3.0/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64'
stdchar='char', d_stdstdio=define, usevfork=false
intsize=4, longsize=4, ptrsize=4, doublesize=8
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t',
lseeksize=8
alignbytes=8, usemymalloc=y, prototype=define
Linker and Libraries:
ld='gcc', ldflags ='-L/usr/local/lib -L/usr/local/BerkeleyDB.3.0/lib '
libpth=/usr/local/lib /lib /usr/lib /usr/ccs/lib
/usr/local/BerkeleyDB.3.0/lib
libs=-lsocket -lnsl -ldb -ldl -lm -lc -lcrypt -lsec
libc=/lib/libc.so, so=so, useshrplib=false, libperl=libperl.a
Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' '
cccdlflags='-fPIC', lddlflags='-G -L/usr/local/lib
-L/usr/local/BerkeleyDB.3.0/lib'
Characteristics of this binary (from libperl):
Compile-time options: USE_LARGE_FILES
Built under solaris
Compiled at May 24 2000 12:16:14
@INC:
/usr/local/lib/perl5/5.6.0/sun4-solaris
/usr/local/lib/perl5/5.6.0
/usr/local/lib/perl5/site_perl/5.6.0/sun4-solaris
/usr/local/lib/perl5/site_perl/5.6.0
/usr/local/lib/perl5/site_perl
.
==========================================================================
I did notice that it also set the -D_FILE_OFFSET_BITS=64, however, the default
in the perl config was set to no
==========================================================================
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... 8 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]
==========================================================================
Should I still reconfigure perl with the -Uuselargefiles parameter? Is the
-D_FILE_OFFSET_BITS=64 set by the -Duse64bitint? If so, then the script didn't
take the default [n].
Mark Murphy Wayne State University
Systems Analyst II Computing & Information Technology (C&IT)
(313) 577-4795 Voice Academic Computing & Customer Services (ACCS)
(313) 577-8787 Fax 5425 Woodward Ave.
Detroit, MI. 48202
Email: [EMAIL PROTECTED]
WWW : http://www.wayne.edu/
