On Tue, 2005-12-06 at 20:00 -0700, Richard Fish wrote:
>
> ldd /bin/bash
found problem: I must use ldd /parth/to/program/program to get the
right result thanks for tip
--
gentoo-user@gentoo.org mailing list
On 12/6/05, cucu ionut cristian <[EMAIL PROTECTED]> wrote:
> I tried the ldd and ldd $x where x is a varios program wich runs fine on
> my system and output is ldd: ./x: No such file or directory
> I guess I shoud have set something somewhere but... don't know what
> where
I'm not sure I understan
> The ldd output of a binary shows the complete
> dependancy tree.
I tried the ldd and ldd $x where x is a varios program wich runs fine on
my system and output is ldd: ./x: No such file or directory
I guess I shoud have set something somewhere but... don't know what
where
--
gentoo-user@gento
Richard Fish wrote:
On 12/6/05, Nagatoro <[EMAIL PROTECTED]> wrote:
I not back to the former question should kview link directly to
libstdc++.so.5 at all?
It probably doesn't. You can check this with:
strings /usr/kde/3.5/bin/kview | grep stdc++
Thanks, it turns out that it does link to b
On 12/6/05, Nagatoro <[EMAIL PROTECTED]> wrote:
> 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/bi
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
ch
On 12/6/05, Nagatoro <[EMAIL PROTECTED]> wrote:
> Richard Fish wrote:
> > Because it is also linking against some other library that you already
> > have installed (Qt, maybe?) that is linked against stdc++.so.5.
>
> Point well taken.
> But would I see this "link" on the actual KDE binaries (eg ldd
Richard Fish wrote:
Because it is also linking against some other library that you already
have installed (Qt, maybe?) that is linked against stdc++.so.5.
Point well taken.
But would I see this "link" on the actual KDE binaries (eg ldd kview) or
would I see this if I checked the QT library tha
Nagatoro <[EMAIL PROTECTED]> writes:
> Yes I've read that too. But why is the newly compiled KDE linking
> against libstdc++.so.5 when it was compiled _after_ the gcc change?
It is probably linking against something (qt perhaps, as the existing
qt was used when I upgraded to kde 3.5) that is itse
On 12/6/05, Nagatoro <[EMAIL PROTECTED]> wrote:
> Peter Ruskin wrote:
> > From http://www.gentoo.org/proj/en/base/x86/gcc-upgrading-guide.xml:
> >
> > # revdep-rebuild --library libstdc++.so.5 -- -pv
> > # revdep-rebuild --library libstdc++.so.5
>
> Yes I've read that too. But why is the newly comp
Peter Ruskin wrote:
From http://www.gentoo.org/proj/en/base/x86/gcc-upgrading-guide.xml:
# revdep-rebuild --library libstdc++.so.5 -- -pv
# revdep-rebuild --library libstdc++.so.5
Yes I've read that too. But why is the newly compiled KDE linking
against libstdc++.so.5 when it was compiled _af
Jan Callewaert wrote:
2005/12/6, Nagatoro <[EMAIL PROTECTED]>:
I've just upgraded my desktop computer to use gcc-3.4 and right after
that I decided to try KDE-3.5. Everything compiled just fine but now i
see that KDE-3.5 is linked against libstdc++.so.5 _and_ libstdc++.so.6.
Does anyone know wh
2005/12/6, Nagatoro <[EMAIL PROTECTED]>:
> Hi,
>
> I've just upgraded my desktop computer to use gcc-3.4 and right after
> that I decided to try KDE-3.5. Everything compiled just fine but now i
> see that KDE-3.5 is linked against libstdc++.so.5 _and_ libstdc++.so.6.
>
> Does anyone know where I've
Hi,
I've just upgraded my desktop computer to use gcc-3.4 and right after
that I decided to try KDE-3.5. Everything compiled just fine but now i
see that KDE-3.5 is linked against libstdc++.so.5 _and_ libstdc++.so.6.
Does anyone know where I've gone wrong?
--
Naga
--
gentoo-user@gentoo.org m
14 matches
Mail list logo
