This is the mail archive of the cygwin-apps@cygwin.com mailing list for the Cygwin project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: libiconv

From: Charles Wilson <cwilson at ece dot gatech dot edu>
To: cygwin-apps at cygwin dot com
Date: Wed, 10 Jul 2002 22:15:36 -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> <20020711014844.GA17469@redhat.com>


Christopher Faylor wrote:

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 haven't looked at the gcc-3.1.1 source tree, but I know that gcc does weird things with autoconf (e.g. top-level configure.in is NOT an input to autoconf...). Anyway, my point: the "real" gettext.m4 from gettext-0.11.2 seems to have the appropriate code in it to check for both -lintl and -liconv if appropriate.

Does gcc-3.1.1 use aclocal.m4/gettext.m4 to find gettext, or some homebrew stuff?

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.


That's reasonable.

--Chuck

Follow-Ups:
- Re: libiconv
  - From: Christopher Faylor

References:
- Re: libiconv
  - From: Christopher Faylor
- Re: libiconv
  - From: Charles Wilson
- Re: libiconv
  - From: Christopher Faylor

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]