Opened 9 years ago
Closed 6 years ago
#48523 closed defect (fixed)
saga does not compile after gdal port uprade to 2.0
| Reported by: | aaschwanden (Andy Aschwanden) | Owned by: | Veence (Vincent) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.3.3 |
| Keywords: | Cc: | yserra@… | |
| Port: | saga |
Description
Hi,
Saga GIS does not compile anymore since gdal got bumped to version 2.0. See attached log.
Thanks,
Andy
Attachments (2)
Change History (10)
Changed 9 years ago by aaschwanden (Andy Aschwanden)
| Attachment: | saga_main.log added |
|---|
comment:1 follow-up: 2 Changed 9 years ago by mf2k (Frank Schima)
| Cc: | vince@… removed |
|---|---|
| Owner: | changed from macports-tickets@… to vince@… |
comment:2 Changed 9 years ago by aaschwanden (Andy Aschwanden)
Changed 9 years ago by aaschwanden (Andy Aschwanden)
comment:3 Changed 9 years ago by aaschwanden (Andy Aschwanden)
I have attached a diff file. 2.2.0 compiles and works for me.
comment:4 Changed 9 years ago by Veence (Vincent)
Hi! Are you sure it REALLY works? Did you try to call any procedure and/or analysis tool. My copy does not work, there is something broken, I can’t get tools working properly, and I must say the preliminary investigation I’ve carried out did not yield anything noteworthy. What about yours? If you can make it work, then that means something is broken on my side.
comment:5 Changed 9 years ago by aaschwanden (Andy Aschwanden)
Sorry for the delay. So far I've only used the QGIS bindings to SAGA and I'm having some issues there too.
Anyway, you're right. I can start up the SAGA gui, and everything looks fine. But loading basic files such as shape files and GeoTiffs fails.
comment:6 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | yserra@… added |
|---|
Has duplicate #48945.
comment:7 Changed 8 years ago by Veence (Vincent)
Saga compiles fine but doesn't work properly. I hope to find some time to fix this in the next days.
comment:8 Changed 6 years ago by Veence (Vincent)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
This issue was fixed in Saga 2.2.0. Bumping the saga port to version 2.2.0 will solve the issue.