Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-Id:	<4.3.1.2.20001116123514.00b900f8@pop.ma.ultranet.com>
X-Sender:	lhall AT pop DOT ma DOT ultranet DOT com
X-Mailer:	QUALCOMM Windows Eudora Version 4.3.1
Date:	Thu, 16 Nov 2000 12:39:58 -0500
To:	Armin Theissen <Armin DOT Theissen AT ireland DOT sun DOT com>,
	cygwin AT sourceware DOT cygnus DOT com
From:	"Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject:	Re: sed and find
In-Reply-To:	<200011161653.QAA25955@ireserver.Ireland.Sun.COM>
Mime-Version:	1.0

At 11:53 AM 11/16/2000, Armin Theissen wrote:


>Hi, 
>
>I'm new to this list and to cygwin in general, and I have a problem 
>which I cannot find discussed anywhere on the faq or mailing list 
>archive. 
>
>its about the commands 'sed' and 'find'. I used the cygwin_b20 and 
>their sed and find therein with no problems, but the obviously 
>different sed and find in cygwin 1.1.4 gives me compile errors. 
>
>sed complains about unterminated 's' commands, as in 
>   sed "s/bla/blubb/"
>which can there be solved by removing the quotation marks. However, 
>in order to expand complicated s/// expressions when compiling under 
>non windows plattforms, I cannot simply remove them all in the (huge) 
>code.  Is there a way to make sed in cygwin 1.1.4 understand the 
>quotation marks? 
>
>Another cause for headaches is 'find' which just won't find anything but 
>complains about unfound files/directories - as it seems in the path 
>where to find. I assume there is a problem with slashes and backslashes. 
>Again, the find of cygwin b20 worked. 


Generally these kinds of problems are due to carriage returns in files,
although the bash and ash versions that come with 1.1.4 should be much better
at making this issue transparent.  Make sure you're up-to-date here.  The
more recent, the better!  As a last resort, you can certainly run your 
files through "tr" to remove the carriage returns.  To do further analysis
of your configuration, we'd need the output of cygcheck -s -r -v though.


>Is there any chance to get these working without copying over the old 
>versions? Or is this eventually a known bug for which there is somewhere 
>here a solution? 
>
>I hope there is. Otherwise: will cygwin_b20 still be available in the 
>future? 


Absolutely not.  B20 is unsupported now.


>cheers
>
>armin



Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -