Ticket #33844 (closed update: fixed)
R ports upgrade to 2.15.0 OMNI-BUG
| Reported by: | kjell.konis@… | Owned by: | dports@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.0.4 |
| Keywords: | maintainer, haspatch | Cc: | |
| Port: | R, R-framework, R-app |
Description
The attached patches/Portfile upgrade the R ports to version 2.15.0. I attached the Portfile for R-app because it looks like the R-app port in bug #32100 still has not been committed.
Attachments
Change History
comment:1 Changed 14 months ago by dports@…
- Owner changed from macports-tickets@… to dports@…
- Status changed from new to assigned
comment:3 Changed 14 months ago by dports@…
R-app isn't building for me. It looks like it's not finding the R-framework headers; see attached log.
comment:4 Changed 14 months ago by kjell.konis@…
Grrr! I thought I didn't need the post-patch phase anymore because I'm setting FRAMEWORK_SEARCH_PATHS. It turns out this was only working because I had another R.framework in /Library/Frameworks. Opps. Anyway, I put the post-patch phase back and tested both with and without an R.framework in /Library/Frameworks and it looks like it's working now.
comment:5 Changed 14 months ago by dports@…
- Status changed from assigned to closed
- Resolution set to fixed
Committed R-app in r91504. I rewrote the bit about forcing llvm-gcc instead of clang in the standard way.
I'm wondering if this port has some requirements for OS/architecture, considering that the xcode.configuration is "Leopard64". Does that mean it won't build on 32-bit systems or won't build on earlier OSes? If so, it would be nice to indicate that in the portfile. But I don't have any such systems to test with.