Cannot build ksh 1.0.10 with MSYS2/MinGW

[cedricblancher]

We cannot build ksh 1.0.10 with MSYS2/MinGW, bin/package fails like this:
$ (SHELL=/bin/dash ; $SHELL ./bin/package make)
package: /home/ced/mingw_ksh93/ksh: must be in the package root directory tree

[cedricblancher]

Still does not work:

$ export SHELL=/bin/bash.exe ; $SHELL ./bin/package make CC="/usr/bin/gcc -m64 -std=gnu17" PACKAGEROOT="$PWD" HOSTTYPE="msys.i386-64"
package: initialize the /home/ced/work/mingw_ksh93/ksh/arch/msys.i386-64 view
package: update /home/ced/work/mingw_ksh93/ksh/arch/msys.i386-64/bin/mamprobe
package: update /home/ced/work/mingw_ksh93/ksh/arch/msys.i386-64/lib/probe/C/make/probe
package: update /home/ced/work/mingw_ksh93/ksh/arch/msys.i386-64/bin/mamake
cc: fatal error: cannot execute 'cc1': spawn: No such file or directory
compilation terminated.

[McDutchie]

Thanks for the report. MSYS2/MinGW is not a system I've ever used. I generally try to avoid Windows as much as possible, but I'm going to have to figure out a way to test it on this system and make it build.

FWIW, Cygwin should work, it's tested every now and then.

[gisburn]

@McDutchie Quick setup via Cygwin shell:
---- snip ----

wget 'https://github.com/msys2/msys2-installer/releases/download/2024-11-16/msys2-x86_64-20241116.exe'
chmod a+x msys2-x86_64-20241116.exe 
./msys2-x86_64-20241116 

---- snip ----
... then in MSYS2 UCRT terminal:
---- snip ----

pacman -S --noconfirm gcc emacs gdb make gettext gettext-devel git subversion flex bison unzip pax tar libiconv-devel ncurses-devel gmp-devel mpfr-devel mpc-devel isl-devel  isl-devel procps-ng libiconv-devel sed time coreutils util-linux grep sed clang base-devel

---- snip ----

Does that help ?

[cedricblancher]

@McDutchie Any updates?

[McDutchie]

No one is currently getting paid for developing ksh, and I don't know when I'll have the time, opportunity and inclination to sit down with a Windows 10 box and figure this out. I don't have one in the house. So, unless someone else figures this out before me, you're going to have to be patient.

@cedricblancher
Hi, I'm trying to build ksh93 for msys2 myself. I got a kinda hacky workaround, which fixes the cc1 issue, only to run into a new issue with forking the process to build libsum after libast is done.
You can see it here:

msys2/MSYS2-packages#5243

[gisburn]

I'm also interested. Where can I find your script you used to try to build ksh93 ?

No matter what, it fails on windows because of fork(). Does mamake like any other make, have ability to resume if it failed during compilation? Asking because as I understand, this is a series of shell scripts. Same error too (minus pid number):
0 [main] mamake 1763 dofork: child -1 - forked process 11484 died unexpectedly, retry 0, exit code 0xC0000142, errno 11

@McDutchie
Good news, I managed to successfully build for msys2 with my PKGBUILD script in the linked merge request. It can build. You just have to run the build command twice, because about half way through it WILL fail because of fork issue. Should this issue be closed now?

[cedricblancher]

@McDutchie Good news, I managed to successfully build for msys2 with my PKGBUILD script in the linked merge request. It can build. You just have to run the build command twice, because about half way through it WILL fail because of fork issue. Should this issue be closed now?

Could you please send a stand alone script which can be used to build ksh93 on msys2? Just a shell script, without the whole PKGBUILD machinery.

@McDutchie Good news, I managed to successfully build for msys2 with my PKGBUILD script in the linked merge request. It can build. You just have to run the build command twice, because about half way through it WILL fail because of fork issue. Should this issue be closed now?

Could you please send a stand alone script which can be used to build ksh93 on msys2? Just a shell script, without the whole PKGBUILD machinery.

Sure. Though it is optional, you might want to patch in this patch I used from gisburn's repo linked.

ksh-unc-paths.patch

I wasn't sure where you wanted it to be installed, so I left that part out. If you have problems with the script, let me know.

#!/bin/sh

# This script assumes you're using gcc.
# Optional: Apply the supplied patch file. Your choice.
#
# A few environmental variables need to be set:
export GCC_DIR="$(gcc -print-search-dirs | sed -ne '/^install: /s///p')" # To fix the cc1.exe not found issue.
export PATH="$PATH:$GCC_DIR"

# A few tweaks to the other environmental variables. To fix other issues that will arise.
export CFLAGS="-I${GCC_DIR}/include -L${GCC_DIR} -L/usr/lib"
export CCFLAGS="${CFLAGS} -fno-use-linker-plugin"
export LIBRARY_PATH="${GCC_DIR}"

# These next two sed commands are necessary to ensure it builds right.
# First one, is to add a shebang to a file because windows can't run it properly without it.
sed -i '1s/^/#!\/usr\/bin\/bash\n/' src/cmd/INIT/mamprobe.sh
sed -i '6s/^/#undef _lib_iconv_open\n/' src/lib/libast/features/iconv # Without this, fails with libiconv installed

# This will fail the first time, this is to be expected and will then run again.
CC="/usr/bin/gcc" /usr/bin/bash bin/package make PACKAGEROOT="$PWD" || true

# Run it again.
CC="/usr/bin/gcc" /usr/bin/bash bin/package make PACKAGEROOT="$PWD" || true

Though I'm wondering: Why did you not want makepkg? You just run makepkg as long as the very few dependencies are installed like gcc and makepkg itself.

[cedricblancher]

Though I'm wondering: Why did you not want makepkg? You just run makepkg as long as the very few dependencies are installed like gcc and makepkg itself.

1. Because I want to do ksh93 development on MSYS2
2. I've been bugging Roland Mainz to add MSYS2 support to one of the ms-nfs41-client CI test scripts (https://github.com/kofemann/ms-nfs41-client/blob/master/tests/nfsbuildtest/nfsbuildtest.ksh93), which simply runs builds of bash, gcc, ksh93 on Windows NFSv4.2 filesystem mount. ksh93 didn't work so far, and Roland did not had time. If your script works, then we have a solution.