I think we need to revisit the whole 64bit integer support.
It has crept from sftp over to scp now. And I think we are at a point
where
[..]
# If we don't have int64_t then we can't compile sftp-server. So
don't
# even attempt to do it.
if test "x$ac_cv_have_int64_t" = "xno" -a \
"x$ac_cv_sizeof_long_int" != "x8" -a \
"x$ac_cv_sizeof_long_long_int" = "x0" ; then
NO_SFTP='#'
else
should be changed to state 'Your platform is not supported with your
current compile.'
I don't think the scp.c can be done without 32bit without fear of
overflowing down the road.
Other than sco w/out gcc. What platforms does this affect? If it is just
sco. I really believe we need to make this move.
- Ben
On Mon, 17 Mar 2003, Ben Lindstrom wrote:> > I think we need to revisit the whole 64bit integer support.[snip]> should be changed to state 'Your platform is not supported with your > current compile.' > > I don't think the scp.c can be done without 32bit without fear of > overflowing down the road.Fortunately it only affects the -l (bandwidth limit) option now.> > Other than sco w/out gcc. What platforms does this affect? If it is just > sco. I really believe we need to make this move. > > - BenAny UnixWare < 7.0.0 But gcc is probably easily available for those. I'm OK with making this move. Doesn't anyone know of any code out there for using 64bit data types on machines that only support 32bit data types? But then it would have to be available under BSD license too. -- Tim Rice Multitalents (707) 887-1469 tim at multitalents.net
Hi, On Mon, Mar 17, 2003 at 09:30:43PM -0600, Ben Lindstrom wrote:> Other than sco w/out gcc. What platforms does this affect? If it is just > sco. I really believe we need to make this move.At least for SCO, requiring gcc would be fine. The original SCO CC is braindead anyway. gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany gert at greenie.muc.de fax: +49-89-35655025 gert.doering at physik.tu-muenchen.de