[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 2.9 and perl 5.8.0 question
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Re: 2.9 and perl 5.8.0 question
- From: Chuck Yerkes <chuck+obsd_(_at_)_2003_(_dot_)_snew_(_dot_)_com>
- Date: Sun, 4 May 2003 15:12:13 -0400
- Mail-followup-to: Chuck Yerkes <chuck+obsd_(_at_)_2003_(_dot_)_snew_(_dot_)_com>, misc_(_at_)_openbsd_(_dot_)_org
- Reply-to: misc_(_at_)_openbsd_(_dot_)_org
It might be offered that 3.1 was just EOL'd making
2.9 mainly moot and very unsupported.
Which should explain why few people of expertise
will respond. The effort of getting your stuff
going on an EOL'd release may work with 3.3, but
may not and thence must be redone. Why do it twice
when you can do it once?
Quoting Carl Brewer (carl_(_at_)_bl_(_dot_)_echidna_(_dot_)_id_(_dot_)_au):
> I've been working with Stas Bekman of mod_perl
> fame with trying to get mod_perl2 to work on
> OBSD (in this case 2.9, but maybe this is a
> general issue?) with apache 2.0.45
> We've come up against what we think is a quirk of
> the perl installation on 2.9 (again, may be a general OBSD
> We've been seeing segfaults that we think are caused by
> my perl 5.8.0 build not really quite working properly
> on OBSD 2.9. Having a quick scan through
> /usr/src/gnu/usr.bin/perl doesn't show me anything
> unusual at first glance, and /usr/bin/perl -V says :
> steel1# /usr/bin/perl -V
> Summary of my perl5 (revision 5.0 version 6 subversion 0) configuration:
> osname=openbsd, osvers=2.9, archname=i386-openbsd
> config_args='-Dopenbsd_distribution=defined -dsE'
> hint=recommended, useposix=true, d_sigaction=define
> usethreads=undef use5005threads=undef useithreads=undef
> useperlio=undef d_sfio=undef uselargefiles=define
> use64bitint=undef use64bitall=undef uselongdouble=undef usesocks=undef
> cc='cc', optimize='-O2', gccversion=2.95.3 20010125 (prerelease)
> cppflags='-fno-strict-aliasing -I/usr/local/include'
> ccflags ='-fno-strict-aliasing -I/usr/local/include'
> stdchar='char', d_stdstdio=undef, usevfork=true
> intsize=4, longsize=4, ptrsize=4, doublesize=8
> d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12
> ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t',
> alignbytes=4, usemymalloc=n, prototype=define
> Linker and Libraries:
> ld='cc', ldflags =''
> libs=-lm -lc
> libc=/usr/lib/libc.so.26.2, so=so, useshrplib=true,
> Dynamic Linking:
> dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=define, ccdlflags=' '
> cccdlflags='-DPIC -fPIC ', lddlflags='-shared -fPIC '
> Characteristics of this binary (from libperl):
> Compile-time options: USE_LARGE_FILES
> Locally applied patches:
> SUIDMAIL - fixes for suidperl security
> CHANGE6214 - fixes a coredump in @DB::args
> Built under openbsd
> Compiled at Apr 28 2001 03:39:51
> I think the magic is in -Dopenbsd_distribution=defined,
> can anyone point me at what's in there so I can try the
> same defs with my 5.8.0 build to see if that'll
> fix the problem we're seeing? I've probably done something
> really dumb like confused ld.so with the wrong paths,
> but if anyone can let me know what's contained within
> -Dopenbsd_distribution it may help a little.
> I had a look at hints/openbsd.sh, which is where that
> comes from, but confess to not really understanding
> how to make it behave nicely.
> Can anyone help me build a perl-5.8.0 on 2.9 that
> won't go looking in the wrong (ie: clash with
> the OS release installed 5.6.0) lib dirs etc?
> Also, out of curiosity, how does ls know to send me to
> /usr/src/gnu/usr.bin/perl from /usr/ports/lang ? ls -lag
> doesn't who me any sym or hard links to that dir :
> steel1# cd /usr/ports/lang
> steel1# ls -lag perl*
> ls: No match.
> steel1# cd perl