[Buildroot] ldconfig - unknown machine 40
cir.vfi at gmail.com
Tue Jul 2 11:49:48 UTC 2013
On Luan, 2013-07-01 at 19:25 -0300, Milton Soares Filho wrote:
> On 28 June 2013 13:55, Ciarán Rehill <cir.vfi at gmail.com> wrote:
> > /sbin/ldconfig: /lib/libnsl.so.1 is for unknown machine 40.
> > [...]
> > *** Firstly, anyone else seeing this? Searching doesn't turn up much.
> Me too! Trying to build a ST sh4 target using an external toolchain.
> My host machine has Ubuntu 13.04 x86-64 installed and ships ldconfig
> version 2.17.
Is it normal not to supply a cross-ldconfig with a toolchain release or
is there a standard policy on this?
> > *** Most importantly, any ideas on how to successfully use Buildroot on an
> > F18 machine for ARM (or any non-Intel arch, I suppose)?
> Still have no idea on how to fix this issue, since my external
> toolchain is pre-compiled and does not ship cross-ldconfig within it.
> I have done a workaround using LD_LIBRARY_PATH on the target
> initialization scripts, but assuming it's a sub-optimal solution.
Is it possible to build the ldconfig from source without going through a
full toolchain build process, given that the majority of the components
already exist? Maybe some essential parts are lost in the binary
distribution and there's still the need to use that intermediate stage
toolchain to generate this. I saw some other traffic on the list
mentioning that stage may not be necessary any more though, but it may
not be relevant here. Any toolchain experts want to chime in?
More information about the buildroot