barracuda156 commented on issue #38769: URL: https://github.com/apache/arrow/issues/38769#issuecomment-1817319362
> The flags were not passed because the source build failed but for some reason didn't kill the whole package install.... I have no idea why but will look into it. Not really sure, since in this case we do not patch anything. Here is the exact port I used (update to the earlier version, which worked with no issues with `arrow` 13.0.0): https://github.com/macports/macports-ports/commit/3411bafc22c024e7eea5e8ca18d22cc3f50c0065 I.e. from our side we only ensure the right choice of compiler (cxx_standard setting). > there is currently a workaround for issues with our source build (includes an older abseil version that doesn't compile on gcc13) that disables gcs, but as you are going to use the system libarrow you can force that with ARROW_GCS=ON (this workaround will hopefully be removed for 15.0.0) We would certainly prefer to avoid rebuilding `arrow` itself just for the usage in R. It is still built from source, just in a way it is available generally. (`abseil` is a painful port, which we have to carry patches for: my PR to upstream, I think, is still hanging for ages open.) Just to be clear, you gonna retain an option to link to an external `arrow` in 15.0.0, right? That is desirable to have, at least as a non-default choice. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
