Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <38D033B6.22E64703@ece.gatech.edu>
Date: Wed, 15 Mar 2000 20:07:02 -0500
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: paul van der Meij <phjvdmeij AT wxs DOT nl>
CC: Chris Faylor <cgf AT cygnus DOT com>, cygwin AT sourceware DOT cygnus DOT com
Subject: Re: Re performance cygwin (o.a.)
References: <38D013F0 DOT F8E2319A AT wxs DOT nl>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

paul van der Meij wrote:

<SNIP>
> - the CYGWIN="binmode" environment variable seems to have no effect,
> probably caused by bash 2.03,
>   which I generated without changing anything after the 'configure'.
> Should it have anything special for cygwin??

I ran into this problem as well, with bash-2.03. I do not know if there
are any special compile-time directives that will correct this problem;
I reverted to the cygnus-distributed bash-2.02, which fixed the problem.

<SNIP>
> - Since these binary mounts the perl generation (make) comes in a loop
> during 'dllwrap' and 'dlltool'. I see
>   a growing number of ds01.0 ds02.o ..... files, and have to kill the
> 'dll' processes.
>   I did goto version 5.5.670 of perl, and made sure that there were no
> text files with embedded CR/LF,
>   since these behave strangely with binary mounts (at least sh scripts).

I haven't seen any of these problems, and I've built every perl from
5.5.640 to 5.6.0-RC1. Generating the initial perl.dll does take a long
time (3-4 minutes on my K6 200). Just let it run to completion?

> - the tar executable distributed with the recent snapshots does not
> behave well despite the binary mounts.
>         tar -cf - . | tar -tf -
>   produces a error, that disappears if I re-make the tar.exe from the
> distibuted cygwin-src

Are you sure this is not related to the binmode pipe problem you
described earlier?

--Chuck

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