DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=LFrVxpKR6o3nn2Sn+C5ivS0LbctXG+KzMm8IeKmDG9s
	yRSumsVzFD+VpbE2NHveTSYFxRXchCuGs8c374Wa5u9fH1Edvt7BVKqpDZfZ1OsF
	HVSR64RJ/LSWSsKEH2ShCj7zbtddIL8LoQLeLmedTQlbFLXuOv6QfgVCdpjt0u1U
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <51CC5D69.40700@users.sourceforge.net>
Date: Thu, 27 Jun 2013 10:42:33 -0500
From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: autoreconf/gettext puzzle (was Re: sed match DOS end of line)
References: <01E9402441FFBB4BBEA0A82549A7D94A0C27C5@ORD2MBX02C.mex05.mlsrvr.com> <20130627142405.GA2378@calimero.vinschen.de> <20130627144952.GB2378@calimero.vinschen.de>
In-Reply-To: <20130627144952.GB2378@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 2013-06-27 09:49, Corinna Vinschen wrote:
> Ok, here's me, even more puzzled.  FIW, the 4.2.2 packages have *not*
> been built the same way as the 4.2.1 package.  The difference is running
> autoreconf (4.2.2) vs. not running autoreconf (4.2.1).

Were these natively compiled or cross-compiled?  The latter pulls in 
gnulib functions in place of libc's (Cygwin) without intervention during 
configure.

> If I build sed with the auto configury unchanged, I'm back to an sed
> which handles the CR just as the old sed 4.2.1 package:
>
>    $ sed --version | head -1
>    sed (GNU sed) 4.2.2
>    $ od -c eol
>    0000000   e   n   d   o   f   l   i   n   e  \r  \n
>    0000013
>    $ sed 's/e$/X/' < eol
>    endoflinX
>
> However, 4.2.2-1 and 4.2.2-2 packages have been built running autoreconf
> first, which, besides other things, updates the included gettext stuff
> from version 0.17 to version 0.18.1.
>
> So I'm wondering if the latest gettext is the culprit here, but I'm not
> fluent enough in the differences within gettext to see where the problem
> is.

I doubt it; as long as libintl is dynamically linked, the gettext build 
infrastructure just handles .po.mo rules.


Yaakov


--
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