Re: Eshell requires execute permission on Win10, was Re: Windows Binaries Release: was The emacs-28 release branch

[Óscar Fuentes]

"H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de> writes:

> Óscar Fuentes <ofv@wanadoo.es> writes:
>
>> "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de> writes:
>
>>> I created such a script but my problem is that chmod seems not to work
>>> for me!
>>>
>>>    chmod u+x build-zips.sh
>>>
>>> doesn't change anything, so I can't run the scripts.  Do you know this
>>> problem?
>>
>> I don't know the context, but I'll chime anyway...
>
> Thanks for asking about the context, sorry!  Above I used *eshell* to
> execute a script on Windows10.
>
> I'm on MSYS2 and emacs-28
>
> ~/scripts $ ./build-28-deps.sh 
> ./build-28-deps.sh: not an executable file
> ~/scripts $ 
>
> Is this a bug of eshell (under Windows)?

No, I don't think so. Eshell knows about executables, possibly with some
platform-specific nuances, and a text file that happens to contain a
bash script is not an executable on Windows, you need the POSIX
emulation layer and the added hacks provided by MSYS2 or Cygwin.

I wouldn't use Eshell for doing work that depends on the POSIX emulation
provided by MSYS2 (too many incompatible things involved!) Better use a
proper MSYS2 console. Make sure that the console is the correct one for
the architecture you are targeting. That is, depending on whether you
are building a 32 bits or 64 bits Emacs, start the MSYS2 console with
the shortcut for Mingw32 or Mingw64, respectively (I'm not sure how
those shortcuts are named nowadays, but it should be obvious.)