From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32252 invoked by alias); 28 Jan 2011 18:11:42 -0000 Received: (qmail 32244 invoked by uid 22791); 28 Jan 2011 18:11:42 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from out1.smtp.messagingengine.com (HELO out1.smtp.messagingengine.com) (66.111.4.25) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 28 Jan 2011 18:11:37 +0000 Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id D1574201E7 for ; Fri, 28 Jan 2011 13:11:35 -0500 (EST) Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 28 Jan 2011 13:11:35 -0500 Received: from [192.168.1.3] (user-0c6se63.cable.mindspring.com [24.110.56.195]) by mail.messagingengine.com (Postfix) with ESMTPSA id 7D4FF442397; Fri, 28 Jan 2011 13:11:35 -0500 (EST) Message-ID: <4D4306CE.4040006@cwilson.fastmail.fm> Date: Fri, 28 Jan 2011 22:13:00 -0000 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Bug in libiconv? References: <20110124154158.GA15279@calimero.vinschen.de> <4D3E3EF6.7010501@cwilson.fastmail.fm> <20110125111507.GA28470@calimero.vinschen.de> <4D3EE67D.3000900@cwilson.fastmail.fm> <20110125155053.GA6353@calimero.vinschen.de> In-Reply-To: <20110125155053.GA6353@calimero.vinschen.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2011-01/txt/msg00401.txt.bz2 On 1/25/2011 10:50 AM, Corinna Vinschen wrote: >>> Please note that I defined >>> __STDC_ISO_10646__ for Cygwin 1.7.8 yesterday. This define is >>> missing since 1.7.2. >> >> Hmmm...maybe I should (re)build libiconv against a snapshot? > > I think that should be safe. There's most likely no new API which would > accidentally be pulled in by libiconv(*). > > (*) Famous last words... Yep. The new fenv support causes applications to add a dependency (from their startup code?) to the new symbol _feinitialize. So, cygiconv-2.dll appears ok, but iconv.exe is not. -- Chuck -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple