[MacPorts] #33423: Updated swi-prolog portfile for version 6.0.1
#33423: Updated swi-prolog portfile for version 6.0.1 ---------------------------------+------------------------------------------ Reporter: pmoura@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Keywords: haspatch maintainer | Port: swi-prolog ---------------------------------+------------------------------------------ Updated swi-prolog portfile for version 6.0.1. -- Ticket URL: <https://trac.macports.org/ticket/33423> MacPorts <http://www.macports.org/> Ports system for Mac OS
#33423: Updated swi-prolog portfile for version 6.0.1 ---------------------------------+------------------------------------------ Reporter: pmoura@… | Owner: cal@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Keywords: haspatch maintainer | Port: swi-prolog ---------------------------------+------------------------------------------ Changes (by cal@…): * status: new => assigned * owner: macports-tickets@… => cal@… Comment: Can you elaborate on why `PKG_CONFIG_PATH=/usr/X11R6/lib/pkgconfig` is needed? We usually don't link against system X11 libs in MacPorts, but rather depend on and link against the appropriate `xorg-*` port. See wiki:FAQ#ownlibs. -- Ticket URL: <https://trac.macports.org/ticket/33423#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#33423: Updated swi-prolog portfile for version 6.0.1 ---------------------------------+------------------------------------------ Reporter: pmoura@… | Owner: cal@… Type: update | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Keywords: haspatch maintainer | Port: swi-prolog ---------------------------------+------------------------------------------ Comment(by pmoura@…): That line is taken from the SWI-Prolog developer instructions for Mac OS X. I'm not familiar with PKG_CONFIG. Tested the patch before submitting. Everything seems fine. Your suggested alternative would be? -- Ticket URL: <https://trac.macports.org/ticket/33423#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#33423: Updated swi-prolog portfile for version 6.0.1 ---------------------------------+------------------------------------------ Reporter: pmoura@… | Owner: cal@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Resolution: fixed | Keywords: haspatch maintainer Port: swi-prolog | ---------------------------------+------------------------------------------ Changes (by cal@…): * status: assigned => closed * resolution: => fixed Comment: I've commited this for now in r90316. I think I have a few points where the portfile can be improved (e.g. building with clang might work), but I'll just put it on my todo list and open a ticket as soon as I have a tested patch. -- Ticket URL: <https://trac.macports.org/ticket/33423#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
#33423: Updated swi-prolog portfile for version 6.0.1 ---------------------------------+------------------------------------------ Reporter: pmoura@… | Owner: cal@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Resolution: fixed | Keywords: haspatch maintainer Port: swi-prolog | ---------------------------------+------------------------------------------ Comment(by pmoura@…): Building with clang does work but it kills performance. Apparently, due to poor support for GCC threaded code. The same thing happens with e.g. YAP, another Prolog compiler. The best performance in both cases is achieved using a recent version of GCC. Btw, can you also take care of committing the update to the "swi-prolog- devel" port? Thanks. -- Ticket URL: <https://trac.macports.org/ticket/33423#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts