persistent database problem

[Differentiated Software Solutions Pvt. Ltd]

Hi,
    I have started with one httpd; 
and executed the following mod-perl program from the browser. We've 
configured apache to have persistent DBI
    The idea is first time the 
database handle will be inactive and it will print 'INSIDE'.  From the 
second time onwards the database handle will be active and it will print 
'OUTSIDE'.  This is working.
    But, sometimes the 'OUTSIDE' 
comes from the third or fourth time only.  (that is it takes more than one 
attempt to become persistent) Why it is happening like this?
Thanks
Muthu S Ganesh
 
mod-perl code is here:
 
$rc = $dbh_pg->{Active};print "$$: 
$rc\n";if($rc eq ''){    
print "INSIDE\n";
    $dbh_pg 
= 
DBI->connect("dbi:Pg:dbname=adcept_smg_ctrl","postgres","postgres",{RaiseError => 1}) || die 
$DBI::errstr;
}
else{    print 
"OUTSIDE\n";
}
 
 
Differentiated Software Solutions Pvt. Ltd.176, 
Ground Floor, 6th Main,2nd Block, RT NagarBangalore - 560032Phone : 
91 80 3431470www.diffs-india.com

tru64/Configure problem with perl5.6.0 for modperl

[Bob Parkinson]

Hi,

I'm in process of upgrading our perl/modperl/apache installation, and have
a problem. Not sure if this is a perl problem or a modperl problem.

modperl-1.24/perl-5.6.0/tru64-D/apache-1.3.14

I'm gettting the ./Configure fail with:

 + doing sanity check on compiler and options
** A test compilation with your Makefile configuration
** failed.  The below error output from the compilation
** test will give you an idea what is failing. Note that
** Apache requires an ANSI C Compiler, such as gcc. 

 Error Output for sanity check 
