Mike et al,
I want to be able to automate the installation of stunnel in the same
manner that I've already automated our openssh installation, however,
I've run into a problem (lack of knowledge) with the "make install"
step.
This is for Solaris (2.5.1 to 10) and AIX (5.1 to 5.3). I'm not quite
ready to create the packages in either Solaris (pkg) or AIX (rpm)
formats.
At a high level, here is what I would like to achieve:
- On a build server (per OS version)
- transfer all of the necessary stuff (gcc, openssl, stunnel
source,
etc.)
- install the necessary stuff (gcc, openssl, etc.)
- un'tar the stunnel package
- run configure (with the appropriate options and paths)
- run "make"
- tar the stunnel directory & transfer it to a holding system
- Put together the necessary pieces on the holding system to install
stunnel
on all targets.
- On a target system (per OS version)
- transfer all of the necessary stuff (libgcc, openssl, tar'ed
stunnel
directory, etc.)
- install the necessary stuff (libgcc, openssl, zlib, etc.)
- un-tar the stunnel file
- run "make install"
Using the same flow with our openssh packages, I do not have to install
a compiler (gcc) and its support packages.
What, if anything, can I do with the stunnel installation to not have to
install a compiler?
Regards,
John Boxall
