public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Steven <apartment415@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] binutils broken revdep-rebuild
Date: Thu, 4 Feb 2010 01:59:14 -0800	[thread overview]
Message-ID: <20100204095914.GC29533@tuxradar.vf.shawcable.net> (raw)
In-Reply-To: <4B6A8C42.8060506@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 09:58/02/04/10, Mariusz Ceier wrote:
> W dniu 04.02.2010 08:15, Steven pisze:
> > I am having a recurring error for the last few weeks
> > 
> > revdep-rebuild -p
> > 
> > * Configuring search environment for revdep-rebuild
> > 
> > * Checking reverse dependencies
> > * Packages containing binaries and libraries broken by a package
> > * update
> > * will be emerged.
> > 
> > * Collecting system binaries and libraries
> > * Generated new 1_files.rr
> > * Collecting complete LD_LIBRARY_PATH
> > * Generated new 2_ldpath.rr
> > * Checking dynamic linking consistency
> > [ 37% ]  *   broken
> > /usr/lib64/binutils/x86_64-pc-linux-gnu/2.20/libbfd.la (requires
> > -liberty)
> > *   broken
> > *   /usr/lib64/binutils/x86_64-pc-linux-gnu/2.20/libopcodes.la
> > *   (requires -liberty)
> > [ 100% ]                 
> > * Generated new 3_broken.rr
> > * Assigning files to packages
> > *   /usr/lib64/binutils/x86_64-pc-linux-gnu/2.20/libbfd.la
> > *   -> sys-devel/binutils
> > *   /usr/lib64/binutils/x86_64-pc-linux-gnu/2.20/libopcodes.la
> > *   -> sys-devel/binutils
> > * Generated new 4_raw.rr and 4_owners.rr
> > * Cleaning list of packages to rebuild
> > * Generated new 4_pkgs.rr
> > * Assigning packages to ebuilds
> > * Generated new 4_ebuilds.rr
> > * Evaluating package order
> > * Generated new 5_order.rr
> > * All prepared. Starting rebuild
> > 
> > emerge --oneshot --pretend  sys-devel/binutils:0
> > 
> > I am not to sure how to go about trouble shooting this problem.
> > Everything seems to be running as usual aside from the revdep-rebuild
> > broken error.
> Check if you have /etc/ld.so.conf.d/05binutils and not
> /etc/env.d/00glibc ( this file should contain LDPATH="include
> ld.so.conf.d/*.conf" ), if so - rebuild glibc. If this is not the case,
> maybe try lafilefixer --justfixit.
> 
> HTH

I tried all, and nothing seemed to solve the problem.
I'm at a loss as to what this could be.
When it says "requires -liberty" is liberty part of a package? I am not
sure what it means by -liberty and were to acquire it.

Anyways thanks for the help so far.
- -- 
public key @
apartment415.homelinux.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)

iF4EAREIAAYFAktqmnIACgkQpSa/g4Qb1ZnoMgD+ITaLS9dyio1GHnIXpaiM2vTV
p1aFRUNjURIbOAc3QFwBAMUwmVnQXEJQxVkOiknrOuIQ27RjGZCdJ+BQx7ldQQ3W
=a3HI
-----END PGP SIGNATURE-----



  parent reply	other threads:[~2010-02-04  9:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-04  7:15 [gentoo-user] binutils broken revdep-rebuild Steven
2010-02-04  8:38 ` Alan McKinnon
2010-02-04  8:58 ` Mariusz Ceier
2010-02-04  9:57   ` Stefan Schulte
2010-02-04  9:59   ` Steven [this message]
2010-02-04 11:45     ` Willie Wong
2010-02-04 13:25       ` Mariusz Ceier
2010-02-06  0:03         ` [gentoo-user] " Harry Putnam

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=20100204095914.GC29533@tuxradar.vf.shawcable.net \
    --to=apartment415@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