FreeTDS Development Group

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

Well, Debian will already need special handling for FreeTDS in that case,
since all our other libs already contain rpath information.  In some cases
this would also seem to be true for ODBC, by accident, even without my
patch.  For instance, if you happened to use --with-iconv and your iconv
libraries happened to be in the same directory as your ODBC libraries, then
your odbc libraries would get the rpath information anyway.  My patch just
ensures that we handle odbc in a manner consistent with our other libraries.
It's committed now, by the way.

I do understand why Debian wouldn't want build staging directory paths in
their distributed libraries.  But I think that's an issue for the libtool
people to hash out, not us :-)

Cheers,
--nick

-----Original Message-----
From: bounce-freetds-145195 AT franklin.oit.unc.edu
[mailto:bounce-freetds-145195 AT franklin.oit.unc.edu] 
Sent: Thursday, October 03, 2002 3:06 PM
To: TDS Development Group
Subject: [freetds] RE: unixodbc library pickup


On Thu, Oct 03, 2002 at 02:30:23PM -0400, Castellano, Nicholas wrote:

> I agree with Merijn.  I'm not really sure that Steve disagrees, I 
> think he's just griping about how much ELF sucks (and I'd have to 
> agree with that).

No, I've always found ELF more than sufficient for my needs; it's libtool
that I'm specifically griping about. :)  Debian packaging policy
specifically prohibits the use of rpath in ELF binaries, because it's an
additional lookup that's always either redundant or wrong.  (Policy also
requires all our libs to be in certain directories within the library path).
Libtool is great about setting rpath when installing sources into the
packaging directory, which means binaries end up with an rpath encoded that
points to a directory that only exists on the machine of the person building
the package. :P

Steve Langasek
postmodern programmer


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.