This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: libiconv
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin-apps at cygwin dot com
- Date: Wed, 10 Jul 2002 21:48:44 -0400
- Subject: Re: libiconv
- References: <FAC87D7C874EAB46A847604DA4FD5A64207648@crtsmail.corp.riotinto.org> <20020625012221.GF32490@redhat.com> <3D184AE8.7030205@netscape.net> <20020710214400.GA15170@redhat.com> <3D2CB8AB.8030504@ece.gatech.edu>
- Reply-to: cygwin-apps at cygwin dot com
On Wed, Jul 10, 2002 at 06:43:55PM -0400, Charles Wilson wrote:
>Christopher Faylor wrote:
>
>>[Cleaning out my mailbox]
>>On Tue, Jun 25, 2002 at 06:50:16AM -0400, Nicholas Wourms wrote:
>>
>>>Now you can link gcc against libiconv ;-).
>>>
>>
>>FWIW, I hope I have done this. I added the libraries in the hopes that
>>the gcc configury would find it. How do we determine if it worked?
>
>
>Well, it's obviously not linked in dynamically (which is probably good
>-- I think we want gcc to be static, except for cygwin1.dll).
I just realized that it was pretty easy to check. I just have to look at
the build logs. Nope. No -liconv. After "all that trouble" to install
it, gcc only randomly detected it in certain directories.
I don't think I'll make this a priority for the testing releases but I'll
see if I can tweak something for the real release.
cgf