cd ..; gcc  -DOSF1 -DUSE_HSREGEX -DUSE_EXPAT -I./lib/expat-lite
-DNO_DL_NEEDED -std -fprm d -ieee -D_INTRINSICS -I/usr/include_ndbm
-I/usr/local/include -DLANGUAGE_C -DMOD_PERL -o helpers/dummy
helpers/dummy.c  `/usr/local/perl-5.6.0/bin/perl
/usr/local/perl-5.6.0/source_apache_modperl/apache_1.3.14/mod_perl-1.24/src/modules/perl/ldopts
` -lm
gcc: d: No such file or directory
cc1: Invalid option `-std'

It's trying to use the compiled defaults that I've made perl-5.6.0 with
(eg. -std) that work with digital cc, but not with gcc, this is a  bit
from the perl -V for 5.6.0

  Compiler:
cc='cc', optimize='-O4', gccversion=
cppflags='-std -ieee -D_INTRINSICS -I/usr/local/include -DLANGUAGE_C'
 

when I use the installed perl (5.0 patch4 sublevel4) I don't get this
problem. This was build with digital cc and shows built with non-gcc
flags: eg;

  Compiler:
cc='cc', optimize='-O4', gccversion=
cppflags='-std -D_INTRINSICS -I/usr/local/include -D__LANGUAGE_C__'
 


Have I misinstalled the new perl or is this a modperl problem (or
something else)? 

Cheers,

Bob

RE: DBD-Oracle

[Geoffrey Young]

> -Original Message-
> From: Daniel Hutchison [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, October 22, 2000 2:16 PM
> To: [EMAIL PROTECTED]
> Subject: DBD-Oracle
> 
> 
> I just transplanted our website from a computer that had only Net8
> installed, to a computer that has an entire Oracle Database 
> installed.  As
> far as I can tell I otherwise fully replicated the original 
> system on the
> new machine.
> 
> These errors are appearing in error_log:
> 
> [Sun Oct 22 14:03:49 2000] Carp.pm: Use of uninitialized value at
> /usr/local/lib/perl5/5.6.0/Carp.pm
>   line 119.
> [Sun Oct 22 14:03:49 2000] Carp.pm: Use of inherited AUTOLOAD 
> for non-method
>   DBD::Oracle::ORA_OCI() is
> deprecated at
>  
> /usr/local/lib/perl5/site_perl/5.6.0/i686-linux/DBD/Oracle.pm line 48.
> 
> I've done a search on the web that return this that seems to 
> indicate the
> AUTOLOAD error has something to do with LD_LIBRARY_PATH, but 
> my I have set
> that variable using both SetEnv and PerlSetEnv.  Any help would be
> appreciated! Thanks.

If you're using DBD::Oracle 1.06, you can find the steps to follow on the
DBI users archive (links on http://www.symbolstone.org/technology/perl/DBI/)
and look for ldconfig or something similar - the question has turned to a
FAQ on that list, so there is no shortage of help on how to set
LD_LIBRARY_PATH properly...

the short answer/path is to edit DBD::Oracle Makefile.PL and build it again

-$::opt_b = 1;   # try to use Oracle's own 'build' rule
+$::opt_b = 0;   # try to use Oracle's own 'build' rule

HTH

--Geoff

> 
> Daniel Hutchison
> Target Analysis Group
> mailto:[EMAIL PROTECTED] 
>  
> 617.583.8411
> 

[DIGEST] mod_perl digest 10/15/2000

[Geoffrey Young]

--

  mod_perl digest
 
   October 15, 2000 - October 21, 2000

--

Recent happenings in the mod_perl world...


Features

  o mod_perl status
  o cvs development
  o module announcements
  o mailing list highlights
  o news
  o FAQ of the week
  o links


mod_perl status

  o mod_perl
- stable: 1.24_01 (released October 10, 2000) [1]
- development: 1.24_02-dev [2]
  o Apache
- stable: 1.3.14 (released October 13, 2000) [3]
- development: 1.3.15-dev [4]
  o Perl
- stable: 5.6 (released March 23, 2000) [5]
- development: 5.7 [6]


cvs development 

  o no patches this week...


module announcements

  o HTML-Embperl 1.3b6 - a module for embedding Perl code in HTML 
pages [7]

  o Apache::SizeLimit released a patch to fix uninitialized
warnings [8]

  o Apache::ProxyStuff 0.10 - adding headers and footers to content
proxied from other web servers by "stuffing" the header and footer
into their correct places in the content [9]

  o Apache::DebugInfo 0.05 - log various bits of per-request data [10]


mailing list highlights

  o A rather lengthy discussion about maintaining state without 
cookies for authentication purposes [11] [12]
 
  o Advice for getting mod_perl to work on NT with ActivePerl [13]

  o When writing translation handlers, instead of checking if the file
is a directory, you can also check $r->content_type against the
DIR_MAGIC_TYPE constant [14]

  o An interesting solution to file uploads over multiple pages [15]

  o Discussion on the size limits of cookie data - Apache defaults to
8K worth of headers, but Netscape limits cookies to 4K [16]

  o Another cookie discussion regarding proxying and port numbers [17]

  o A patch was submitted to stop Windows from crashing when mod_perl
DSO is stopped [18] [19]


news

  o Netcraft mod_perl statistics are out for September [20]
  1508381 Domains, 170758 IP Addresses


FAQ of the week

  o I'm trying to make mod_perl with Apache 1.3.14, but see the error:
"Apache Version 1.3.0 required, aborting..." 

Using mod_perl with Apache 1.3.14 requires an upgrade to 1.24-01
(or some hacking around). Get the latest version from the mod_perl
distribution page [21]


links

  o The Apache/Perl Integration Project [22]
  o mod_perl documentation [23]
  o mod_perl modules on CPAN [24]
  o mod_perl homepage [25]
  o mod_perl list archives [26] [27]


happy mod_perling...

--Geoff
[EMAIL PROTECTED]

--
[1] http://perl.apache.org/dist/
[2] http://perl.apache.org/from-cvs/modperl/
[3] http://www.apache.org/dist/
[4] http://dev.apache.org/from-cvs/apache-1.3/
[5] http://www.perl.com/pub/language/info/software.html#stable
[6] http://www.perl.com/pub/language/info/software.html#devel
[7] http://forum.swarthmore.edu/epigone/modperl/falhahclerd 
[8] http://forum.swarthmore.edu/epigone/modperl/tilreldprend
[9] http://forum.swarthmore.edu/epigone/modperl/kaphandhul
[10] http://forum.swarthmore.edu/epigone/modperl/swehpontol
[11] http://forum.swarthmore.edu/epigone/modperl/blulrextwu
[12] http://forum.swarthmore.edu/epigone/modperl/flolcreskin
[13] http://forum.swarthmore.edu/epigone/modperl/rixglelclou
[14] http://forum.swarthmore.edu/epigone/modperl/zundimpcherd
[15] http://forum.swarthmore.edu/epigone/modperl/karwhoskul
[16] http://forum.swarthmore.edu/epigone/modperl/gilswysnerm
[17] http://forum.swarthmore.edu/epigone/modperl/thimpzhanyil
[18] http://forum.swarthmore.edu/epigone/modperl/dwebonnan
[19] http://forum.swarthmore.edu/epigone/modperl/flanvenshul
[20] http://marc.theaimsgroup.com/?l=apache-modperl-cvs&m=97187209526568&w=2
[21] http://perl.apache.org/dist/mod_perl-1.24_01.tar.gz
[22] http://perl.apache.org
[23] http://perl.apache.org/#docs
[24] http://www.perl.com/CPAN-local/modules/by-module/Apache/
[25] http://www.modperl.com
[26] http://forum.swarthmore.edu/epigone/modperl/
[27] http://archive.covalent.net/modperl/

Very WIRED error msg

[hpcenter]

Hello guys , I saw this :

[Mon Oct 23 14:45:09 2000] [notice] Apache/1.3.12 (Unix) mod_perl/1.24 configured -- 
resuming normal operations
Argument "OK" isn't numeric.
Argument "OK" isn't numeric.
Argument "OK" isn't numeric.
Argument "OK" isn't numeric.

etc..

What that mean ???
Thanks

- La messagerie itinérante sans abonnement NetCourrier -
Web : www.netcourrier.com Minitel : 3615 et 3623 NETCOURRIER
  Tél : 08 36 69 00 21

Re: Very WIRED error msg

[Steven Cotton]

On Mon, 23 Oct 2000 [EMAIL PROTECTED] wrote:

> Hello guys , I saw this :
> 
> [Mon Oct 23 14:45:09 2000] [notice] Apache/1.3.12 (Unix) mod_perl/1.24 configured -- 
>resuming normal operations
> Argument "OK" isn't numeric.
> Argument "OK" isn't numeric.
> Argument "OK" isn't numeric.
> Argument "OK" isn't numeric.
> 
> etc..
> 
> What that mean ???

Do you:

use Apache::Constants qw(:common); 

at the top of your script or in your startup file?

-- 
steven

Re: Very WIRED error msg

[John Saylor]

Hi
> - Original Message -
> From: <[EMAIL PROTECTED]>

> Argument "OK" isn't numeric.
> Argument "OK" isn't numeric.
> Argument "OK" isn't numeric.
> Argument "OK" isn't numeric.

> What that mean ???

Your code is expecting a numeric value [probably 1 or 0] and it's
getting a string.
Your code is expecting a numeric value [probably 1 or 0] and it's
getting a string.
Your code is expecting a numeric value [probably 1 or 0] and it's
getting a string.
Your code is expecting a numeric value [probably 1 or 0] and it's
getting a string.

\js

Re: Very WIRED error msg

[Sean D. Cook]

> > Argument "OK" isn't numeric.
> > Argument "OK" isn't numeric.
> > Argument "OK" isn't numeric.
> > Argument "OK" isn't numeric.
> 

It looks like you are trying to check the return value from a mod_perl
handler.  

my $foo = handler();
if($foo == 1){
   # this won't work :)
}


sub handler {
 ...  

 return OK;
}

Re: IPC::Shareable (was Re: Perl module - LWP)

[Alexander Farber (EED)]

On Sun, 22 Oct 2000, Steven Cotton wrote:
> What version of Perl are you using? I had some problems with make test,
> one of the tests doesn't return and I got a few munged shared memory
> segment errors, I was attempting to install under Solaris 7 and Perl
> 5.6.0.

The messages about "munged shared memory" seem to be going if you change

my($tag, $ice) = unpack 'A14 A*' => $stuff;

in the file lib/IPC/Shareable.pm, sub _thaw to the:

my($tag, $ice) = unpack 'A13 A*' => $stuff;

(since the sub _freeze calls

my $stuff = 'IPC::Shareable' . $ice;   

- i.e. 13 chars). But there are further problems ("make test" hangs)...

Re: persistent database problem

[Jeff Beard]

Are using Apache::DBI and establishing a connection in
your startup.pl?

On Mon, 23 Oct 2000, Differentiated Software Solutions Pvt. Ltd wrote:

> Hi,
> I have started with one httpd; and executed the following mod-perl program from 
>the browser. We've configured apache to have persistent DBI
> The idea is first time the database handle will be inactive and it will print 
>'INSIDE'.  From the second time onwards the database handle will be active and it 
>will print 'OUTSIDE'.  This is working.
> But, sometimes the 'OUTSIDE' comes from the third or fourth time only.  (that is 
>it takes more than one attempt to become persistent) Why it is happening like this?
> Thanks
> Muthu S Ganesh
> 
> mod-perl code is here:
> 
> $rc = $dbh_pg->{Active};
> print "$$: $rc\n";
> if($rc eq '')
> {
> print "INSIDE\n";
> $dbh_pg = 
>DBI->connect("dbi:Pg:dbname=adcept_smg_ctrl","postgres","postgres",{RaiseError => 1}) 
>|| die $DBI::errstr;
> }
> else
> {
> print "OUTSIDE\n";
> }
> 
> 
> Differentiated Software Solutions Pvt. Ltd.
> 176, Ground Floor, 6th Main,
> 2nd Block, RT Nagar
> Bangalore - 560032
> Phone : 91 80 3431470
> www.diffs-india.com
> 

-- 
Jeff Beard
___
Web:www.cyberxape.com
Location:   Boulder, CO, USA

Re: IPC::Shareable (was Re: Perl module - LWP)

[Alexander Farber (EED)]

>my $stuff = 'IPC::Shareable' . $ice;   
> - i.e. 13 chars)

Oops, sorry - I can't count on mondays!

Re: IPC::Shareable (was Re: Perl module - LWP)

[Steven Cotton]

On Mon, 23 Oct 2000, Alexander Farber (EED) wrote:

> The messages about "munged shared memory" seem to be going if you change
> 
> my($tag, $ice) = unpack 'A14 A*' => $stuff;
> 
> in the file lib/IPC/Shareable.pm, sub _thaw to the:
> 
> my($tag, $ice) = unpack 'A13 A*' => $stuff;
> 
> (since the sub _freeze calls
> 
> my $stuff = 'IPC::Shareable' . $ice;   
> 
> - i.e. 13 chars). But there are further problems ("make test" hangs)...

Intriguing. Since I'm a sad spod I'll have a look at that later tonight,
I'll also see if it cures the same error I get when attempting to access
a previously delete()ed shared hash element with exists().

Thanks,

-- 
steven

Re: persistent database problem

[John K. Sterling]

The db connection happens once for each child - so every time you hit a
child for the first time it will open up a new connection - you probably
have apache configured to start with 4 or so kids.

sterling

 On Mon, 23 Oct 2000,
Differentiated Software Solutions Pvt. Ltd wrote:

> Hi,
> I have started with one httpd; and executed the following mod-perl program from 
>the browser. We've configured apache to have persistent DBI
> The idea is first time the database handle will be inactive and it will print 
>'INSIDE'.  From the second time onwards the database handle will be active and it 
>will print 'OUTSIDE'.  This is working.
> But, sometimes the 'OUTSIDE' comes from the third or fourth time only.  (that is 
>it takes more than one attempt to become persistent) Why it is happening like this?
> Thanks
> Muthu S Ganesh
> 
> mod-perl code is here:
> 
> $rc = $dbh_pg->{Active};
> print "$$: $rc\n";
> if($rc eq '')
> {
> print "INSIDE\n";
> $dbh_pg = 
>DBI->connect("dbi:Pg:dbname=adcept_smg_ctrl","postgres","postgres",{RaiseError => 1}) 
>|| die $DBI::errstr;
> }
> else
> {
> print "OUTSIDE\n";
> }
> 
> 
> Differentiated Software Solutions Pvt. Ltd.
> 176, Ground Floor, 6th Main,
> 2nd Block, RT Nagar
> Bangalore - 560032
> Phone : 91 80 3431470
> www.diffs-india.com
> 

Re: child seg fault (11) with mod_perl as DSO (Sol 8, perl 5.6, gcc 2.95.2)

[Bjørn Ola Smievoll]

* Gary Goldberg
|
| Hello. I am build a machine from scratch, so I've done this:
| 
| 1. Installed clean Solaris 8 Intel.
| 2. Installed SFWgcc (2.95.2) from Solaris install.
| 3. Used Solaris-installed perl 5.005 to build perl 5.6 in /opt. (Everything
| in /opt).
| 4. Used CPAN to install libnet, MD5, CPAN bundles.
| 5. Installed Mysql 3.23.26 into /opt.
| 6. Installed Bundle::Mysql, Bundle::Apache using CPAN.
| 7. Installed Berkeley db 3.1 into /opt.
| 8. Reinstalled perl 5.6 using -Ubincomat5005 enabling large file support.
| 8. Used clean dists of apache 1.3.14, php 4.03pl1, mod_perl 1.24.
| 
|Built apache using suexec config, --enable=module=most --enable-shared-max
|with largefile support. Make, install.
| 
|Built mod_perl using USE_APXS=1 WITH_APXS=/opt/apache/bin/apxs EVERYTHING=1
|and make, install.
| 
|Built php4 using APXS. Make, install.
| 
| Everything seems fine, but when I try to access the status module or the
| webroot home page I get "child exit segmentation fault (11)".
| 
| All previous messages in the list archive did not seem to apply, although
| I tried their suggestions also. Nothing seems to work and I am stuck
| here, Any ideaa? THanks to all in advance, -Gary


I've got the same sigsegv problem, though not with perl 5.6.0 only
5.00503 and 500404 and only on linux/x86 and linux/ppc, solaris/usparc
works fine.  DSO or no DSO doesn't seem to matter.  I'm trying to
do some debugging of this problem, but haven't gotten very far.
Actually I only have the Apache::Status sigsegv on one build on
linux/x86.  _BUT_ I've got another homemade module that dies on every
linux build that doesn't use 5.6.  It's a real show stopper, but it's
forcing me to learn a little more about gdb and c every day :)

Any advances you do in tracing this problem, please let me know.


(bo)
Head Engineer   Center for Information Technology Services
University of Oslo

Re: File Space Usage ... in perl ?

[Alexander Farber (EED)]

See Perl Power Tools - http://language.perl.com/ppt/what.html

[REPOST] MyClass::import() not being called.

[Rodney Broom]

Hi all,

Did we forget me? (snif, snif...)


I've got this happy little access handler that works just fine. I'm loading it
like this:
  PerlAccessHandler MyClass

Now I need for it to accept parameters through import(). That would let me
change the usage to something like this:
  PerlAccessHandler MyClass 'extra parameters'

The catch is that MyClass::import() isn't being called reguardless of how I load
it. I've done all of the obvious stuff, like including lots of debugging
messages in the package, reading the docs, reading the Apache modules book, and
even searching the archives for this list, no help. Does anybody know what's
happening here?


Rodney Broom

Re: [REPOST] MyClass::import() not being called.

[Carlos Ramirez]

You can use PerlSetVar to set parameters like so:
PerlAccessHandler MyClass
PerlSetVar Param1
PerlSetVar Param2
in your handler (MyClass) you can call $r->dir_config('Param1') to get
it's value;
-Carlos
 
 
Rodney Broom wrote:
Hi all,
Did we forget me? (snif, snif...)
I've got this happy little access handler that works just fine. I'm
loading it
like this:
  PerlAccessHandler MyClass
Now I need for it to accept parameters through import(). That would
let me
change the usage to something like this:
  PerlAccessHandler MyClass 'extra parameters'
The catch is that MyClass::import() isn't being called reguardless of
how I load
it. I've done all of the obvious stuff, like including lots of debugging
messages in the package, reading the docs, reading the Apache modules
book, and
even searching the archives for this list, no help. Does anybody know
what's
happening here?

Rodney Broom

-- 
---
Carlos Ramirez + Boeing + Reusable Space Systems + 714.372.4181
---
-- Don't make me use uppercase
 

Re: [REPOST] MyClass::import() not being called.

[Rodney Broom]

From: "Carlos Ramirez" <[EMAIL PROTECTED]>
CR> You can use PerlSetVar to set parameters like so:

CR> PerlAccessHandler MyClass
CR> PerlSetVar Param1
CR> PerlSetVar Param2


Yep, that's definately an effective work-around. My biggest concern is the fact
that import() doesn't seem to be getting called at all. That sounds broken to
me.


Rodney Broom

Re: [REPOST] MyClass::import() not being called.

[Rodney Broom]

From: "Benjamin Trott" <[EMAIL PROTECTED]>

> Unless I'm missing something rather obvious--or perhaps non-obvious--you
> can't do this. If you provide multiple params to a Perl*Handler, that sets
> up a stacked handlers for that request phase; it doesn't pass parameters to
> the import method in that class.
>
> The Guide shows this syntax for setting up stacked handlers:
>
> Perl*Handler directives (in your configuration files) can
> define any number of subroutines. For example:
>
> PerlTransHandler OneTrans TwoTrans RedTrans BlueTrans
>
> Which would seem to conflict rather badly w/ your desired behavior. :)
>
> As another poster mentioned, try using PerlSetVar or PerlAddVar to set
> config options.
>

Heh, sort of, but not. This handler will only be loaded once per configuration.
The types of parameters I'll pass to this handler will change
machine-by-machine. You see, I need to run this package on several different
servers, and need it to know how to configure it's self.


Rodney Broom

Re: [REPOST] MyClass::import() not being called.

[Benjamin Trott]

> The types of parameters I'll pass to this handler will change
> machine-by-machine. You see, I need to run this package on several different
> servers, and need it to know how to configure it's self.

Okay... I don't think I get exactly why this situation makes using
PerlSetVar impossible/impractical, because if you were thinking that you
could write

PerlAccessHandler My::Access 'parameters'

Why can't you just write

PerlAccessHandler My::Access
PerlSetVar param1 value1
PerlSetVar param2 value2

So I'm not sure I understand that distinction.

*However*, if you really want to use import, couldn't you go about doing so
like this:


use My::Access 'parameters';


PerlAccessHandler My::Access

If you do that, and define a My::Access::import, it should definitely be
called correctly.

bye,
Ben

Re: [REPOST] MyClass::import() not being called.

[Ken Williams]

[EMAIL PROTECTED] (Rodney Broom) wrote:
>I've got this happy little access handler that works just fine. I'm
>loading it like this:
> PerlAccessHandler MyClass
>
>Now I need for it to accept parameters through import(). That would let
>me change the usage to something like this:
> PerlAccessHandler MyClass 'extra parameters'
>
>The catch is that MyClass::import() isn't being called reguardless of
>how I load it. 

I actually wouldn't expect it to call import() with the given parameter
list, simply because it's documented to do something else.  It's
documented to think of the second parameter as another AccessHandler
module, as in chained handlers.

Remember: PerlModule is the way to load new modules.  Ordinarily you
should do "PerlModule Blah" to load the module, and then "Perl*Handler
Blah" to actually install it as a handler somewhere.  However, in recent
versions of mod_perl, the "PerlModule Blah" will be done automatically
for you if you refer to a previously unseen module as a handler.

To me, the exact behavior you're looking for seems like a bad idea,
because as Benjamin pointed out, it conflicts with the chained handler
syntax.  But it seems reasonable that PerlModule might take an import()
list.  I'm not sure whether it does so now or not.


  ------
  Ken Williams Last Bastion of Euclidity
  [EMAIL PROTECTED]The Math Forum

cannot install mod_perl-1.24_01/mod_ssl-2.7.1/apache_1.3.14/perl-5.6.0

[William Rico]

I've been trying to install the following combination without any luck:
mod_perl-1.24_01
mod_ssl-2.7.1
openssl-0.9.6
apache_1.3.14
perl-5.6.0
...on FreeBSD 2.2.8

Error when making mod_perl:
bash-2.02# make
...successful steps cut out...
<=== src/modules/perl
<=== src/modules
cc -c -I. -I/usr/local/lib/perl5/5.6.0/i386-freebsd/CORE -I./os/unix -I./inc
lude   -f
unsigned-char -DMOD_SSL=207101 -DMOD_PERL -DUSE_PERL_SSI -I/usr/local/includ
e -DEAPI
-DNO_DL_NEEDED -I/usr/local/include `./apaci` modules.c
cc -c -I. -I/usr/local/lib/perl5/5.6.0/i386-freebsd/CORE -I./os/unix -I./inc
lude   -f
unsigned-char -DMOD_SSL=207101 -DMOD_PERL -DUSE_PERL_SSI -I/usr/local/includ
e -DEAPI
-DNO_DL_NEEDED -I/usr/local/include `./apaci` buildmark.c
cc  -funsigned-char -DMOD_SSL=207101 -DMOD_PERL -DUSE_PERL_SSI -I/usr/local/
include -
DEAPI -DNO_DL_NEEDED -I/usr/local/include `./apaci` -L/opt/ssl/lib-o
httpd buildm
ark.o modules.o  modules/standard/libstandard.a  modules/ssl/libssl.a
modules/perl/l
ibperl.a  main/libmain.a  ./os/unix/libos.a
 ap/libap.a-lcrypt   -lssl -lcrypto
  -L/usr/local/lib
/usr/local/lib/perl5/5.6.0/i386-freebsd/auto/DynaLoader/DynaLoader
.a -L/usr/local/lib/perl5/5.6.0/i386-freebsd/CORE -lperl -lm -lc -lcrypt
DynaLoader.o: Undefined symbol `_Perl_vmess' referenced from text segment
*** Error code 1

