[MacPorts] #43960: mercurial @3.0.1 build failure in msgfmt
#43960: mercurial @3.0.1 build failure in msgfmt ---------------------+-------------------------------- Reporter: cobbe@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.0 Keywords: | Port: mercurial ---------------------+-------------------------------- I'm trying to upgrade to mercurial @3.0.1, but it's failing during the "build" phase. I've attached the logfile. MacOS 10.9.3, XCode 5.1.1, MacPorts 2.3.0. I first saw the failure as part of a "macports upgrade outdated", but I'm seeing the same message after "port clean --all mercurial; port uninstall mercurial; port install mercurial" (with appropriate "sudo"s, of course). -- Ticket URL: <https://trac.macports.org/ticket/43960> MacPorts <http://www.macports.org/> Ports system for OS X
#43960: mercurial @3.0.1 build failure in msgfmt ------------------------+-------------------------------- Reporter: cobbe@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.0 Resolution: | Keywords: Port: mercurial | ------------------------+-------------------------------- Comment (by cobbe@…): I just tried to roll back to the package as it existed as of r120718, and I'm getting the same failure. Trying r119642 next -- I'm quite confident this will work, as I believe this was the version I was running previously. -- Ticket URL: <https://trac.macports.org/ticket/43960#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#43960: mercurial @3.0.1 build failure in msgfmt ------------------------+-------------------------------- Reporter: cobbe@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.0 Resolution: | Keywords: Port: mercurial | ------------------------+-------------------------------- Comment (by cobbe@…): Replying to [comment:1 cobbe@…]:
I just tried to roll back to the package as it existed as of r120718, and I'm getting the same failure. Trying r119642 next -- I'm quite confident this will work, as I believe this was the version I was running previously.
Turns out r119642 fails as well, with the same message. I noticed that the failure is happening in msgfmt, which is part of the gettext package. The original "port upgrade outdated" command that led to the Mercurial failure also updated gettext from @0.18.3.2_0 to @0.19_0, so I tried rolling gettext back to the previous version. With gettext 0.18, the current version of Mercurial (as of r102719) installs fine. Should I file a ticket against gettext? -- Ticket URL: <https://trac.macports.org/ticket/43960#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#43960: mercurial @3.0.1 build failure in msgfmt ------------------------+-------------------------------- Reporter: cobbe@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.0 Resolution: | Keywords: Port: mercurial | ------------------------+-------------------------------- Comment (by cobbe@…): Ah, I see that someone already has (#43938). Please feel free to close this ticket, and I'm sorry for the noise. -- Ticket URL: <https://trac.macports.org/ticket/43960#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#43960: mercurial @3.0.1 build failure in msgfmt ------------------------+-------------------------------- Reporter: cobbe@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.0 Resolution: duplicate | Keywords: Port: mercurial | ------------------------+-------------------------------- Changes (by mf2k@…): * status: new => closed * resolution: => duplicate -- Ticket URL: <https://trac.macports.org/ticket/43960#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts