[MacPorts] #40797: Configuring groff hangs on OS X 10.9
#40797: Configuring groff hangs on OS X 10.9 ---------------------------+-------------------------------- Reporter: Per.Mildner@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: | Port: ---------------------------+-------------------------------- port install groff hangs during configuration. Manually running configure from the build directory works. Tried various combinations of port clean groff etc but nothing helped. It turns out that a call to pnmtops hangs. What did help was to change configure (in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_groff/groff\ /work/groff-1.22.2/): # original line: if echo P2 2 2 255 0 1 2 0 | pnmtops -nosetpage > /dev/null 2>&1 ; then # changed line if echo P2 2 2 255 0 1 2 0 | $pnmtops -nosetpage > /dev/null 2>&1 ; then Note that the configure file spends some effort to figure out the path to pnmtops (putting it in the variable with the same name) so regardless of the hanging issue the code that uses plain 'pnmtops' instead of '$pnmtops' looks suspicious. There are code a few lines down that sets pnmtops_nosetpage to a value that also ignores the path found for pnmtops but I did not change those. I have no idea why using a full path makes a difference here. It is even possible that I misunderstood the configure script and that the if-test just quietly fails after my change, but the hang disappeared. -- Ticket URL: <https://trac.macports.org/ticket/40797> MacPorts <http://www.macports.org/> Ports system for OS X
#40797: Configuring groff hangs on OS X 10.9 ----------------------------+-------------------------------- Reporter: Per.Mildner@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: | ----------------------------+-------------------------------- Comment (by egall@…): So it's not just Mountain Lion as reported in #40793 then? -- Ticket URL: <https://trac.macports.org/ticket/40797#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#40797: Configuring groff hangs on OS X 10.9 ----------------------------+-------------------------------- Reporter: Per.Mildner@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: duplicate | Keywords: Port: | ----------------------------+-------------------------------- Changes (by larryv@…): * status: new => closed * resolution: => duplicate Comment: Duplicate of #40793. -- Ticket URL: <https://trac.macports.org/ticket/40797#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#40797: Configuring groff hangs on OS X 10.9 ----------------------------+-------------------------------- Reporter: Per.Mildner@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: duplicate | Keywords: Port: | ----------------------------+-------------------------------- Comment (by Per.Mildner@…): Note that #40793 just removed the broken line in configure, my analysis above shows how to correct it. -- Ticket URL: <https://trac.macports.org/ticket/40797#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#40797: Configuring groff hangs on OS X 10.9 ----------------------------+-------------------------------- Reporter: Per.Mildner@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: duplicate | Keywords: Port: | ----------------------------+-------------------------------- Comment (by larryv@…): Replying to [comment:3 Per.Mildner@…]:
Note that #40793 just removed the broken line in configure, my analysis above shows how to correct it.
So comment on that ticket. This ticket is closed. -- Ticket URL: <https://trac.macports.org/ticket/40797#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#40797: Configuring groff hangs on OS X 10.9 ----------------------------+-------------------------------- Reporter: Per.Mildner@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: duplicate | Keywords: Port: groff | ----------------------------+-------------------------------- Changes (by ryandesign@…): * port: => groff Old description:
port install groff hangs during configuration. Manually running configure from the build directory works.
Tried various combinations of port clean groff etc but nothing helped.
It turns out that a call to pnmtops hangs.
What did help was to change configure (in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_groff/groff\ /work/groff-1.22.2/):
# original line: if echo P2 2 2 255 0 1 2 0 | pnmtops -nosetpage > /dev/null 2>&1 ; then
# changed line if echo P2 2 2 255 0 1 2 0 | $pnmtops -nosetpage > /dev/null 2>&1 ; then
Note that the configure file spends some effort to figure out the path to pnmtops (putting it in the variable with the same name) so regardless of the hanging issue the code that uses plain 'pnmtops' instead of '$pnmtops' looks suspicious. There are code a few lines down that sets pnmtops_nosetpage to a value that also ignores the path found for pnmtops but I did not change those.
I have no idea why using a full path makes a difference here. It is even possible that I misunderstood the configure script and that the if-test just quietly fails after my change, but the hang disappeared.
New description: port install groff hangs during configuration. Manually running configure from the build directory works. Tried various combinations of port clean groff etc but nothing helped. It turns out that a call to pnmtops hangs. What did help was to change configure (in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_groff/groff\ /work/groff-1.22.2/): # original line: {{{ if echo P2 2 2 255 0 1 2 0 | pnmtops -nosetpage > /dev/null 2>&1 ; then }}} # changed line {{{ if echo P2 2 2 255 0 1 2 0 | $pnmtops -nosetpage > /dev/null 2>&1 ; then }}} Note that the configure file spends some effort to figure out the path to pnmtops (putting it in the variable with the same name) so regardless of the hanging issue the code that uses plain 'pnmtops' instead of '$pnmtops' looks suspicious. There are code a few lines down that sets pnmtops_nosetpage to a value that also ignores the path found for pnmtops but I did not change those. I have no idea why using a full path makes a difference here. It is even possible that I misunderstood the configure script and that the if-test just quietly fails after my change, but the hang disappeared. -- -- Ticket URL: <https://trac.macports.org/ticket/40797#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
#40797: Configuring groff hangs on OS X 10.9 ----------------------------+-------------------------------- Reporter: Per.Mildner@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: duplicate | Keywords: Port: groff | ----------------------------+-------------------------------- Changes (by ryandesign@…): * cc: ryandesign@… (added) Comment: This is not the correct solution. The variable $pnmtops does not contain the path to the `pnmtops` program; it contains the string "found". After making the above change, the configure script tries to determine if `pnmtops` supports the `-nosetpage` option by running the nonexistent program "`found`" which of course fails so the test decides incorrectly that `pnmtops` does not support the `-nosetpage` option. -- Ticket URL: <https://trac.macports.org/ticket/40797#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts