-
Notifications
You must be signed in to change notification settings - Fork 25
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
Fixed missing GEOS_LIBS #47
Conversation
I believe that the CI test from travis-ci may not be because of the changes in the PR. The text suggests to me that this is because of a deprecation warning from the CI framework. See line 4666 of the ci outpu from Details, then line 4809-4810, where the warning states
and lines 4814-4825,
|
I just updated this PR. |
This appears to be the line that causes and error.
It doesn't say why, but this doesn't seem to be anything to do with the change I made. The changes that commented these lines from .travis.yml
seemed to change the error message, but it still seems to be outside the changes here. I could try to start over, as there have been a number of changes since last Nov, when this was originally opened. If you would like me to pursue this. |
Yes, it would be great if you could sync with master and see if the issue still exists. |
OK. I'll give it a try. There seem to be a number of the R geospatial libraries that are tangled with autoconf. Spent part of today looking at rgdal, too. |
Hi, Edzer, I am going to close this PR since it's got out of sync with master and I am not good enough with Git to get everything on track. I will open a new PR based on the current master. |
The original was only passing
-lgeos_c
and not the location of the libraries that contain it. Replacing the hard-coded-lgeos_c
with the information fromgeos-config
stored in$GEOS_LIBS
inconfigure.ac
and runningautoreconf -i
generated theconfigure
script here.I ran that with
on Centos 7.6 and tested the resulting configure with
and the resulting
src/Makevars
containedwhich should be correct.
My original comments were based on the contents of the package distributed on CRAN. See Issue #45. If there is something I can do to help get a patched version created and distributed to CRAN, please let me know.