Problems with sftp under SCO OpenServer (fwd)

[mouring at etoh.eviladmin.org]

This is the final results of sftp on SCO OpenServer.

---------- Forwarded message ----------
Date: Mon, 26 Feb 2001 12:27:51 -0700
From: Greg Jewell <gjewell at cnnxn.com>
To: mouring at etoh.eviladmin.org
Subject: RE: Problems with sftp under SCO OpenServer



> -----Original Message-----
> From: mouring at etoh.eviladmin.org [mailto:mouring at etoh.eviladmin.org]
> Sent: Monday, February 26, 2001 12:53 PM
> To: Greg Jewell
> Subject: RE: Problems with sftp under SCO OpenServer
> 
> 
> 
> > I downloaded today's snap, and placed #undef HAVE_SNPRINTF 
> and #undef
> > HAVE_VSNPRINTF in the openbsd-compat/bsd-snprintf.c file.  When I
> > compiled this and connected to the system, everything looked good...
> > 
> <grumble>  That is what I was afraid of.
> 
> Is 'llu' even valid under SCO's snprintf?
> 
> - Ben
> 
> 

With SCO's "native" development kit, it is not.  With the newly released
UnixWare and OpenServer Development Kit, it is.  Right now, gcc is
configured to look into /usr/include /usr/lib, etc. which is where the
native development environment resides.  I am not certain how to change
this to /udk/usr/*, which is where the new development kit resides.

Even if gcc can be reconfigured to look into these new directories by
default, though, I don't know whether it would break something else.
The gcc package for OpenServer was built with the older libraries in
mind.