From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Edwards To: Bart Veer Cc: ecos-discuss@sources.redhat.com Subject: Re: [ECOS] CR's in build tree under Cygwin? Date: Wed, 25 Oct 2000 07:18:00 -0000 Message-id: <20001025091822.A4938@visi.com> References: <20001024201936.A12283@visi.com> <200010251243.e9PChpb06732@sheesh.cygnus> X-SW-Source: 2000-10/msg00300.html On Wed, Oct 25, 2000 at 01:43:51PM +0100, Bart Veer wrote: > Grant> Do people usually have their build trees mounted in "text" > Grant> mode under Cygwin? > > Grant> [I had assumed that they should be mounted in binary mode > Grant> since the arm-elf tools built more easily that way...] > > No. eCos build trees have to be on drives mounted in text mode. This > is documented behaviour. The problem is that there are some files in > the build tree, e.g. the ecos.ecc savefile, which users will want to > edit. We cannot mandate cygwin-aware editors, e.g. some people might > want to use notepad. Hence the files need to contain cr/lf pairs. Thanks. That's what I expected, but I wanted to make sure. I must have missed the mention of text mode in the docs. > Work has been done on some of the tools, e.g. gcc and (I thought) > make, so that they just ignore spurious carriage returns. It might not actually be make's fault. The last time I tracked down one of these problems it turned out that a file included by a makefile was generated by a shell-script, and the CR somehow confused the shell script that generated that file. > It is a shame that there are still operating systems out there which > insist on using two characters to mark the end of a line. I believe > Unix systems have managed with just a single character since 1969 or > so. I'm sure it all goes back to either something in DEC RSX-11 or something in Gary Killdall's childhood. ;) -- Grant Edwards grante@visi.com