Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Tue, 7 Jan 2003 15:04:56 +0100 From: Corinna Vinschen To: Cygwin Users List Subject: Re: sed -i problem? Message-ID: <20030107150456.B14974@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: Cygwin Users List References: <200301031627.h03GRTRQ020947@wolf.cimsoft.com> <002301c2b3eb$b9adb250$9b1e1897@bonz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002301c2b3eb$b9adb250$9b1e1897@bonz> User-Agent: Mutt/1.3.22.1i On Sat, Jan 04, 2003 at 01:20:51PM +0100, Bonzini wrote: > Ok, I tracked down the problem and it is because fopen is used for the file > instead of ck_fopen. Alas I don't have a patch ready (a nice solution would > be practically the diff from 4.0.5 to 4.0.6), but grepping for [^_]fopen.*"w > and replacing fopen with ck_fopen will probably be a quick, workable hack. Thanks for tracking this down, I'll upload a new version of sed soon. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/