Opened 15 years ago

Closed 15 years ago

#20153 closed defect (fixed)

p5-xml-namespacesupport @1.10 infinite loop in configure due to CPAN questions

Reported by: league@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.8.0
Keywords: cpan Cc:
Port: p5-xml-namespacesupport

Description

This one threw me for a loop — the configure phase for this package was taking more than 30 minutes. I stopped it and ran with port -dv, and discovered it repeating this question over and over:

(1) Africa
(2) Asia
(3) Central America
(4) Europe
(5) North America
(6) Oceania
(7) South America
Select your continent (or several nearby continents) [] 
Sorry! since you don't have any existing picks, you must make a
geographic selection.

(1) Africa
(2) Asia
(3) Central America
(4) Europe
(5) North America
(6) Oceania
(7) South America
Select your continent (or several nearby continents) [] 
Sorry! since you don't have any existing picks, you must make a
geographic selection.

I'm a beginner with MacPorts and with CPAN, so I don't know whether it's legit to rely on it to grab Perl modules rather than have explicit dependencies to other ports. I worked around it by running ‘sudo cpan’ and answering all the interactive questions, then trying the configure again. Complete logs (before and after) attached.

Attachments (2)

config-fail.txt (8.9 KB) - added by league@… 15 years ago.
config-success.txt (3.5 KB) - added by league@… 15 years ago.

Download all attachments as: .zip

Change History (3)

Changed 15 years ago by league@…

Attachment: config-fail.txt added

Changed 15 years ago by league@…

Attachment: config-success.txt added

comment:1 Changed 15 years ago by blb@…

Resolution: fixed
Status: newclosed

That is usually a sign of a missing dependency, though I note your success log didn't show anything else being installed by CPAN; also, XML::NamespaceSupport doesn't have much in the way of dependencies. The general case of CPAN asking questions in order to download should be fixed by r53351.

Note: See TracTickets for help on using tickets.