Ticket #28468 (closed defect: duplicate)
gobject-introspection @0.9.12 fails to build on 10.4
| Reported by: | roberto@… | Owned by: | singingwolfboy@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.9.2 |
| Keywords: | Cc: | mk@…, gale@… | |
| Port: | gobject-introspection |
Description
Please see attached build log.
Attachments
Change History
comment:5 Changed 2 years ago by mk@…
Ooops, I saw now that in my case not gobject-introspection fails to build, but that it is not installed when I tried upgrading atk.
comment:6 Changed 2 years ago by mk@…
- Owner changed from singingwolfboy@… to rmstonecipher@…
I looks like I'd have to open a separate ticket for atk instead which is obviously missing gobject-introspection as dependency.
comment:8 Changed 2 years ago by singingwolfboy@…
- Status changed from new to closed
- Resolution set to invalid
Please reopen ticket if gobject-introspection actually fails to build, but based on mk's comments, it looks like this ticket was open accidentally. Closing as invalid.
comment:9 Changed 2 years ago by roberto@…
- Status changed from closed to reopened
- Resolution invalid deleted
The problem is still there for me. I executed a selfupdate and then attempted the build again. The error looks the same to me, but I have attached updated logs just in case something is different and it escaped my notice.
comment:10 Changed 2 years ago by jmr@…
- Owner changed from rmstonecipher@… to macports-tickets@…
- Status changed from reopened to new
comment:11 Changed 2 years ago by ryandesign@…
The error in the log is:
:info:configure checking whether Python support is requested... checking for a Python interpreter with version >= 2.5... none :info:configure configure: error: no suitable Python interpreter found
Seems to be the same issue as #28479: gobject-introspection uses "python" when it should use a specific known-good version of python instead.
comment:14 Changed 16 months ago by jmr@…
- Status changed from new to closed
- Resolution set to duplicate
Duping to #28479 even though it's newer, since the summary there is closer to the real issue.