Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add m4 program #78

Closed
Tim-Sobolev opened this issue Jul 17, 2023 · 1 comment
Closed

Add m4 program #78

Tim-Sobolev opened this issue Jul 17, 2023 · 1 comment

Comments

@Tim-Sobolev
Copy link

Tim-Sobolev commented Jul 17, 2023

I was using w64devkit to build GNU MP library recently.

To run configure script from cmd.exe were created scripts, based on comment.
Scripts were placed to the w64devkit\bin directory:

prepare.sh

if [[ "$OSTYPE" == "msys" ]]; then
    echo "MSYS..."
else
    export PATH_SEPARATOR=';'
    export ac_executable_extensions='.exe'
fi
export build_alias="$(uname -m)-pc-mingw64"

if [ -f configure ]
then
    echo "Converting configure..."
    sed -i 's/func_convert_file_msys_to_w32/func_convert_file_noop/' configure
    ./configure $@
fi

prepare.cmd

sh %~dp0prepare.sh %*

However, I have to use m4 from old unxutils project.
It will be nice to have it available in the standart distribution packege.

@skeeto
Copy link
Owner

skeeto commented Aug 8, 2024

I'm not interested in including m4, but some good news: As of w64devkit 2.0.0 you can easily compile m4 from source the usual way yourself:

$ tar xf m4-1.4.19.tar.xz
$ cd m4-1.4.19/
$ ./configure CFLAGS=-fpermissive
$ make -j$(nproc)

And then you'll have m4.exe. There's currently a bug in m4 and -fpermissive is required when compiling m4 with GCC 14 or later. You'd need it even outside of w64devkit.

@skeeto skeeto closed this as completed Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants