I have a few resources that I have read that show what I need, openSSL and zlib of one version or another to get openSSH to work to start.
Here is my dilemma to start, I will need to compile the source for the openSS* and the zlib, but when I type "make" into the command prompt I get "make: not found". There is also no man pages for it either, the make anyways.
I have all of the source downloaded and can move it to the SCO box, but if I don't have make, what would I do with it? Should I get GNU C++ compiler? This is the first hurdle. I also have to do this for 5.0.5, 5.0.4, and I think older like 5.0.2 or something.
Does anyone have any suggestions on what I should be doing with the source, or if there is distribution from SCO for openSSH, openSSL, or zlib. (I don't have any contact with SCO without payment and it has never been approved any other time I have asked for it.) But I was thinking zlib or an equivalent was already on the SCO boxes, or at the very least got that impression when I was reading the documentation on zlib its variants and stuff like that. So I might not need that program "zlib", but it would be great to know.
Is there something I can add from the SCO install CD ROM to accomplish some if this, I have read about some 5.0.7 updates that have older or compatible system files in them for this sort of thing.
Do you have the development system installed?
I did this installation about 3 years ago.
Even if you install the gcc environment, I am not sure that the linker is available.
However with gcc you can try gmake instead of make, and probably will have to hack the make file to change CC to GCC
You might consider upgrading to 5.0.7 as ssh is included.
The development system is on the base OS cd, and can be installed for 60 days. The last price I saw was about 1200.US
I found through google.com and then the old Caldera Skunkware site where to get GNU CC, and GNU make, along with other toys like the CD recorder someone else was looking for on here a while ago, it is also on the SCO/Caldera SKunkware website:
Anyways, I used `custom' and got that stuff installed, but the files for zlib and openSSL come as *.gz!?!?! What the do I use for those, for now I am going to try using WinRAR on my laptop and get them to just *.tar files and go from there. Hopefully there is nothing I need to worry about there.
Update 4/26/2007
Never mind I figured out it was gzip, or GNU ZIP, and added nearly every GNU tool on the Skunkware CD that I could find just for good measure on our test box.
Update 4/27/2007
I have GCC and the other stuff needed in the test system now. But, really since I taught myself from the Internet and man pages I am kind of at a loss for what to do now. The zlib stuff seems to be header files, so I am assuming they are not going to get compiled, or so GCC tells me. So should they be included in a "make" for openSSH?
As I recall, the zlib stuff is copied into the ssh source directory into a directory called zlib.
Then run make |gmake | and watch for errors, there is lots of output, you may find redirecting it to a file is useful.
When there are no more errors, run "make install".
I am getting the impression that make is a building tool. I get the impression that I put all of the files into a directory that are needed, and then use make or gmake, switching the "cc" to "gcc", and running until no more errors with all of the zlib and openSSL software with the openSSH software in a directory.
The header files are just directives, data structures etc., and they should be included in the directory when the compiling/make happens. I got that out of a SCO programming guide circa 12/10/1991 for SCO System V/386, don't I feel spiffy, that's my docs. (Part number AU01404P001)
Thanks jgt for the advice, I will mess with it on Monday again, I had gotten distracted with Windows virii issues at customers.
Forgot to mention that there is a script called configure in the root directory of the ssh distribution. Run it './configure' and it will run a series of tests to determine which compiler you are using, and which libraries you have available and whether your system is 'big endian' or 'little endian'.
I am getting back onto this project for a little while again, interruptions happen constantly, and have installed the development system from the base CD. Hopefully this will work better for me.
All I have to do I think is get this one done and then deploy it. Or at least I hope, if I get this done do you jgt, or anyone else, know if I can just tar the directory and place it into a new system? Or would I have to go through this process everywhere? Now that I think about it all of the system hooks would have to be recreated...would it be something that I could package and load through scoadmin?
I have found a something packaged online already but don't trust it. Has anyone downloaded a complete version that is already finished and packaged?
After you have finished making the source distribution:
Tar the entire directory structure (about 100mb) and copy it to the other machines maintaining the complete path , then on these machines just run 'make install'.
We are moving everything to SCO OpenServer 5.07. Some locations have the software already. It is installed in the initial setup also. This also gives us the chance to implement other technologies also right away.