Re: libiconv-prefix seems broken

Frediano Ziglio <[email protected]>
Newsgroups gmane.comp.db.tds.freetds
Message-ID <[email protected]>
2011/2/18 RR <[email protected]>:
> On Fri, Jan 9, 2009 at 3:11 AM, Wood, David <[email protected]> wrote:
>
>> >From my generated config.rpath:
>>
>>    master.nyc:/tmp/usr/local/pkg/freetds > egrep '^shrext|^shlibext="'
>> config.rpath
>>    shrext=.so
>>    shlibext="$shlibext"
>>
>> So - config.rpath is quite important since it sets shlibext for
>> configure!  Now I'll build with a valid config.rpath:
>>
>>
> Hello, this thread is a bit old  but I haven't needed to compile or use
> FreeTDS for 2 years or so now. Now that I have to, I downloaded the stock
> "freetds-stable" which opens up to freetds-0.82 and I'm still getting this
> config.rpath error in configure. I am not a programmer by a long shot so I
> have no idea how to "generate" my own config.rpath. Can someone help??
>
>
>>    /tmp/freetds > ls config.rpath
>>    config.rpath
>>    /tmp/freetds > ./configure --with-libiconv-prefix=/usr/local/gnu
>>    ...
>>    /tmp/freetds > grep '^LIBICONV' config.log
>>    LIBICONV='/usr/local/gnu/lib/libiconv.so -R/usr/local/gnu/lib'
>>
>> Voila - GNU libiconv is being used!
>>
>> BTW - freetds-0.83.dev.20090104 seems to include config.rpath:
>>
>
> Does that mean I have to download a snapshot / current trunk/branch etc. to
> make this work?
>
>
>>
>> > You should see the change in tomorrow's CVS HEAD
>> > snapshot.  If that works for you, I'll do the same
>> > thing to the 0.82 branch.
>>
>>
> I'm assuming this never got put into the 0.82 branch as the stable/default
> download package doesn't have it?
>
> Thanks
> \RR

Use official patched version at http://freetds.sourceforge.net/. It
fixes this and other problems

bye
  freddy77
_______________________________________________
FreeTDS mailing list
[email protected]
http://lists.ibiblio.org/mailman/listinfo/freetds
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.