Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Mar 2012 01:17:51 +0100
From:      Mel Flynn <rflynn@acsalaska.net>
To:        freebsd-ports@freebsd.org
Subject:   Re: libxcb-related breakage in ports
Message-ID:  <4F691E2F.1050209@acsalaska.net>
In-Reply-To: <4F690448.7080006@m5p.com>
References:  <201203201948.q2KJmZ5A017485@m5p.com> <4F68E6C5.7090007@acsalaska.net> <4F690448.7080006@m5p.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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@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[3]: *** [xfwm4-workspace-settings] Error 1
>>> gmake[3]: Leaving directory
>>> `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs'
>>> gmake[2]: *** [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-*).
-- 
Mel



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F691E2F.1050209>