I just several minutes ago sent in a comment on a continued "bug" in this vein. After doing some checking and rerunning the saga_cmd executable I believe the error was on my part in inadvertently setting an environment variable which was no longer needed for the version of SAGA (2.2.7) I am runnng. Seems current versions no longer need this environment variable, SAGA_MLB, set and unsetting it seems to have corrected the problem. It does seem odd, however, that having it set would cause an abend and resultant core dump, seems like there would be a "nicer" way to deal with the issue. However, sorry for any inconvenience this may have caused, and please ignore my comment. Also, I didn't want to send in any official bug notification, if I did please remove and/or ignore it.
Thanks. Terry Sobecki -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1433255 Title: Please rebuild saga against latest gdal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/saga/+bug/1433255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
