-
Notifications
You must be signed in to change notification settings - Fork 124
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
uname applet to emulate msys2's mingw64 environment's uname #296
Comments
The busybox-w32 binaries I make available don't come with a development environment so it would be inappropriate to guess how they might be used. w64devkit ships a custom busybox-w32 binary. Perhaps they'd consider altering the output of |
Getting |
Could you implement it like this: set the environment variable |
They are just wrong, just run |
wrong or not is unimportant, the point is to emulate mingw so configure script won't fail. |
Currently:
On msys2's mingw64 environment:
Most users will use a mingw64 based gcc with busybox-w32 anyway (w64devkit?) so it's wise to copy msys2's mingw64 environment's uname. The current value of uname caused configure script to fail to detect the platform it's building on.
The text was updated successfully, but these errors were encountered: