#40797 closed defect (duplicate)
Configuring groff hangs on OS X 10.9
Reported by: | PerMildner | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.2.0 |
Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt) | |
Port: | groff |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
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.
Change History (6)
comment:1 Changed 11 years ago by cooljeanius (Eric Gallager)
comment:2 Changed 11 years ago by larryv (Lawrence Velázquez)
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Duplicate of #40793.
comment:3 follow-up: 4 Changed 11 years ago by PerMildner
Note that #40793 just removed the broken line in configure, my analysis above shows how to correct it.
comment:4 Changed 11 years ago by larryv (Lawrence Velázquez)
Replying to 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.
comment:5 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|---|
Port: | groff added |
comment:6 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign@… added |
---|
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.
So it's not just Mountain Lion as reported in #40793 then?