That's the kind of solution I think will work. Starting all over again.
The only doubt from my side is that this a BRAND NEW installation.
Anyway I think it should be done again.
Another question:
If I plan to use the DBD modules in the future, should they be installed
before mod_perl, or is it the same?
Thanks
Alejandro
----- Original Message -----
From: "Kurt Hansen" <[EMAIL PROTECTED]>
To: "A. Santillan Iturres" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, February 27, 2001 5:36 PM
Subject: Re: Not even beginning - INSTALL HELP
> Hello Alejandro,
>
> > I did not build Perl myself. It is the Perl that comes from rpm's with
> RH7.0
> > distro.
> > Idem gcc and Apache.
> > It seems that there is something I am missing.
> > I do have Apache
> > I do have gcc
> > I do have perl
> > I do have mod_perl-1.25.gcc
>
> I'm not sure if this will help, but your situation sounds similar --
though
> not exact -- to one I just faced over the weekend.
>
> I upgraded a development system to RH6.1 from RH5.2 (ok, I'm a bit behind
> the times, but I that's the RH CD-ROM I had available. Also, not quite
ready
> for perl 5.6.0, given some of the programs we use.) I was also upgrading
> from Apache 1.3.6 -- Raven SSL 1.4.1 -- mod_perl 1.21 to Apache 1.3.12 --
> Raven SSL 1.4.3 -- mod_perl 1.25. My segfault did not happen during the
> compile, but whenever the server was accessed. The child segfaulted.
>
> I went through a few hickups, like having CPAN.pm try to install 5.6.0,
and
> only was able to fix the problem by starting over with a clean
installation
> of perl 5.005_3, mod_perl 1.24, the DBD modules, apache 1.3.12, Raven
1.4.3.
> When I started clean, everything worked perfectly according to the
> directions in the INSTALL.x docs in the mod_perl directory!
>
> Don't know what exactly caused the problem, but maybe starting over with
> mod_perl 1.24 would help?
>
> Take care,
>
> Kurt Hansen
> [EMAIL PROTECTED]
>
>
>
