FreeTDS Development Group

["Castellano, Nicholas" <Nicholas_Castellano AT acml.com>]

GCC will generate references to these functions for certain floating point
operations.  Normally the compiler will resolve these automatically from
libgcc.a during the final link phase.

Are you consistently using the same compiler for all your builds?  This type
of problem might turn up if, for example, you used gcc to build the
libraries but used a vendor cc to build your application.  In this case, you
would need to explicitly tell the vendor compiler to link with libgcc.a.

-----Original Message-----
From: bounce-freetds-145195 AT franklin.oit.unc.edu
[mailto:bounce-freetds-145195 AT franklin.oit.unc.edu] 
Sent: Wednesday, August 07, 2002 9:49 AM
To: TDS Development Group
Subject: [freetds] RE: must be getting tired - I need a holiday!


Hmmm.

Its not the unixodbc stuff as I suspected. 
Its convert.c
If I nm convert.o, I get this:

convert.o:

[Index]   Value      Size    Type  Bind  Other Shndx   Name

[80]    |         0|       0|NOTY |GLOB |0    |UNDEF  |__divdi3
[89]    |         0|       0|NOTY |GLOB |0    |UNDEF  |__eprintf
[90]    |         0|       0|NOTY |GLOB |0    |UNDEF  |__fixdfdi
[91]    |         0|       0|NOTY |GLOB |0    |UNDEF  |__fixsfdi
[72]    |         0|       0|NOTY |GLOB |0    |UNDEF  |__floatdidf

,,,,,

can anyone say what's causing this for me, and what library I now need to
link in ?

Bill




---
You are currently subscribed to freetds as: [Nicholas_Castellano AT acml.com]
To unsubscribe, forward this message to
$subst('Email.Unsub')


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 for certain accounts we do not accept
orders and/or instructions by e-mail, and for those accounts we will not be
responsible for carrying out such orders and/or instructions. Kindly refrain
from sending orders or instructions by e-mail unless you have confirmed that
we accept such communications for your account. Please also note that to
satisfy regulatory requirements we review the outgoing and incoming e-mail
correspondence of staff members serving certain functions.