removes --static

[edzer]

No description provided.

[rsbivand]

Could I suggest changing the test to try with --static first as a separate test, and if it fails remove it from PROJ_LIB_PATH and try again? Failing --static would be a message or warning, not an error. Would a Fedora CI assist in the future to detect unannounced policy changes?

I don't see any email traffic around 17/1 discussing anything like this.

On reconsideration, sf/configure.ac line 393 was testing PROJ_LIB_PATH=pkg-config proj --libs --static, not imposing static linking, so what probably needs to be removed is -lsqlite3 in line 433?

[edzer]

I have no recollection why --static was added, and cannot find any reason in the issues or PRs. Maybe it was done by accident, like a wild guess, by accident (..) not in a branch? If nobody remembers this, I suggest reverting.