Operating System - HP-UX
1855011 Members
2797 Online
104109 Solutions
New Discussion

compile on one server and moving sendmail/apache..

 
someone_4
Honored Contributor

compile on one server and moving sendmail/apache..

Hello everyone,
I just complied sendmail/apache from source on one server. I was wondering how would I go about moving a configuration that works to another server without having to re-compile.

Thanks
~ Richard
5 REPLIES 5
Jordan Bean
Honored Contributor

Re: compile on one server and moving sendmail/apache..


If the architectures are identical or compatible and the build is compatible, then you should be able to tar up the build tree, ftp it over, untar, and run make install. This is recommended for apps like Sendmail that don't install in their own directories. However, if Apache is installed in its own directory (/opt/apache?), then you may be able to copy that tree assuming the archs are compatible.

As you get the configurations working on one server, simply copy sendmail.cf and httpd.conf to the other servers with appropriate modifications.
someone_4
Honored Contributor

Re: compile on one server and moving sendmail/apache..

the issue with sendmail is that i dont want to have to recompile or install ansi/c++ to be able to install the lib files.

~ Richard
Christopher Caldwell
Honored Contributor

Re: compile on one server and moving sendmail/apache..

Given that the machines are the same PA RISC level and the same word width (32 bit vs. 64 bit), you can simply copy everything (rcp, ftp, tar+ ... pick your tool) from the installed point on host a to the install point on host b. Everything will work just fine.
Jordan Bean
Honored Contributor

Re: compile on one server and moving sendmail/apache..


If the compiler is on PA2.0W, but the other systems are a mix of PA2.0, PA2.0W, and PA1.1, then compile with cc +DAportable.

Jordan Bean
Honored Contributor

Re: compile on one server and moving sendmail/apache..


Forgive me if I haven't answered your question. I will be more specific.

Build the software on the host with the compiler (make, make all, whatever). Use the cc option +DAportable if necessary. Install the software (make install) and test.

When satisfied, transfer the build directory to the other systems by whatever means appropriate (or make it available via NFS) and just install it from there (make install). It should not attempt to recompile or relink anything since all of the binaries are already present.