Skip to Content.
Sympa Menu

freetds - FW: [freetds] Compiling on FreeBSD without ICONV

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: 'TDS Development Group' <freetds AT lists.ibiblio.org>
  • Subject: FW: [freetds] Compiling on FreeBSD without ICONV
  • Date: Mon, 9 Jun 2003 13:37:46 -0400

> From: Alan Pettigrew [mailto:freetds AT pettigrew.fsnet.co.uk]
> Sent: June 9, 2003 11:52 AM
>
> I had to add libraries libbind_r and libc_r
> before it would build, but it is now there.

I should have mentioned that the default is now multithreaded, too, which of
course is why you're pulling in the _r libraries. Apparently FreeTDS can be
compiled for with multithreaded support for FreeBSD, which is good, but it
seems we are not automatically linking in all the required libraries, which
isn't. :-( I wonder how we should fix that. Do you know?

For singlethreaded programs, we don't normally mention libc; it's included
among the linker's default libraries. Is the usual practice for
multithreaded programs in FreeBSD to mention libc_r explicitly, or is there
some shortcut that says "do the multithreaded thing"?

Either way, it looks like we'll have to adjust configure.in to generate a
configure script that will work out of the box for FreeBSD.

Thanks for the pr, Alan.

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