Date: Wed, 21 Mar 2012 07:28:35 -0400 From: George Mitchell <george@m5p.com> To: freebsd-ports@freebsd.org Subject: Re: libxcb-related breakage in ports Message-ID: <4F69BB63.30001@m5p.com> In-Reply-To: <CAN6yY1vGu1x-V5CtFUZ181Rt0gbRAoV2xgOiCejogAG891K41A@mail.gmail.com> References: <201203201948.q2KJmZ5A017485@m5p.com> <4F68E6C5.7090007@acsalaska.net> <4F690448.7080006@m5p.com> <4F691E2F.1050209@acsalaska.net> <CAN6yY1vGu1x-V5CtFUZ181Rt0gbRAoV2xgOiCejogAG891K41A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/21/12 01:52, Kevin Oberman wrote: > On Tue, Mar 20, 2012 at 5:17 PM, Mel Flynn<rflynn@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@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-*). > > 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. Thanks for this pointer, too, and above all thanks for reminding me to read /usr/ports/UPDATING -- I'm too used to "portmaster -a -D" just magically doing the right thing for me. I wonder if we could get portmaster to parse command lines out of /usr/ports/UPDATING ... -- George
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F69BB63.30001>