public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Kazantsev <mk.fraggod@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] *** WARNING *** - upgrade to libxcb-1.4 (-r1) breaks your system
Date: Tue, 15 Sep 2009 16:22:59 +0600	[thread overview]
Message-ID: <20090915162259.59a17bd7@malediction> (raw)
In-Reply-To: <200909150958.58687.alan.mckinnon@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]

On Tue, 15 Sep 2009 09:58:58 +0200
Alan McKinnon <alan.mckinnon@gmail.com> wrote:

> On Tuesday 15 September 2009 09:49:39 Helmut Jarausch wrote:
> > On 15 Sep, Neil Bothwick wrote:
> 
> > > To completely get rid of libxcb-xlib.so references, please read :
> > > http://www.gentoo.org/proj/en/desktop/x/x11/libxcb-1.4-upgrade-guide.xml
> > 
> > Since my browser got broken, too, this took some time.
> > And following that advice takes even much more time, since
> > I have to rebuild half of my system.
> > 
> > Luckily it has 4 cores,
> > Helmut.
> > 
> 
> The gods must be favouring me for a change. I'm completely unaffected
> by this upgrade :-)
> 
> $ sudo /var/portage/x11-libs/libxcb/files/xcb-rebuilder.sh
> Password:
> * Fixing broken libtool archives (.la)
> * Scanning for libraries requiring libxcb-xlib.so...
> * No broken libraries detected
> 
> I wonder what I did different?

Prehaps nothing.
Rebuild warning is triggered by a check for libxcb-xlib.so.0.0.0, which
didn't seem to exist on my system either.
Guess "xcb" use-flag for libX11 is to blame: if it's not set, then
older libX11 brought along it's own libxcb.

-- 
Mike Kazantsev // fraggod.net

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2009-09-15 10:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15  7:35 [gentoo-user] *** WARNING *** - upgrade to libxcb-1.4 (-r1) breaks your system Helmut Jarausch
2009-09-15  7:38 ` Helmut Jarausch
2009-09-15  7:45   ` Neil Bothwick
2009-09-15  7:49     ` Helmut Jarausch
2009-09-15  7:58       ` Alan McKinnon
2009-09-15  8:11         ` Neil Bothwick
2009-09-15  8:34           ` Helmut Jarausch
2009-09-15  9:34             ` Volker Armin Hemmann
2009-09-15 10:13               ` Mike Kazantsev
2009-09-15 10:49             ` Neil Bothwick
2009-09-15  8:51         ` Jorma Airola
2009-09-15  9:01           ` Ward Poelmans
2009-09-15  9:38             ` Alan McKinnon
2009-09-15  9:52             ` Jorma Airola
2009-09-15 10:22         ` Mike Kazantsev [this message]
2009-09-15 11:21           ` Alan McKinnon
2009-09-15 17:14             ` Paul Hartman
2009-09-15 17:56               ` Mark Knecht
2009-09-15  7:46   ` Alan McKinnon
2009-09-15  9:31 ` [gentoo-user] " Nikos Chantziaras
2009-09-15  9:37   ` Boris Fersing
2009-09-15  9:43   ` Volker Armin Hemmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090915162259.59a17bd7@malediction \
    --to=mk.fraggod@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox