Skip to Content.
Sympa Menu

freetds - RE: configure.in check for long long

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: ZIGLIO Frediano <Frediano.Ziglio AT vodafoneomnitel.it>
  • To: "'TDS Development Group'" <freetds AT franklin.metalab.unc.edu>
  • Subject: RE: configure.in check for long long
  • Date: Fri, 9 Aug 2002 14:19:49 +0200


>
> You mean that configure tells you have no __int64? That would
> be normal.
>
> My configure output shows
>
> checking size of long long... (cached) 8
> checking size of __int64... (cached) 0
>

0 mean that __int64 type do not exist. (cached) mean that you exec configure
without deleting config.cache... some problem can raise.

I note in configure.in this code

case 8 in
$ac_cv_sizeof_long) int64=long;;
$ac_cv_sizeof_long_long) int64="long long";;
$ac_cv_sizeof___int64) int64=__int64;;
esac

if test "$int64"; then
AC_DEFINE(HAVE_INT64)
else
int64=long
fi

If you have not a 64bit int why you define int64 to long? This can cause
some problems. Perhaps is best to define int64 as a struct like
struct {
TDS_UINT low;
TDS_INT high;
} int64;
for little endian and
struct {
TDS_INT high;
TDS_UINT low;
} int64;
for big endian
This also prevent compilating of bad code.

> is that what you mean, or something different? I guess i need more
> specifics ;-)
>
> Brian
>
freddy77

=================================
"STRICTLY PERSONAL AND CONFIDENTIAL

This message may contain confidential and proprietary material for the sole
use of the intended recipient. Any review or distribution by others is
strictly prohibited. If you are not the intended recipient please contact
the sender and delete all copies.
The contents of this message that do not relate to the official business of
our company shall be understood as neither given nor endorsed by it."

=================================




Archive powered by MHonArc 2.6.24.

Top of Page