Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <4021BB81.2080200@cwilson.fastmail.fm> Date: Wed, 04 Feb 2004 22:41:53 -0500 From: Charles Wilson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030630 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: iconv support not detected by configure when using gcc-3.3.1-3 References: <87ptcvxbb0 DOT fsf AT vzell-de DOT de DOT oracle DOT com> In-Reply-To: <87ptcvxbb0.fsf@vzell-de.de.oracle.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Dr. Volker Zell wrote: > Now I'm wondering how the iconv support in the original build could *EVER* > be detected ? because these symbols do not seem to be defined in the library. > > > By the way the same problem exists when trying to build TeXmacs (see the > discussion on cygwin-apps). The discussion there reminds me that I used > gcc-3.2-3 for my original build whereas now I have gcc-3.3.1-3 > > > Is this a know issue ? Does anybody has any clue what's going on here. > This is thanks to the new iconv support in newlib. Even tho it is "turned off" in cygwin-1.5.7, the new cygwin package still installs its own version of /usr/include/iconv.h -- and the "new" version is not, of course, recognized as GNU iconv. Short-term solution: reinstall 'libiconv' Medium-term solution: next cygwin release, if it still does not use newlib's iconv, should also _not_ include newlib's iconv.h Long-term solution: we really really need a package linter that detects file conflicts like these BEFORE they lead to wierd problems. Any volunteers? -- Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/