[MacPorts] #33844: R ports upgrade to 2.15.0 OMNI-BUG
#33844: R ports upgrade to 2.15.0 OMNI-BUG ----------------------------------+----------------------------------------- Reporter: kjell.konis@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Keywords: maintainer, haspatch | Port: R, R-framework, R-app ----------------------------------+----------------------------------------- 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. -- Ticket URL: <https://trac.macports.org/ticket/33844> MacPorts <http://www.macports.org/> Ports system for Mac OS
#33844: R ports upgrade to 2.15.0 OMNI-BUG ----------------------------------+----------------------------------------- Reporter: kjell.konis@… | Owner: dports@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Keywords: maintainer, haspatch | Port: R, R-framework, R-app ----------------------------------+----------------------------------------- Changes (by dports@…): * status: new => assigned * owner: macports-tickets@… => dports@… -- Ticket URL: <https://trac.macports.org/ticket/33844#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#33844: R ports upgrade to 2.15.0 OMNI-BUG ----------------------------------+----------------------------------------- Reporter: kjell.konis@… | Owner: dports@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Keywords: maintainer, haspatch | Port: R, R-framework, R-app ----------------------------------+----------------------------------------- Comment(by dports@…): Committed R and R-framework in r91422 and r91423 respectively. Looking at R-app now... -- Ticket URL: <https://trac.macports.org/ticket/33844#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#33844: R ports upgrade to 2.15.0 OMNI-BUG ----------------------------------+----------------------------------------- Reporter: kjell.konis@… | Owner: dports@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Keywords: maintainer, haspatch | Port: R, R-framework, R-app ----------------------------------+----------------------------------------- Comment(by dports@…): R-app isn't building for me. It looks like it's not finding the R-framework headers; see attached log. -- Ticket URL: <https://trac.macports.org/ticket/33844#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#33844: R ports upgrade to 2.15.0 OMNI-BUG ----------------------------------+----------------------------------------- Reporter: kjell.konis@… | Owner: dports@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Keywords: maintainer, haspatch | Port: R, R-framework, R-app ----------------------------------+----------------------------------------- Comment(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. -- Ticket URL: <https://trac.macports.org/ticket/33844#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
#33844: R ports upgrade to 2.15.0 OMNI-BUG ------------------------------------+--------------------------------------- Reporter: kjell.konis@… | Owner: dports@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Resolution: fixed | Keywords: maintainer, haspatch Port: R, R-framework, R-app | ------------------------------------+--------------------------------------- Changes (by dports@…): * status: assigned => closed * resolution: => fixed Comment: 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. -- Ticket URL: <https://trac.macports.org/ticket/33844#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts