#46534 closed defect (worksforme)
glade @3.18.3_1: You must have XML::Parser installed to run /opt/local/bin/intltool-merge
| Reported by: | jkordani (Joshua Kordani) | Owned by: | dbevans (David B. Evans) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.3.3 |
| Keywords: | Cc: | ||
| Port: | glade |
Description
terminal output and macports log attached.
this is after running sudo port clean glade
Attachments (2)
Change History (7)
Changed 10 years ago by jkordani (Joshua Kordani)
| Attachment: | glade.main.log added |
|---|
Changed 10 years ago by jkordani (Joshua Kordani)
| Attachment: | glade.out.txt added |
|---|
install terminal output
comment:1 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
| Keywords: | failed-install removed |
|---|---|
| Owner: | changed from macports-tickets@… to devans@… |
| Summary: | 10.7 can't install glade @3.18.3_1 → glade @3.18.3_1: You must have XML::Parser installed to run /opt/local/bin/intltool-merge |
Hmm, the log says:
You must have XML::Parser installed to run /opt/local/bin/intltool-merge
That should have been installed as a dependency of intltool. And the glade port already includes the code to run autoreconf to ensure intltool can find the right copy of XML::Parser.
comment:2 Changed 10 years ago by jkordani (Joshua Kordani)
what do you recommend I do, or what other output can I provide?
comment:3 follow-up: 4 Changed 10 years ago by jkordani (Joshua Kordani)
per https://trac.macports.org/ticket/46604, uninstalling several bad *-headers packages, namely CarbonHeaders, dyld_headers, libunwind-headers etc, and reattempting build of glade succeeds
comment:4 Changed 10 years ago by dbevans (David B. Evans)
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Replying to joshua.kordani@…:
per https://trac.macports.org/ticket/46604, uninstalling several bad *-headers packages, namely CarbonHeaders, dyld_headers, libunwind-headers etc, and reattempting build of glade succeeds
This doesn't seem logical to me although I could be wrong. It seems more likely to me that your intltool was installed with a perl variant less than +perl5_16. Perl extensions are no longer supported for these versions of perl and have been removed from MacPorts. This would explain your issue.
The unsupported variants have recently been removed from intltool so a rebuild would result in a supported version of perl being used instead, +perl5_16 by default.
comment:5 Changed 10 years ago by jkordani (Joshua Kordani)
it is likely that I ran a selfupdate somewhere in this process that would have dropped the old perl module package and picked up a new one, and didn't really think about it.
macports main.log