[MacPorts] #29160: crfpp @ 0.54 - new port
#29160: crfpp @ 0.54 - new port ---------------------------------------+------------------------------------ Reporter: hiroshi.umemoto@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: science | Port: crfpp ---------------------------------------+------------------------------------ This is a Portfile for CRF++, Yet Another CRF toolkit. -- Ticket URL: <https://trac.macports.org/ticket/29160> MacPorts <http://www.macports.org/> Ports system for Mac OS
#29160: crfpp @ 0.54 - new port ---------------------------------------+------------------------------------ Reporter: hiroshi.umemoto@… | Owner: ryandesign@… Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: science | Port: crfpp ---------------------------------------+------------------------------------ Changes (by ryandesign@…): * owner: macports-tickets@… => ryandesign@… * status: new => assigned Comment: Thanks. -- Ticket URL: <https://trac.macports.org/ticket/29160#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#29160: crfpp @ 0.54 - new port ---------------------------------------+------------------------------------ Reporter: hiroshi.umemoto@… | Owner: ryandesign@… Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: science | Port: crfpp ---------------------------------------+------------------------------------ Comment(by ryandesign@…): What is the reason for running autoreconf? Usually we do that if we patch configure.ac, and thus need autoreconf to regenerate configure. We might also use autoreconf to regenerate configure if it was made with a very old version of autoconf that doesn't support universal builds (i.e. doesn't pass `-arch` flags along). It doesn't look like either reason applies here. -- Ticket URL: <https://trac.macports.org/ticket/29160#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#29160: crfpp @ 0.54 - new port ---------------------------------------+------------------------------------ Reporter: hiroshi.umemoto@… | Owner: ryandesign@… Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: science | Port: crfpp ---------------------------------------+------------------------------------ Comment(by hiroshi.umemoto@…): Replying to [comment:2 ryandesign@…]:
What is the reason for running autoreconf? Usually we do that if we patch configure.ac, and thus need autoreconf to regenerate configure. We might also use autoreconf to regenerate configure if it was made with a very old version of autoconf that doesn't support universal builds (i.e. doesn't pass `-arch` flags along). It doesn't look like either reason applies here.
Thanks a lot for your comment! I tried to build the port with a universal variant and found it did not work properly. Although `autoreconf` is not necessary as you pointed out, I have no idea how to fix the port to enable universal builds. Should I put `universal_variant no` in the port? -- Ticket URL: <https://trac.macports.org/ticket/29160#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#29160: crfpp @ 0.54 - new port ---------------------------------------+------------------------------------ Reporter: hiroshi.umemoto@… | Owner: ryandesign@… Type: submission | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: science | Port: crfpp ---------------------------------------+------------------------------------ Comment(by hiroshi.umemoto@…): I added Portfile.2 that enables a universal build as well as the `bact` port does. Could you please check the port? Thanks in advance. -- Ticket URL: <https://trac.macports.org/ticket/29160#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
#29160: crfpp @ 0.54 - new port ----------------------------------------+----------------------------------- Reporter: hiroshi.umemoto@… | Owner: ryandesign@… Type: submission | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Resolution: fixed | Keywords: science Port: crfpp | ----------------------------------------+----------------------------------- Changes (by ryandesign@…): * status: assigned => closed * resolution: => fixed Comment: Committed in r78009 with these changes: * did not commit the universal directives you proposed because they are not necessary for a project like crfpp that uses a standard autoconf-based configure script; the only reason universal didn't work here was that the developers unwisely decided in their configure script to override our CFLAGS and CXXFLAGS; I added a patch to correct that. * simplified master_sites to just "sourceforge" * just set distname instead of setting both distfiles and worksrcdir * don't autoreconf (accidentally left it in the portfile, commented out; removed it entirely in r78010) -- Ticket URL: <https://trac.macports.org/ticket/29160#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts