Github user pwendell commented on the pull request: https://github.com/apache/spark/pull/1031#issuecomment-57211561 Hey @tgravescs I actually don't mind capturing `LD_LIBRARY_PATH` and inserting it into `java.library.path` - it has the same effect and it makes the patch set much easier to reason about. Do you see any specific issues with this approach?
--- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org