public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nagatoro <nagatoro@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Strange KDE/gcc upgrade
Date: Tue, 06 Dec 2005 19:47:06 +0100	[thread overview]
Message-ID: <4395DCAA.3050207@gmail.com> (raw)
In-Reply-To: <7573e9640512060909l1189e198paae8800cb24cdf8c@mail.gmail.com>

Richard Fish wrote:
> You can check both.  The ldd output of a binary shows the complete
> dependancy tree.  You can then check individual libraries.  The
> following script should identify the 'offender':
> 
> for x in `ldd /usr/kde/3.5/bin/kview | awk '{ print $3}' | grep lib` ; do
>   echo $x
>   ldd $x
changed this to ldd $x | grep libstdc++.so.5
>   read
> done
> 
> Just press "enter" to move from one library to the next...

Thanks!

This shows me that kview and some of it's libraries link to 
libstdc++.so.5. Or am I missreading the display (libstdc++.so.5 shows up 
both for kview and some of the libs)?

I not back to the former question should kview link directly to 
libstdc++.so.5 at all?

-- 
Naga
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-12-06 18:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-06 11:11 [gentoo-user] Strange KDE/gcc upgrade Nagatoro
2005-12-06 12:42 ` Jan Callewaert
2005-12-06 13:27   ` Nagatoro
2005-12-06 14:16     ` Peter Ruskin
2005-12-06 14:54       ` Nagatoro
2005-12-06 15:24         ` Richard Fish
2005-12-06 16:53           ` Nagatoro
2005-12-06 17:09             ` Richard Fish
2005-12-06 18:47               ` Nagatoro [this message]
2005-12-06 20:09                 ` Richard Fish
2005-12-06 20:31                   ` Nagatoro
2005-12-06 23:00               ` cucu ionut cristian
2005-12-07  3:00                 ` Richard Fish
2005-12-07 20:06                   ` cucu ionut cristian
2005-12-06 15:28         ` Graham Murray

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=4395DCAA.3050207@gmail.com \
    --to=nagatoro@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