FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> From: Harrison, Bruce (CXO) [mailto:Bruce.Harrison AT hp.com]
> Sent: December 9, 2002 1:36 PM
> 
>     I just saw it.  I pulled down the current snap-shot.  The problems
> with the configure script are solved, but I still get quite a few
> compiler warnings and errors.  

Hi Bruce, 

Well, I don't see any errors.  Does it run?  

There are a lot of warnings, most of which are harmless, some of which might
be OS-related:

$ grep line log |perl -pe 's/^.+# //' |grep ^Type |sort |uniq -c
  13 Types 'char *' and 'int' are not assignment-compatible.
  18 Types 'char *' and 'unsigned char *' are not assignment-compatible.
  12 Types 'const char *' and 'unsigned char *' are not
assignment-compatible.
  18 Types 'const unsigned char *' and 'char *' are not
assignment-compatible.
   2 Types 'int *' and 'unsigned long *' are not assignment-compatible.
   1 Types 'passwd *' and 'int' are not assignment-compatible.
  22 Types 'unsigned char *' and 'char *' are not assignment-compatible.
   1 Types 'void *' and 'int (*)(cs_context *,cs_clientmsg *)' are not
assignment-compatible.

The unsigned/signed warnings need cleaning up but are probably OK.  You tell
me if int* and unsigned long* are the same size.  But the char* and int
warnings could easily be trouble, if your OS returns a count and we expect a
pointer, or vice versa.  Those need careful examination.  

OTOH, if it compiles under GNU, I doubt the code is as broken as these
warnings seem to indicate.  I think it's more likely we're getting useful
information about nonfatal problems.  

It would help if you could look at the char*/int warnings especially, and
check what return type is defined for your system.  I will fix any genuine
problems (functional prototype differences) in the autoconf setup.   If you
don't mind recompiling every attempt, I think someone might be willing to
eliminate *all* the warnings.  (We also accept patches!)  :)

I don't understand why strtok_r is getting pulled in, because you haven't
configured for threadsafe operation.  

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