Stop.

What is _Perl_vmess?  Could the above error be related to my installation of
perl-5.6.0?  I was able to compile this version of mod_perl when I had Perl
5.00503.  Should I blow 5.6 away and try with 5.00503 again?  I appreciate
your time and help.

Thanks!!!

-Will
[EMAIL PROTECTED]

P.S. Here are more specifics on steps  I took:

(1) I installed perl-5.6.0 without trouble.  I chose all the defaults.  As
it was installing, I didn't see any error messages or instances where the
defaults weren't good.
* I wasn't sure whether to override the use "vfork" (?) which was one of the
prompts so I went with the default (use "vfork").
* I did not build a shared libperl.so.
* I did choose dynamic loading.
I'm mentioning the above b/c I'm not really too clear on the implications so
they remain suspects in the mystery to me.

(2) I installed openssl-0.9.6 as per the instructions.  No problems there.

(3) I followed the mod_perl instructions in INSTALL.simple.mod_ssl:

ash-2.02# cd ../mod_ssl-2.7.1-1.3.14
bash-2.02# ./configure --with-apache=../apache_1.3.14
Configuring mod_ssl/2.7.1 for Apache/1.3.14
 + Apache location: ../apache_1.3.14 (Version 1.3.14)
 + Auxiliary patch tool: ./etc/patch/patch (local)
 + Applying packages to Apache source tree:
   o Extended API (EAPI)
   o Distribution Documents
   o SSL Module Source
   o SSL Support
   o SSL Configuration Additions
   o SSL Module Documentation
   o Addons
