-
Notifications
You must be signed in to change notification settings - Fork 194
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
If using CXX1XSTD should also use CXX1X compiler #176
Comments
as an intermediate fix, @jimhester suggested (if I understood correctly) to amend my I tried the below
But still got a failing build, this time erroring out on
Apologies in advance if this is because I am using the makevars wrong. |
interestingly, just setting
|
The first example creates a HEREDOC, so you just need to add Trusty has an older version of GCC as the default, so doesn't run into this issue. |
They are a C99 extension which then requires =c++11 / c++0x causing other issues (tidyverse#176) as we do not actually use the CXX1X compiler. The only use of fprintf in ole.c uses two additional arguments, so we will just hard code that number directly. Fixes tidyverse#176
readxl sets PKG_CXXFLAGS to include CXX1XSTD (added in commit c957ce1), but does not use the CXX1X compiler.
If the user speficies an alternative compiler for CXX1X (and CXX1XSTD) in Makevars this can result in readxl failing to build (see https://travis-ci.org/leeper/rio/builds/131807863#L1641-L1645 for an example).
In addition the comment confuses me, if the issue is compiling C code with the C99 standard as the submission comments suggest, should we not be setting
PKG_CFLAGS=-std=c99
instead?The text was updated successfully, but these errors were encountered: