-
-
Notifications
You must be signed in to change notification settings - Fork 310
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
Unable to compile GRASS GIS on Windows #4485
Comments
There's ongoing efforts to address this (among other things) with #4121, but you should start with removing the package |
Thank you for the extremely prompt reply. Unfortunately, removing the Here's the start of my error.log file -
and so on ... Running make in lib/gis gives the following errors -
Looks like it no longer recognizes the -lomp flag. |
You should clean previous attempt with |
Thank you. That worked and I am able to compile without errors. But I am unable to run r.sun. If I try to invoke in inside the GRASS GUI console tab, I get the following error -
Instead, if I try to invoke it directly at the command line, the following popup comes up - |
Update: Switching to releasebranch_8_3 from main resolves the issue with r.sun. |
Please consider updating https://trac.osgeo.org/grass/wiki/CompileOnWindows suitably. |
If you try again building from main branch, what does configure say about blas and lapack, these lines am I curious about:
it is likely you have linking to "openblas" instead of "cblas" and "lapacke", which would be expected. If that is the case your problem can perhaps be fixed by replacing the two lines: grass/mswindows/osgeo4w/package.sh Lines 133 to 134 in 400b0df
with |
Re-compiled main branch. The lines from my config.log that you asked about are as follows -
It does seem to be linking to openblas as you suspected. I will make the change you suggest to package.sh and try again. |
Update: Recompiling with But invoking it from the console tab within the GRASS GUI still generates errors -
|
We're making some progress! Will it work if you run the command from command line only, with all arguments (not only fire up the gui)? |
I am able to run it from a python script (through r.sun.daily), so that should be an affirmative. Appreciate your prompt and helpful guidance in resolving this. |
I have an idea for the maximum recursion thing. I'm not sure I have time this weekend though. |
Good. I suppose the latter issue is somehow Python related. I don't know the reason for that, the error log looks familiar though...
Most welcome, and thank you for testing and reporting back! |
Great! |
Thanks for confirming #4514 works! |
I am following the instructions here -
https://trac.osgeo.org/grass/wiki/CompileOnWindows
but the final step of running
./mswindows/osgeo4w/package.sh
generates errors in multiple modules, which appear to be the ones that use OpenMP. Trying to run make on failed modules individually seems to confirm this -My config.log file seems to confirm this, as it includes the following text -
My Msys2 is up to date and I have re-installed all the listed msys2 requirements -
pacman -S tar libintl make bison flex diffutils git dos2unix zip mingw-w64-x86_64-toolchain mingw-w64-x86_64-cairo mingw-w64-x86_64-fftw mingw-w64-x86_64-lapack mingw-w64-x86_64-pkg-config mingw-w64-x86_64-gcc mingw-w64-x86_64-ccache mingw-w64-x86_64-zlib mingw-w64-x86_64-libiconv mingw-w64-x86_64-bzip2 mingw-w64-x86_64-gettext mingw-w64-x86_64-libsystre mingw-w64-x86_64-libtre-git mingw-w64-x86_64-libwinpthread-git mingw-w64-x86_64-libpng mingw-w64-x86_64-pcre mingw-w64-x86_64-python3-six mingw-w64-x86_64-openblas mingw-w64-x86_64-llvm-openmp
The problem persists even if I switch to an older GRASS GIS branch like releasebranch_8_3.
I am on Windows 11 Home.
Would appreciate suggestions on resolving this.
The text was updated successfully, but these errors were encountered: