R-CMD_check MacOS-latest: configure: error: gdal-config not found or not executable. #60768
Replies: 1 comment
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
Hi GitHub Actions community!
I'm writing to see if I can get some help with a problem I'm having when running the R-CMD-check on GitHub Actions for the MacOS-latest operating system. My checks are succeeding for all operating systems, but failing for MacOS with the following string of errors:
✔ Packaged terra 1.7-41 (2.1s)
ℹ Building terra 1.7-41
✖ Failed to build terra 1.7-41
Error:
! error in pak subprocess
Caused by error in
stop_task_build(state, worker)
:! Failed to build source package 'terra'
Full installation output:
staged installation is only possible with locking
** using non-staged installation
configure: CC: clang -arch x86_64
configure: CXX: clang++ -arch x86_64 -std=gnu++17
checking for gdal-config... no
no
configure: error: gdal-config not found or not executable.
ERROR: configuration failed for package ‘terra’
Backtrace:
Subprocess backtrace:
Execution halted
Error: Process completed with exit code 1.
I understand this is an issue caused by one of my dependencies, terra, and its reliance on gdal, which seems to be missing when performing the R-CMD-check. I've read some stuff stating this has something to do with packages not being installed as binaries. However, since I am by no means an expert in R package development, I am not sure how to circumvent this issue. It is important for me that my R-CMD-check works on all operating systems, since this is one of the requirements for the repository I'm hoping to submit this to at some later point.
If anyone has some advice on what might be causing this issue, and how I may circumvent it (without having to remove my terra dependency), I would be super grateful.
All the best,
Thomas
Beta Was this translation helpful? Give feedback.
All reactions