FreeTDS Development Group

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

Can you post a complete log of the build?  That would be useful in
identifying what symbols are multiply defined, and might help point us
towards a fix.

Cheers,
--nick

-----Original Message-----
From: bounce-freetds-145195 AT franklin.oit.unc.edu
[mailto:bounce-freetds-145195 AT franklin.oit.unc.edu]
Sent: Tuesday, October 15, 2002 2:26 PM
To: TDS Development Group
Subject: [freetds] Re: Shared libs on Mac OS X Server 10.2

I was following a previous suggestion that re-libtoolizing (which then
prompted me to re-aclocal etc) might solve the problem of not being able to
make the shared libraries on os x.  I have since gone ahead and installed
autoconf 2.54 and it does now correctly recognize the ability to build
shared libs and attempts to build them but fails with multiply defined
symbols.  As I stated in the beginning I only know enough to get myself into
trouble, but since I am stuck until I get this working I have plenty of time
to learn.  I tried adding -multiply_defined suppress to the LDFLAGS, but
that doesn't appear to have been the correct location since I still get the
same error (but can see that my flag was added in other locations).

thankyou for all of the assistance and putting up with a novice.

john michael

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