Re: Installing the current emacs-28 branch under Windows 10

[H. Dieter Wilhelm]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
>> core.autocrlf=true
>
> Bad idea: it should be 'false'.  Git should not change the EOLs,
> neither when it checks out files, nor when it pushes them upstream.

Excuse me, I overlooked the crlf hint in the (optional) git section of
INSTALL.w64.

> I'm not sure this is the root cause of your problem, but it might be.
> Suggest to reconfigure Git, and then delete your local repository and
> clone it again.

I did that and an emacs-28.0.60 was build :-) thank you very much!

>> Must be the default for this git installation on Windows, I didn't touch
>> it.
>
> When you install Git, it asks you how you want to treat EOLs, and you
> should have selected "checkout as-is, checkin as-is" (or somesuch, I
> don't remember the exact wording).

Well, git slumbered on this Windows system for a few years, I can't
remember...

>> A sample of text files are encoded in undecided-dos in the emacs
>> repo.  Do the files need to be encoded in Unix style line endings for
>> MinGW tools?
>
> Not for MinGW, for MSYS.  The autotools you run are MSYS tools, and
> MSYS is a fork of Cygwin; Cygwin tools expect Unix-style EOLs, yes.

I see, MinGW is a compiler collection and MSYS is the tooling twiddle,
thanks for the explanation.


One observation so far: The Emacs executable can't find its own info
files!  It seems that in the info viewer are only core utils.


     Dieter

-- 
Best wishes
H. Dieter Wilhelm
Zwingenberg, Germany