#39320: gtkmm @2.24.3_2 - triggers rebuild due to broken port -----------------------------+---------------------- Reporter: maverick.woo@… | Owner: devans@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: gtkmm | -----------------------------+---------------------- Comment (by egall@…): Error: {{{ :info:build libtool: link: cannot find the library `/opt/local/lib/libXrender.la' or unhandled argument `/opt/local/lib/libXrender.la' :info:build make[2]: *** [extra_defs_gen/generate_extra_defs] Error 1 :info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_gtkmm/gtkmm/work/gtkmm-2.24.3/tools' :info:build make[1]: *** [all-recursive] Error 1 :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_gtkmm/gtkmm/work/gtkmm-2.24.3' :info:build make: *** [all] Error 2 :info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_gtkmm/gtkmm/work/gtkmm-2.24.3' :info:build Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_gtkmm/gtkmm/work/gtkmm-2.24.3" && /usr/bin/make -j4 -w all :info:build Exit code: 2 }}} OP, does the file `/opt/local/lib/libXrender.la` actually exist on your system? On my system it comes from `xrender`: {{{ eric-gallagers-macbook-pro:~ root# port provides /opt/local/lib/libXrender.la /opt/local/lib/libXrender.la is provided by: xrender }}} ...which should have been dragged in as a recursive dependency: {{{ eric-gallagers-macbook-pro:~ root# port rdeps gtkmm The following ports are dependencies of gtkmm @2.24.3_2+universal: ... graphviz ... pango cairo ... xrender }}} Perhaps an explicit dependency on `xrender` should be added? -- Ticket URL: <https://trac.macports.org/ticket/39320#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X

#39320: gtkmm @2.24.3_2 - triggers rebuild due to broken port -----------------------------+---------------------- Reporter: maverick.woo@… | Owner: devans@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: gtkmm | -----------------------------+---------------------- Comment (by devans@…): What variants are you using to avoid X11 ? Should be +no_x11 -x11 +quartz for quartz rendering gtkmm just provides bindings to gtk2 and its dependendents so you need to make sure they are all built with the correct variants. In this case xrender is a dependency of cairo when it is built for X11. {{{ port rdeps gtkmm }}} should show no X11 dependencies if your variants.conf is set as above. -- Ticket URL: <https://trac.macports.org/ticket/39320#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X

#39320: gtkmm @2.24.3_2 - triggers rebuild due to broken port -----------------------------+---------------------- Reporter: maverick.woo@… | Owner: devans@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: gtkmm | -----------------------------+---------------------- Comment (by devans@…): Yes, thanks. I was able to reproduce the problem by first installing gtkmm with variants for +x11 and then trying again with variants for +quartz as you are doing. This results in pango cairo gtk2 being rebuilt for +quartz but cairomm and pangomm are not rebuilt because they don't have a +quartz variant. Thus a dependency in pangomm that was created by the +x11 build can persist in the +quartz build. You can probably fix your problem by forcing a rebuild of cairomm and pangomm before trying the build gtkmm again {{{ sudo port -n upgrade --force cairomm pangomm sudo port -f install gtkmm }}} -- Ticket URL: <https://trac.macports.org/ticket/39320#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X

#39320: gtkmm @2.24.3_2 - triggers rebuild due to implicit pangomm variant mismatch -----------------------------+---------------------- Reporter: maverick.woo@… | Owner: devans@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: fixed | Keywords: Port: gtkmm | -----------------------------+---------------------- Changes (by devans@…): * status: new => closed * resolution: => fixed Comment: The lesson to remember here is that, at this time, the available binary archives are only built (if at all) for a given port's default variants. In the case of pangomm this is effectively +x11 because that's pango's default. I have committed a fix in r106728 that: * adds variants +quartz +x11 (default +x11) to cairomm, pangomm and gtkmm since these ports effectively inherit the variants of their dependents. * adds checks that require variants of a given port's dependents to match its own variants Thanks for your report and for your help working through this problem. -- Ticket URL: <https://trac.macports.org/ticket/39320#comment:9> MacPorts <http://www.macports.org/> Ports system for OS X

#39320: gtkmm @2.24.3_2 - triggers rebuild due to implicit pangomm variant mismatch -----------------------------+---------------------- Reporter: maverick.woo@… | Owner: devans@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: gtkmm | -----------------------------+---------------------- Comment (by egall@…): Replying to [comment:10 cal@…]:

This breaks the upgrade path for all users that have pango and cairo installed with +quartz, requiring manual intervention:

{{{ ---> Computing dependencies for pangomm ---> Fetching archive for pangomm Error: org.macports.archivefetch for port pangomm returned: path:lib/pkgconfig/cairo.pc:cairo cairomm pango must be installed without +quartz. Please see the log file for port pangomm for details:

/opt/local/var/macports/logs/_opt_dports_x11_pangomm/pangomm/main.log

Error: Unable to upgrade port: 1 }}}

While manually running {{{ sudo port upgrade --enforce-variants pangomm -x11 +quartz }}} works, it would be easier, if the port checked whether pango or cairo were already installed and changed its `default_variants` depending on their installed variants. After all, there's no point in setting a `default_variant` that will not be installable on a user's system.

Made a separate issue for this: #39397 -- Ticket URL: <https://trac.macports.org/ticket/39320#comment:11> MacPorts <http://www.macports.org/> Ports system for OS X