Yes Ged, I always make test before make install. Even just make, when appropriate...
The idea to make the independently installed mod_perl enabled Apache has failed on this machine several times (when the native sysadmin tried to do that). Now, I have to find out why it fails. I see the polluted file system and a lot of mess in common perl libraries. What of that could affect the installation? I would like to know. I see an odd behavior of the make install (what I've just never been seeing on my dev). It might be OK, or may be wrong. I'd like to know too. I'd like to obtain probably some extra ideas, what to check/care about in this situation... Is there anybody, who can understand what I'm writing about? Thanks, Slava ----- Original Message ----- From: "Ged Haywood" <[EMAIL PROTECTED]> To: "Slava Bizyayev" <[EMAIL PROTECTED]> Cc: "mod_perl Mailing List" <[EMAIL PROTECTED]> Sent: Saturday, April 06, 2002 4:12 PM Subject: Re: sun4-solaris polluted installation > Hi there, > > On Fri, 5 Apr 2002, Slava Bizyayev wrote: > > > Nice try. Unfortunately, helpless... Don't you see two instances of > > mod_perl in common perl libraries? That's just flowers... > > Are you sure you understood my message? > > I don't understand your reply but you seem to be a little frustrated. > > Running two instances of a mod_perl Apache does not necessarily > require that you run the Apache nor mod_perl 'make install' twice > (although you may wish to compile different Apache and/or mod_perl > binaries). You just have to create a second configuration and start a > second server. You can for example compile a mod_perl Apache in your > home directory and run it without root permissions. You don't need to > do anything at all to the system's Perl installation until you mean to > run the mod_perl Apache in production, listening to port 80. In fact > it's probably better if you don't. > > Did you get 'make test' to run ok before attempting 'make install'? > > 73, > Ged. > > > >
