X-Spam-Check-By:	sourceware.org
Date:	Fri, 24 Feb 2006 12:41:51 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: sed: 4.1.5 breaks libtool generation
Message-ID:	<20060224114151.GL4294@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<43FE1CEF DOT 9030905 AT users DOT sourceforge DOT net> <43FECB5A DOT 7060908 AT cwilson DOT fastmail DOT fm> <20060224094106 DOT GK4294 AT calimero DOT vinschen DOT de> <dtmpf1$o83$1 AT sea DOT gmane DOT org>
Mime-Version:	1.0
In-Reply-To:	<dtmpf1$o83$1@sea.gmane.org>
User-Agent:	Mutt/1.4.2i
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Feb 24 12:08, Pavel Holejsovsky wrote:
> 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.

sed's internal getline enforces CRLF line ending recognition regardless
of the mount type, which results in mishandling of binary input files.
sed has no -b/--binary option.  So by using newlib's getline which
doesn't enforce CRLF->LF conversion, sed 4.1.5 should be actually
"fixed", FWIW.  If you need CRLF->LF conversion, you can use a filter
application like dos2unix.

Nothing's impossible, but I'd be actually surprised if that's the cause
for the libtool misbehaviour.


Corinna

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

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

- Raw text -