Mailing-List: contact apache-bugdb-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: apache-bugdb@apache.org
From: TOKILEY@aol.com
Message-ID: <ad.22ddf71.2725ebe2@aol.com>
Date: Mon, 23 Oct 2000 15:30:42 EDT
Subject: Re: config/6726: Configuration files
To: apache-bugdb@apache.org
CC: eyal.shaynis@iname.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit


You should not have to 'fix' 50 text files. No way.

It sounds like you GZIP'ed a copy of the Windows source
tree, moved it to UNIX and then 'gunzipped' it, or something.

That's the only time you should see the problem(s) you are reporting
with wrong UNIX/Windows EOL characters in the text files.

If not... are you sure you aren't missing the right TERM statement
in your SunOS 5.8 shell?

Maybe you need to do an 'export -p TERM=vt100' or something
before you run your text editor on the UNIX side.

Yours
Kevin Kiley
CTO, Remote Communications, Inc.

Original message...

>Environment:
SunOS olimpus 5.8 Generic_108528-02 sun4u sparc SUNW,Ultra-60
>Description:
The source configuration files & the Makefile output is in DOS/Windows format,
Which means they end with ^M in the unix environment.
They are also not in the correct mode (755).
After fixing about 20 files, I need to manualy edit about 30 Makefiles.