Skip to Content.
Sympa Menu

freetds - RE: [freetds] fd_Set -parse error

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] fd_Set -parse error
  • Date: Mon, 27 Oct 2003 10:05:54 -0500

> From: Swapna_Anand [mailto:Swapna_Anand AT Satyam.com]
> Sent: October 27, 2003 7:30 AM
>
> Jkl- Thanks for the reply. "Man fs_set" does not find an
> entry in Interix.
...
>
> in "configure" giving the following errors
>
> Making all in unittests
> if /bin/sh ../../libtool --mode=compile gcc -I. -I. -I../../include
> -I../..
> clude -D_ALL_SOURCE -D_FREETDS_LIBRARY_SOURCE -DTDS50 -Wall
^^^^^

I don't trust this output, Swapna. Unless you really have a "clude"
directory, it looks some characters got dropped while cutting and pasting.
However, it's clear that "configure" is failing to detect your headers:

> exit 1; figcc -I. -I. -I../../include -I../../include -D_ALL_SOURCE
^^^^^ is that right?
> -D_FREETDS_LIBRARY_RCE -DTDS50 -Wall -Wstrict-prototypes
> -Wmissing-prototypes -D_ALL_SOURCE -MT
> in.lo -MD -MP -MF .deps/login.Tpo -c login.c -o login.o
> login.c: In function `tds_set_server':
> login.c:143: warning: implicit declaration of function `strlen'

These "implicit declaration" warnings indicate that gcc (or what is your
compiler?) hasn't included the file with the function's prototype. In this
case, string.h. Interix may have its quirks, but I'm sure it has an include
file for strlen(3)! My guess is you have to twiddle with your CFLAGS to
tell configure where your include files are.

If that's not enough, I'd like to see the output from configure. You might
try posting the first 200 lines or so here, but if the problem isn't
obvious, it would help to see the whole thing. You'd have to post the
results on a webserver somewhere, or upload them as a "patch" on source
forge, because the output will be voluminous.

1. the complete output of "./configure" (plus whatever swithes you're
using).

2. edit the configure script, inserting this line very near the top:

set -x

and rerun as before. That will cause each statement to be echoed before
it's executed.

Best is to use nohup(1) or script(1) to capture all the output. For each
case, I'd like to see the output and the resulting config.log.

HTH.

--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