Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Jan 2012 23:27:46 -0600
From:      "Conrad J. Sabatier" <conrads@cox.net>
To:        Kevin Oberman <kob6558@gmail.com>
Cc:        kwm@freebsd.org, x11@freebsd.org
Subject:   Re: libxcb 1.8
Message-ID:  <20120125232746.627fe2dd@cox.net>
In-Reply-To: <CAN6yY1uB2ky8on8hBJ-jP_wJdOEPre-sCge2Xuho4KEQAxQVWA@mail.gmail.com>
References:  <20120125205727.GP2726@deviant.kiev.zoral.com.ua> <CAHrc_evG7MAfaqk9-fXaHeagJ6tk0nkjaxqMFtpEW1byFmxo2g@mail.gmail.com> <20120125200433.52d26eba@cox.net> <CAN6yY1uB2ky8on8hBJ-jP_wJdOEPre-sCge2Xuho4KEQAxQVWA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 25 Jan 2012 20:34:20 -0800
Kevin Oberman <kob6558@gmail.com> wrote:

> On Wed, Jan 25, 2012 at 6:04 PM, Conrad J. Sabatier <conrads@cox.net>
> wrote:
> > On Wed, 25 Jan 2012 22:17:30 +0100
> > Sebastian Chmielewski <chmiels@o2.pl> wrote:
> >
> >> 2012/1/25 Kostik Belousov <kostikbel@gmail.com>
> >>
> >> > This is a note that updating libxcb from xorg-dev to 1.8 killed
> >> > my client-side X. Every client using libxcb hangs on start,
> >> > eating 100% CPU in the poll(2) loop. Downgrading to 1.7 fixed
> >> > the issue.
> >> >
> >> > Not much useful, but I hope to get less mail after the notice.
> >> >
> >>
> >> I have the same issue. Rebuilding libxcb, xcb-util didn't help.
> >
> > I experienced the same roughly a week ago, and reported it on the
> > xorg mailing list (xorg@lists.x.org). =A0Reverting to 1.7 was
> > absolutely necessary. =A0I considered for a while upgrading every
> > port that depended on libxcb, but according to pkg_info, that came
> > out to be roughly 750+ packages(!). =A0No thank you. =A0:-)
>=20
> pkg_info may list 750+ ports, but that includes both build depends
> (which really need to be re-built) and run-time depends which just
> link to the .so and don't. Install sysutils/bsdadminscripts and use
> 'pkg_libchk -o' to get a list of the ports that REALLY need
> rebuilding. It's probably only a dozen or less as libxcb is typically
> only used by linking to the .so.

Thanks!  I just *knew* there had to be a way to do that, but it just
wasn't coming to me.

Much obliged.  :-)

I'm finding now that the biggest problem I'm having is all these ports
that depend on xcb-util, due to the removal of libxcb-{atom,aux,event}.*

I'm currently rebuilding a whole slew of things after having
sed-replaced all references to these in /usr/local/lib/*.la with
libxcb-util.  Making progress.  :-)

--=20
Conrad J. Sabatier
conrads@cox.net



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