gtk{2,3}-x11 fails to build on Darwin

[smaret]

Issue description

gtk{2,3}-x11 fails to build on Darwin with the following message:

checking for CAIRO_BACKEND... no
configure: error: Package requirements (cairo-xlib >= 1.6) were not met:

No package 'cairo-xlib' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables CAIRO_BACKEND_CFLAGS
and CAIRO_BACKEND_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
builder for '/nix/store/dnay7nf0f9g6kli435ibgx8ic5yym67l-gtk+-2.24.32.drv' failed with exit code 1
error: build of '/nix/store/dnay7nf0f9g6kli435ibgx8ic5yym67l-gtk+-2.24.32.drv' failed

Last successful evaluation on Hydra was on April 20.

Steps to reproduce

% nix-build -I. -A gtk2-x11

Technical details

• system: "x86_64-darwin"
• host os: Darwin 18.6.0, macOS 10.14.5
• multi-user?: no
• sandbox: yes
• version: nix-env (Nix) 2.2.2
• channels(smaret): "nixpkgs-19.03pre170546.0f43790d2ce"
• nixpkgs: /nix/store/381kbvy7byjv28l0knxb3s4g9mdmjwi7-master.tar.gz

[matthewbauer]

Probably caused by b7a41a2

[dhruvio]

FYI, I'm still having issues with this, but it may be due to the merged changes from yesterday not yet being available in unstable.

My problem arose from using vim_configurable because it depends on gtk{2,3}. However, it is possible to work around this by eliminating the gtk dependency by overriding the guiSupport parameter. This was useful for me because I use vim from a terminal. See snippet below:

# with gtk{2,3} (old way):
pkgs.vim_configurable.customize { /*...*/ }

# without gtk{2,3} (workaround):
let
overridden = pkgs.vim_confirgurable.override { guiSupport = "false"; };
in
overridden.customize { /*...*/ }

[smaret]

@dhruvio I’ve made another fix in gtk{2,3}-x11 (#61942). Maybe it solves your problem with vim-configurable? If not then I would suggest that you open a new issue that describes it.

[dhruvio]

Looks like it's still not working on macOS without the workaround. I think the problem has to do with the way the vim_configurable package was defined. I'll create another ticket. Thanks @smaret