----- Original Message -----
From: "Earnie Boyd" <earnie_boyd@...>
To: "Luke Dunstan" <coder_infidel@...>
Cc: "mingw-msys" <mingw-msys@...>
Sent: Monday, May 13, 2002 7:34 PM
Subject: Re: [Mingw-msys] postinstall on Windows 9x
> Luke Dunstan wrote:
> > Hi,
> > Apparently Windows 98 cannot handle batch files with Unix line endings,
> > pi.bat does not work (it treats the three lines as one PATH command).
> Oh, yes, I forgot about that.
> > However, with DOS line endings I still get an "Out of environment space"
> > error, so perhaps the batch file needs to be launched differently (I
> > checked what Inno Setup allows yet).
> Are there command line options for setting environment space on child
> of command.com? Something like `command.com /e:4096'?
Yes, I have tried that switch and it works fine.
> > Also, msys.bat works because most lines
> > have CRLF, but a few of the comment lines have only LF, which is of
> > ignored by Win9x.
> I try to keep all lines \r\n formatted. I'll have to get in the habit of
> write.exe (aka WordPad) to write my .bat files. Hmm... I wonder if
> vim option to switch modes based on file extension? I'll have to look at
Are you implying that you use vim, or are you suggesting an option that I
could use? If you use vim in "vi compatible" mode (the default), it will
assume that all files are Unix so it would make editing DOS files difficult
and error prone. If this is how you use it, I strongly recommend setting the
"nocompatible" option in .vimrc so that the line endings are detected
automatically and preserved (along with enabling many other features). If
you do this, you can easily tell whether all lines have \r because if so,
you will not see any ^M. You can save files in a different format by setting
the "fileformat" option before writing. And yes, I am sure you could use
":autocmd" to automatically save *.bat files as DOS.
> > On a related note, which version/port of CVS do you (Earnie) use?
> The Cygwin version. I have ported the Cygwin version to MSYS (so I'm not
> dependent on Cygwin) and it will be a part of the DTK.
That sounds like an acceptable solution.
> > With the
> > Windows native version that I use, files are normally read and written
> > text mode so they get CRLF line endings. Since you seem to have used a
> > different CVS program that reads files in binary mode, the DOS text
> > get stored on the CVS server with DOS line endings, but are still marked
> > text files. When I check out these files, the "\r\n" becomes "\r\r\n",
> > suggest that all files that must have DOS line endings be checked in as
> > binary files, and all files that are really text should be checked in
> > Unix line endings.
> I'll have to take a look at this suggestion. If I can automate it via
> files then fine. If it depends on someone remembering to set the binary
> then that's not going to work well.
> > Of course, ideally I should probably get a CVS client
> > that writes (checks out) files in binary mode so that line endings are
> > unchanged, but I think there are too many Windows CVS clients already in
> > for this to be a requirement for accessing Mingw through CVS.
> I agree.
> :)) Have you tried to build the MSYS runtime? I can't think of a reason
> wouldn't build with MSYS/MinGW. You'll need the GCC patches to build
> that depend on it though.
No I haven't tried yet because I knew that a different version of GCC is
required to build MSYS-dependent programs. However, it would still be useful
to build the MSYS DLL to try debugging and fixing bugs in the runtime (e.g.
in path handling). I will try it out some time...