Ticket #17418 (closed update: fixed)
glib2: update to 2.18.3
| Reported by: | ryandesign@… | Owned by: | ryandesign@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.7.0 |
| Keywords: | Cc: | mcalhoun@… | |
| Port: | glib2 |
Description
glib2 should be updated to 2.18.3.
Change History
comment:4 Changed 4 years ago by ryandesign@…
- Status changed from assigned to closed
- Resolution set to fixed
Updated to 2.18.3 and worked around the problem in r42728.
comment:5 Changed 4 years ago by north@…
This problem appears to be persisting in Tiger for some reason. Build fails at:
-- Installing ./html/up.png /bin/sh: line 1: gtkdoc-rebase: command not found make[5]: * [install-data-local] Error 127 make[4]: * [install-am] Error 2 make[3]: * [install-recursive] Error 1 make[2]: * [install-recursive] Error 1 make[1]: * [install-recursive] Error 1 make: * [install] Error 2 Error: Target org.macports.destroot returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_glib2/work/glib-2.18.3" && make install DESTDIR=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_glib2/work/destroot " returned error 2
Don't know if that advises reopening this bug or what...
comment:6 Changed 4 years ago by ryandesign@…
- Status changed from closed to reopened
- Resolution fixed deleted
Yes, I appear to have screwed something up...
comment:7 Changed 4 years ago by north@…
Rats. Tried the latest and it failed at the same spot. Ah well; I'll keep an eye on this space!
comment:8 Changed 4 years ago by ryandesign@…
- Status changed from reopened to closed
- Resolution set to fixed
Fixed in r42805 - actually tested before committing this time :)
comment:11 Changed 4 years ago by anonymous
- Milestone Port Updates deleted
Milestone Port Updates deleted
There's a problem updating to 2.18.3. If you don't have gtkdoc installed it still tries to use gtkdoc-rebase during the destroot phase and says
In 2.18.2 this error was ignored but in 2.18.3 it is a fatal error. I reported it upstream. We can work around it by fixing the use of which in their scripts.