public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: autoreconf/gettext puzzle (was Re: sed match DOS end of line)
Date: Thu, 27 Jun 2013 15:55:00 -0000	[thread overview]
Message-ID: <20130627155133.GF2378@calimero.vinschen.de> (raw)
In-Reply-To: <51CC5D69.40700@users.sourceforge.net>

On Jun 27 10:42, Yaakov (Cygwin/X) wrote:
> 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.

Yeah, I seem to be entirely on the wrong track, sorry about that.

I'm just inspecting the sources and it seems that the read mode of
files has changed from "rt" to "r" between 4.2.1 and 4.2.2 for some
reason.

I'm still digging, and I'm unsure how I could create a version of
sed 4.2.2 which did the right thing at all a couple of minutes ago.

Still digging...


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

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

  reply	other threads:[~2013-06-27 15:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 14:24 sed match DOS end of line Paul Becker
2013-06-27 14:49 ` Corinna Vinschen
2013-06-27 15:16   ` autoreconf/gettext puzzle (was Re: sed match DOS end of line) Corinna Vinschen
2013-06-27 15:42     ` Corinna Vinschen
2013-06-27 15:51     ` Yaakov (Cygwin/X)
2013-06-27 15:55       ` Corinna Vinschen [this message]
2013-06-27 17:31         ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130627155133.GF2378@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).