libxcb-related breakage in ports
kob6558 at gmail.com
Wed Mar 21 05:52:33 UTC 2012
On Tue, Mar 20, 2012 at 5:17 PM, Mel Flynn <rflynn at acsalaska.net> wrote:
> On 3/20/2012 23:27, George Mitchell wrote:
>> On 03/20/12 16:21, Mel Flynn wrote:
>>> On 3/20/2012 20:48, george+freebsd at m5p.com wrote:
>>>> libtool: link: cannot find the library `/usr/local/lib/libxcb-aux.la'
>>>> or unhandled argument `/usr/local/lib/libxcb-aux.la'
>>>> gmake: *** [xfwm4-workspace-settings] Error 1
>>>> gmake: Leaving directory
>>>> gmake: *** [all] Error 2
>>> You forgot two things:
>>> - pkg_updating xcb
>>> - http://tinyurl.com/7taullk
>> Thanks for the pointer; I will try this out. -- George
> Recovering from not reading /usr/ports/UPDATING is in this case quite a
> bit harder. The method is basically:
> 1) pkg_delete <port that links with old libxcb>
> 2) portmaster <failing port's origin>
> 3) portmaster -r libxcb
> 4) goto 1 if more failures
> Also, you may want to read up on pkg_updating pcre, cause that one's
> even harder to recover from as some ports do braindead things as linking
> to it's old version library during compilation (avahi-*).
Much, much faster is to install sysutils/bsdadminscripts and use
'pkg_libchk -o' | grep xcb to find all of the ports you will need to
re-build. It will probably be no more then low 2 digits while
'portmaster -r libxcb' likely catch a couple of hundred.
R. Kevin Oberman, Network Engineer
E-mail: kob6558 at gmail.com
More information about the freebsd-ports