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: Mon, 19 Jul 2004 10:45:05 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Problem with echo in tcsh 6.13.00-2 in Cygwin 1.5.10 (fwd) Message-ID: <20040719084505.GB11473@cygbert.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On Jul 16 15:41, David Mastronarde wrote: > I already indicated that the problem will not appear when the program is > compiled with g77. I would be glad to send you the program compiled with > the Intel compiler, but a statically linked version of even such a simple > program is 245K and only compresses to 115K, so I was not able to send it > to this list. Is there another address that will accept this file? So it's a native Windows application which fails, not a Cygwin application. I missed that detail. Consequentially I tried to call notepad and write in that script instead of calling ./fortopen. Works nicely. So I'm wondering why you think that this is a bug in tcsh and not a bug in the intel fortran libs. However, you could try a recent Cygwin snapshot from http://cygwin.com/snapshots/ and see if the problem is solved. If not, you'll probably have to debug that problem. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:cygwin@cygwin.com Red Hat, Inc. -- 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/