Re: [cobalt-users] giving up - trying to do ftp security

[Jim Dory <jdory@xxxxxxxxxxxxxx>]

Open note for the archives to anyone trying this, with hopes you have 
better luck. I'm sure people more versed in linux will have success. I 
did learn a few things so it was not a total waste of time.

> Jim Dory wrote:
>
> > I tried to install the following rpms to compile proftpd hardened and 
> > now I can't compile: I get errors: "checking whether C compiler 
> > works... configure: error: cannot run C compiled programs."
> >
> > I think I just need the right symlink in there somewhere, probably 
> > from /usr/bin/gcc. Gcc does not exist there though. I don't know what 
> > to have point to where.  Anyone tell me what to use for a link and 
> > where to put it? Sure appreciate it.
> >
> >
> > # rpm -Uvh 
> > ftp://ftp.cobalt.sun.com/pub/products/raq550/RPMS/sg-cpp-1.1.2-30_SG201_cobalt.i386.rpm 
> >
> > # rpm -Uvh 
> > ftp://ftp.cobalt.sun.com/pub/products/raq550/RPMS/sg-egcs-1.1.2-30_SG201_cobalt.i386.rpm 
>
> Ok, I found gcc in /usr/sg/bin/ so I did a ln -s /usr/sg/bin/gcc 
> /usr/bin/gcc. Hopefully this is right. It compiled no problem, I 
> believe. On to the next step..
Next problem was I got the configure to work though there were some 
errors in the config.log, mostly:
"failed program was: /* confdefs.h. */, and a few missing files.

Then I tried make, and got missing files for /openssl/include.. So I 
tried creating a symlink to where they exist, was unable, so just copied 
those missing files to the expected directory (which I created): 
/usr/local/openssl/include and /usr/local/openssl/lib.

Then I did a

./configure --with-modules=mod_tls \
   --with-includes=/usr/local/openssl/include \
   --with-libraries=/usr/local/openssl \
   --prefix=/usr --sysconfdir=/etc

and the missing files error went away but now I get a 
"make[1]: cc: Command not found" at the end of the make
process. Searching google, they all
say to install gcc and a libdev6, but that would defeat the purpose
of the stackguard egcs install. 

I've spent enough time, unless someone spots an easy 'fix'. I'll continue on with unsecured ftp, using the hosts.allow and hosts.deny files.

cheers, Jim D.