Skip to Content.
Sympa Menu

freetds - RE: [freetds] Compiling freetds 0.61 source in cygwin

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: "'FreeTDS Development Group'" <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] Compiling freetds 0.61 source in cygwin
  • Date: Fri, 25 Apr 2003 11:15:14 -0400

> From: Anthony Kong [mailto:anthony.kong AT ufjia.com]
> Sent: April 25, 2003 12:21 AM
>
> When I run ./configure, I encountered the error message:
>
> [snip]
> checking size of char...
> checking for short... yes
> checking size of short...
> checking for long... yes
> checking size of long...
> checking for int... yes
> checking size of int...
> checking for float... yes
> checking size of float...
> checking for double... yes
> checking size of double...
> checking for long double... yes
> checking size of long double...
> checking for long long... yes
> checking size of long long...
> checking for __int64... no
> checking size of __int64... 0
> configure: error: No 16-bit int found.
>
> How can I get around this problem? The version of cygwin is
>
> CYGWIN_NT-5.0 WS054 1.3.15(0.63/3/2) 2002-11-06 22:41 i686 unknown

Nothing leaps out at me, Anthony. The message implies that the "short" type
isn't 16 bits, which if course it is....

Let's start with something simple. What says "grep -i short
include/config.h"? I get:

/* The size of a `short', as computed by sizeof. */
#define SIZEOF_SHORT 2

Also, does config.log offer any hint?

--jkl


The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that we do not accept account orders and/or
instructions by e-mail, and therefore will not be responsible for carrying
out such orders and/or instructions.





Archive powered by MHonArc 2.6.24.

Top of Page