Skip to Content.
Sympa Menu

freetds - RE: [freetds] excluding libiconv

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: 'FreeTDS Development Group' <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] excluding libiconv
  • Date: Wed, 6 Aug 2003 10:13:13 -0400

> From: Alex Kiesel [mailto:alex.kiesel AT document-root.de]
> Sent: August 6, 2003 2:20 AM
> On Wed, 2003-08-06 at 07:19, James K. Lowden wrote:
>
> > I think I found the road to *preventing* linking with
> > libiconv. It's
> > something Bill asked about a few weeks back.
...
> > Once I work out the actual syntax, you could
> >
> > ./configure --without-libiconv
> >
> > and pick up the built-in replacement instead.
>
> I'm just curious and seem to have missed the discussion: Why
> do you want to remove libiconv?

I don't. :-)

Not everyone needs libiconv, and it should be possible to use FreeTDS
without it. The releases never required it, but there were a few months
recently when the CVS version did. That's fixed now.

Bill Thompson doesn't need libiconv, but found that 'configure' links it in
if it discovers it on his box. He'd like to defeat that, because he's doing
binary builds for his firm and doesn't want to introduce a downstream
runtime requirement. That's our motivation here.

By default, configure will use libiconv if it finds it. You can help it
find it using --with-libiconv-prefix. Soon, you'll be able to exclude it
using --without-libiconv. At least, that's the plan.

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