pkg/52358: x11/libxcb building inconsistency

[triaxx%triaxx.org@localhost]

>Number:         52358
>Category:       pkg
>Synopsis:       x11/libxcb building inconsistency
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jul 02 09:40:01 +0000 2017
>Originator:     Frederic Fauberteau
>Release:        pkgsrc-2017Q1
>Organization:
>Environment:
NetBSD mutalisk.triaxx.org 7.1 NetBSD 7.1 (GENERIC.201703111743Z) amd64
>Description:
Building of awesome fails on my host due to error from lua-gi and this error is 
related to cairo.

This problem occurs with packages installed from remote binary repositories.

I try to load cairo from lua-gi and get the following error:
>>>>>
$ /usr/pkg/bin/lua5.3
Lua 5.3.4  Copyright (C) 1994-2017 Lua.org, PUC-Rio
> cairo=require("lgi").cairo
/usr/pkg/share/lua/5.3/lgi/override/cairo.lua:31: attempt to index a nil value (field '_module')
stack traceback:
        /usr/pkg/share/lua/5.3/lgi/override/cairo.lua:31: in main chunk
        [C]: in function 'require'
        /usr/pkg/share/lua/5.3/lgi/namespace.lua:176: in function 'lgi.require'
        (...tail calls...)
        stdin:1: in main chunk
        [C]: in ?
<<<<<   

Actually, the problem occurs when GModule loads libcairo.so.2. It is underlined
by the following code:
>>>>>
#include <gmodule.h>

int main(int argc, char **argv)
{
  GModule *module;
  //module = g_module_open("/usr/lib/libcairo.so.2", 0);
  module = g_module_open("libcairo.so.2", 0);
  g_print("addr=%p\n", module);
  g_print("%s\n", g_module_error());

  return 0;
}

$ ./cairo-gmodule
addr=0x0
/usr/pkg/lib/libxcb-shm.so.0: Undefined PLT symbol "xcb_send_request_with_fds" (symnum = 26)
<<<<<

If I rebuild x11/libxcb from my local repository, the problem is resolved. But I 
have no idea to definitly fix it...
>How-To-Repeat:
pkg_delete -f libxcb && pkgin install libxcb

The load of libcairo.so.2 by GModule fails again
>Fix:
Just rebuild the package fixes the error. But no idea what happens on the building host system...