This issue seems resolved with with commit [ff996b]. Regards, Manfred
Thank you! The fix looks good to me. The older sgrd files are now written as expected. The seems to be as far as I can tell. Regards, Manfred
saga_cmd fails to load and write shapefiles
saga_cmd fails to read and write native grids
Binary Packages
Hi! interpreting your provided information, it seems cmake is unable to finde the openMP. The hint is the following line: Could NOT find OpenMP_C (missing: OpenMP_C_FLAGS OpenMP_C_LIB_NAMES) Since openMP can't be found it may help to provide cmake with an explicit path to the install location before configuring SAGA as suggested in the accepted answer here [1] . It might also be a problem with clang and the version of installed version of openMP as Volker wrote on a similar thread in the forum [2]...
Misleading FILE Parameter for Export Grid to KML
Export Grid to KML might produce invalid files
Hi Rainer! the last days I had time to build SAGA from git with your patch included. There were no problems at all. In both cases (rpmbuild and development environment) the PySAGA package installed correctly. As far as I'm concerned, this ticked can be closed. Thank you! Regards, Manfred
Dear SAGA team! this issue is resolved! Please close. Regards, Manfred
Hi Rainer, this issue is resolved, the changed were undone some days later. Unfortunately, I do not have the possibility/permission to close this ticket, even though I am the creator. Please close it, if you can! Thank you! Regards, Manfred
Hello Rainer, thank you very much for all you work regarding this patch and even reaching out to the core team to get it integrated! Interesting to see how cmake seems to handle variables on FreeBSD compared to linux. I am going to do test builds from git the following days. Thank you again! Kind regards, Manfred
Install PySAGA relative to install prefix
PySAGA package installs to /usr
Packaging fails due to RPATH
Source Tarball file permissions
Python invalid escape sequences
PySAGA does not install in architecture dependet directory
Binary Packages
Hi, the error is not related to the rpm environment. I was able reproduce it outside. It seems that there were changes in the compiler environment with gcc 13, where the cstdint header does not get included automatically anymore [1], therefore the error message about the missing uint32_t definition. This issue was fixed upstream [2] by adding the header manually. With this patch applied, SAGA builds successfully with c++ standard set to C++17 and clipper2 enabled with -DWITH_CLIPPER_ONE=OFF. [1]...
Hi, it seems to me that the raised C++ standard (to 14) solved the initial issue. As for now the PDAL module builds without problem with c++14, even though other requirements are listed. For me, the problem with vigra (mentioned in the discussion) is not a SAGA issue and should be fixed elsewhere. So from my point of view, this ticket could be closed. Regards, Manfred
Hi Justus, It was the intention of this post to let you know about the availability of this repository since individual Copr projects have to be manually added by the user. I added an entry for Fedora to the binary package wiki page. I just realized that I have the permission to edit the wiki even as a non project member. Regrading the open tickets, I will comment on them separately. Regards, Manfred
Binary Packages
Hi everyone! Some may have noticed that the Fedora SAGA package is no longer maintained and is not included in the official repositories anymore (Fedora 38). I started preparing a SAGA package for Fedora some weeks ago and with the the support from the saga developer team I was able to create a package for Fedora with almost all optional features enabled. Thank you all! Today I updated the build to the latest 9.0.1 release and finally uploaded it to Fedora Copr. You can find the fedora builds here:...
Hi! I also think that an additional README file should be sufficient to for the guidelines to be met as the license files itself are already present. Until recently there was a SAGA package available in the official repository. Even for this the the presence of a README file was acceptable. The package was quite outdated and is now not available anymore for Fedora.
Hi! thank you for your help and referencing your AUR package. I have seen you disabled the call to the cmake routine. On Fedora this results in using C++17 (compiler default) and an other failed build due to the enabled vigra component (vigra 11.1 from the fedora repo). It seems C++17 is not fully backwards compatible as it fails with: ISO C++17 does not allow dynamic exception specifications [1] inside the vigra library which is not a SAGA problem. So I have to set the C++ standard here again. It...
Build with Clipper2 failed
PDAL-enabled build fails due to forced c++11
Missing license files