Right, on many systems it is completely unnecessary to run ldconfig, you just copy the library files into /lib or /usr/lib, but on any newer desktop or server, and many newer embedded systems, you MUST run ldconfig after copying the files. As time goes on you will likely see all systems require that ldconfig be run.
On the problem at hand, it is possible that the version of libpthread.so on the TS-7260, and the version he compiled against are different, and the one he compiled against had some symbols that are not in the different version. That is one thing I did not think of before.
I remember having to strip and copy libpthread.so from the dev tools to the TS-7260. Maybe he did not copy the correct version.
Don.
On 11/22/06,
Jim Jackson <> wrote:
All this talk of ldconfig
I simply copied my new libs into /lib and they were found without any
ldconfig stuff being required. You can set the environment
variable LD_LIBRARY_PATH to the set of lib directories if they are
not the usual /lib and /usr/lib (these are built into the loader).
ldconfig is not absolutely necessary.
On Wed, 22 Nov 2006, Robert Ernst wrote:
> > > that works for my system but the TS7260 does not have a ldconfig
> > > or /etc/ld.so/conf
>
> The ldconfig binary for the target should have been built with the
> crosscompiler. If you use the tools from http://www.kegel.com/crosstool/, you
> might find it in a directoy like
>
> /opt/crosstool/gcc-3.3.6-glibc-2.3.2/arm-unknown-linux-gnu/arm-unknown-linux-gnu/sbin
>
> The exact path may vary depending on the version and compile options used when
> building the toolchain. Note that this binary contains the symbols - you
> might want strip the binary to reduce the size.
>
> --
> Robert Ernst
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
-- Dr. Don W. Carr J. G. Montenegro 2258 Guadalajara, Mexico +52-333-630-0704 +52-333-836-4500 ext 2930
__._,_.___
![]()
SPONSORED LINKS
__,_._,___
|