Problem compiling mod_perl for apache 1.3

Problem compiling mod_perl for apache 1.3

Post by Joe Emenake » Sat, 28 Feb 1998 04:00:00



I downloaded the mod_perl 1.08 source a few days ago and have been
trying to get it going with apache 1.3.

The system I'm on is a Debian Linux box. Debian lets you install just
the apache header files (rather than the whole damn source tree) for
compiling modules. This worked great for the mod_jserv Java servlet
module. It hasn't worked so great for mod_perl.

When I run "perl Makefile.PL", it asks me for my apache source, at which
point I point it to "/usr/include/apache-1.3", where the headers are.
Then it asks "Configure mod_perl with /usr/include/apache-1.3?" and I
answer yes.

Things go fine for a while until I get an error message that it can't
get a makefile down in the apache source tree:

   Can't open /usr/include/apache-1.3/modules/perl/Makefile: No such
file or directory
   cat: /usr/include/apache-1.3/Makefile.config: No such file or
directory
   cat: /usr/include/apache-1.3/modules/perl/Makefile: No such file or
directory
   mv: cannot move `/tmp/mpmf.5057' to
`/usr/include/apache-1.3/modules/perl/Makefile': No such file or
directory
   Will run tests as User: 'nobody' Group: 'root'
   Checking for LWP::UserAgent......failed

/usr/lib/perl5/i386-linux/5.004
/usr/lib/perl5/usr/local/lib/site_perl/i386-linux
/usr/local/lib/site_perl .) at Makefile.PL line 687.

I have this sinking suspicion that mod_perl is trying to compile itself
to a ".o" module that gets statically linked into apache (and, thereby,
requiring anyone wanting to use mod_perl to recompile ALL of apache)
instead of the prefered ".so" modules that can be loaded in at runtime.

Any ideas?

- Joe

 
 
 

Problem compiling mod_perl for apache 1.3

Post by Rick Mang » Fri, 06 Mar 1998 04:00:00



> I have this sinking suspicion that mod_perl is trying to compile itself
> to a ".o" module that gets statically linked into apache (and, thereby,
> requiring anyone wanting to use mod_perl to recompile ALL of apache)
> instead of the prefered ".so" modules that can be loaded in at runtime.

Any time you add a module to Apache you need to recompile the server. At
least you did with Apache 1.2.x.
Building mod_perl it asks if you want to rebuild apache or not. You
probably answered yes.

Rick

--
_______________________________________________________________

Rick Mangi                                  Tel: (212) 972-2030
Thaumaturgix, Inc.                          Fax: (212) 972-2003

New York, NY 10017                          http://www.tgix.com
          thau'ma-tur-gy, n. the working of miracles
  "Perl is a state of mind as much as it is a language grammar"
_______________________________________________________________

 
 
 

1. Problem with mod_perl under apache 1.3

Hello you gurus out there.

We have a problem with an application we written in Perl.
We are using an apache which has several virtual servers running on it.
Two of the site are created dynamically using the same scripts.

1.) Script A contains variables which are used by several other scripts
     e.g.:
$rootdir      = $ENV{DOCUMENT_ROOT};
$homedir      = $rootdir . '/contents/';
$dir_user     = $homedir . 'user/';
$dir_material = $homedir . 'material/';
...
2.) Script B uses script A via "require"

If these scripts run (with the same name) on more than one (virtual) server,
mod_perl does not recognize that it should not use the variable-values (and
functions) in its library (like it should when running on one server), but
rather reload them.

The prefered method would be to have a different mod_perl process for each
(virtual) server, I think.

Is there a method to configure apache this way?

Any help apreciated.

Thanks you very much.

Best Regards Markus

2. Samtron monitors - anyone got docs?

3. apache(1.3)+php+mod_perl install

4. future domain

5. Apache 1.3 /AIX 4.2 compile problems

6. HELP! grub won't boot Win98 anymore!

7. Problems compiling Apache 1.3 beta 6

8. named forwarding-only

9. Compile problem Apache 1.3 and GNUgcc 2.7.2.1

10. Apache 1.3/HPUX compile problems

11. apache DSO problem (Loaded DSO libexec/mod_mime.so uses plain Apache 1.3 API)

12. Apache 1.3 - Solaris Compile Help

13. self-compiled httpd does not start (suse 6.1 / apache 1.3.x))