Re: sed: 4.1.5 breaks libtool generation

[Pavel Holejsovsky <pavel dot holejsovsky at upek dot com>]

Corinna Vinschen wrote:
> On Feb 24 04:01, Charles Wilson wrote:
> > Yaakov S (Cygwin Ports) wrote:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > After a recent update to my Cygwin installation, suddenly
> > > configure-generated libtool scripts give me this error when compiling
> > > and linking C++ code:
> > >
> > > libtool: ignoring unknown tag CXX
> > >
> > > And even worse, it tries to use gcc to link, which of course fails
> > > because of undefined symbols provided by libstdc++.
> > >
> > > Using the /usr/bin/libtool instead works, so this would seem to be
> > > caused during the generation of the package libtool.
> > >
> > > So I guessed that the sed update was the problem, and I was right.
> > > Downgrading sed to 4.1.4-1 makes everything work again.
> > >
> > > I'm attaching my cygcheck output (before I downgraded sed).
> > Thanks for the heads up. I'll try to look in to it, but it might be a 
> > week or two.
>
> I would appreciate any hint here.  sed 4.1.5-1 has 0 FAILs in the sed
> testsuite and the only really interesting Cygwin related difference 
> between 4.1.4 and 4.1.5 is that 4.1.4 uses sed's own implementation
> of getline(), while 4.1.5 uses the newlib version of getline.

One incompatibility of 4.1.5 is that sed no longer works correctly with 
CRLF-style files on binary mounts.  For example, 's/^$//' script no 
longer filters out empty lines if they are CRLF terminated, but works OK 
for LF terminated lines.  However, I'm not sure whether this causes the 
problem described above.

Pavel


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