Done: source extension and patches successfully applied.

bash-2.02# perl Makefile.PL USE_APACI=1 EVERYTHING=1 SSL_BASE=/opt/ssl
APACHE_PREFIX=
/opt/apache APACI_ARGS=--enable-module=ssl,--enable-module=rewrite

bash-2.02# cd ../mod_perl-1.24_01

bash-2.02# perl Makefile.PL USE_APACI=1 EVERYTHING=1 SSL_BASE=/opt/ssl
APACHE_PREFIX=
/opt/apache APACI_ARGS=--enable-module=ssl,--enable-module=rewrite
Will configure via APACI
Configure mod_perl with ../apache_1.3.14/src ? [y]
Shall I build httpd in ../apache_1.3.14/src for you? [y]
cp apaci/Makefile.libdir ../apache_1.3.14/src/modules/perl/Makefile.libdir
cp apaci/Makefile.tmpl ../apache_1.3.14/src/modules/perl/Makefile.tmpl
cp apaci/README ../apache_1.3.14/src/modules/perl/README
cp apaci/configure ../apache_1.3.14/src/modules/perl/configure
cp apaci/libperl.module ../apache_1.3.14/src/modules/perl/libperl.module
cp apaci/mod_perl.config.sh
../apache_1.3.14/src/modules/perl/mod_perl.config.sh
cp apaci/load_modules.pl.PL
../apache_1.3.14/src/modules/perl/load_modules.pl.PL
cp apaci/find_source.PL ../apache_1.3.14/src/modules/perl/find_source.PL
cp apaci/apxs_cflags.PL ../apache_1.3.14/src/modules/perl/apxs_cflags.PL
cp apaci/mod_perl.exp ../apache_1.3.14/src/modules/perl/mod_perl.exp
PerlDispatchHandler.enabled
PerlChildInitHandlerenabled
PerlChildExitHandlerenabled
PerlPostReadRequestHandler..enabled
PerlTransHandlerenabled
PerlHeaderParserHandler.enabled
PerlAccessHandler...enabled
PerlAuthenHandler...enabled
PerlAuthzHandlerenabled
PerlTypeHandler.enabled
PerlFixupHandlerenabled
PerlHandler.enabled
PerlLogHandler..enabled
PerlInitHandler.enabled
PerlCleanupHandler..enabled
PerlRestartHandler..enabled
PerlStackedHandlers.enabled
PerlMethodHandlers..enabled
PerlDirectiveHandlers...enabled
PerlTableApienabled
PerlLogApi..enabled
PerlUriApi..enabled
PerlUtilApi.enabled
PerlFileApi.enabled
PerlConnectionApi...enabled
PerlServerApi...enabled
PerlSectionsenabled
PerlSSI