-
Notifications
You must be signed in to change notification settings - Fork 173
fix(c/driver_manager): fix expected ; for musl arch
#3105
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
Conversation
lidavidm
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops. Thanks for catching this!
|
I had to leave my desk so I didn't fully write down the description, but I did complete it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed, we should consider a MUSL build too. Want to file a new issue? (We could just have a Docker Compose job that builds the source and run it as a nightly test, like we already do to test newest Clang/GCC.)
|
Ignoring the Dev PR check since it's incorrectly reading the |
Thanks, sounds good. I've opened #3107 |
|
FWIW, I am now seeing this compilation error in the new CRAN release of package 'adbcdrivermanager' (0.19.0). Checks on Alpine aren't part of the submission checks yet, so this slipped through. A patch version would be nice. |
|
@bastistician Due to the amount of effort involved in the Apache release process in general, I think it is unlikely that a patched version will be released for this. In that case, the next release will probably be more than a month away. But @paleolimbot could submit a patched version to CRAN. |
|
I can cherry pick this into a patch no problem! |
|
I did the pick and will push to CRAN shortly. I get: (i.e., this should probably also check |
|
@paleolimbot Thanks! |
I noticed that the WASM build for the ADBC 19 release on R-multiverse is failing.
I was able to reproduce the error locally using an Alpine-based Docker image, as shown below:
Then, execute the following command on the container:
The error will be as follows:
In the future it may be worthwhile to have musl builds on CI.