-
Notifications
You must be signed in to change notification settings - Fork 49
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
Non-portable flags used for compilation #264
Comments
I have the same issue as well. |
The Ubuntu build of R has those flags, by default, I think. So unless you specified these flags yourself, and/or you are seeing them for other platforms that CRAN uses, e.g. R-devel on Debian, you can ignore them. |
First: sorry for posting to a closed issue. These flags are set in the |
We could "fix" this in the Dockerfile, but I am just not sure if that's the right thing to do. This is a builder that is for Ubuntu, so I guess you would want to keep the default Ubuntu settings? The maintainer knows about this, btw.: https://stat.ethz.ch/pipermail/r-package-devel/2019q2/003898.html |
You are right, it makes sense to leave it as it is in the Dockerfile. Also because it might be fixed in future Ubuntu versions. Thanks for the informative link! |
Actually, this is not so much a bug in Ubuntu, but a bug in the R check code. Yes, these flags are not portable, but they are not coming from the package, they are coming from the system setup, so in this case it does not actually matter if they are portable or not. |
I'll report it as a bug. |
I get the following on Ubuntu Linux 16.04 LTS, R-release, GCC:
See the full build log at https://builder.r-hub.io/status/spsann_2.2.0.tar.gz-268f9200dc964f988a305582ce2bf429
I know that this can be solved locally by setting alternative flags in the ~/.R/Makevars file. How can I solve this issue when using
rhub
?The text was updated successfully, but these errors were encountered: