Re: WinNT/CVS/^M prob

[Eli Zaretskii]

On Thu, 31 Jan 2002, Vardhan Varma wrote:

> using windowsnt4.0 + mingw + cvs from cvsnt.org.
> does this cvs handles cr/lf issues properly ??

Yes.

> first i get emacs/nt/makefile.w32-in with additional ^M,
> which i had to be manually removed or mingw's make cries.

What version of Make do you have?  Please see the file nt/INSTALL: it 
lists versions of Make and GCC which are known to work.  Please make sure 
your tools are consistent with the ones recommended there.

> (looks like cvs copy is wrong, can somebody with unix od it
> to check if line ends in 0d0d0a , 0d0a or 0a )

It has DOS-style CR-LF end-of-line format.  But that shouldn't prevent 
Make from working, because the Windows ports of Make support such files.

> and make bootstrap on entering liem, says:
> Converting h:/PersonalWork/CVS-SOURCES/emacs/leim/CXTERM-DIC/4Corner.tit to 
> quail-package...
> Invalid ENCODE: value in TIT dictionary
> 
> again a case of BIG5^M being seen by code !!

What port of CVS client do you have installed?  Is it possible that your 
CVS client adds a CR character to each LF?  If so, you have 
makefile.w32-in with _two_ CR characters before each LF, and you have 
4Corner.tit in DOS format instead of Unix format.  That would probably 
break a build.

Solutions: either install a different CVS client, which does not convert 
end-of-line (EOL) format; or manually convert text files back to the Unix 
format; or do the "cvs up" on a Unix machine and then copy the files to 
the Windows machine.

> My Question(s):
>       which is Preferred set of tools in MS Env? ..
>               1. Mingw / Cygwin / MSVC ?

See nt/INSTALL, it's all there.  In general, all of the above.

>               2. which precompiled cvs ?

If you want to be free of the EOL hassles, install the Cygwin port of 
CVS.

>       some of the things in Win  makefile could have been done better,

Thanks.  Please note that those Makefile's need to work with several 
different versions of Make, several different versions of Windows 
(Windows 9X, NT, W2K, XP), and several different kinds and versions of 
shell (command.com, cmd.exe, and Cygwin's port of Bash).  So any change 
should have a very good reason to be accepted, and preferrably should be 
tested on several different systems.

>       if i eventually make a patch, whom do i share it with ?

Please send patches to address@hidden (which is the right 
address to send any bug reports about CVS versions).

TIA