Created attachment 244828 [details] poudriere-cairomm-1.12.2_6.log I get a package build failure for cairomm in my poudriere since a few days back. A wild guess is that this is caused because of OPTIONS_UNSET+= X11. See the failure snipped below and the attached poudriere build log. =======================<phase: package >============================ ===> Building package for cairomm-1.12.2_6 pkg-static: Unable to access file /wrkdirs/usr/ports/graphics/cairomm/work/stage/usr/local/libdata/pkgconfig/cairomm-xlib-1.0.pc:No such file or directory pkg-static: Unable to access file /wrkdirs/usr/ports/graphics/cairomm/work/stage/usr/local/libdata/pkgconfig/cairomm-xlib-xrender-1.0.pc:No such file or directory *** Error code 1 Stop. make: stopped in /usr/ports/graphics/cairomm
Looking more closely, this was (for me) caused by the updated net-p2p/transmission port. Previously I built transmission without QT/GTK/X11, but when the port moved to flavor it defaulted to the transmission-full flavor with GUI support; adding dependencies like cairomm and other X11 libraries. Building net-p2p/transmission@daemon instead of net-p2p/transmission was the solution for me. I'm not sure if this is a bug that should be fixed or if should be sorted under user error...
(In reply to Fredrik Eriksson from comment #1) I think you are referring to net-p2p/transmission-components which is flavored instead of net-p2p/transmission which has options for the different components. What I fail to see is how can cairomm fail to build because an unrelated software that depends on it builds with a certain flavor. Certainly this could happen the other way around, but I'm puzzled about the workaround you found.
There has been a bit of action around the transmission port lately. I ran in to this when the port moved to flavors after this commit: https://cgit.freebsd.org/ports/commit/?id=8da970ab75e1a1031d93ff8e1aa8e3ff71afef07 Now it has been reorganized to a meta port and the flavors moved to net-p2p/transmission-components: https://cgit.freebsd.org/ports/commit/?id=ac3e39992e95659a5193a15d4cb873efb00fcb30 Nevertheless, I think the bug was not *caused* by the transmission port, it's more probable that it was found *because* of it. The poudriere environment I used to build the port is not configured to build GUI applications; having the following options unset (more configuration is in the log): OPTIONS_UNSET+= MYSQL PGSQL X11 OPENGL GLESV2 XCB WAYLAND GUI net-p2p_transmission_UNSET= GTK QT Since the transmission port at the time didn't honor the unset of GUI frameworks it dragged in various new dependencies and cairomm was one of them. So my guess about what happened was that one or more of the cairomm dependencies has the X11 option, and cairomm needs it to be set.
(In reply to Fredrik Eriksson from comment #3) Thank you Fredrik for the explanation. That makes sense. I'm not sure this is a bug in the port but a mismatch in the configuration options.