[Buildroot] ldconfig - unknown machine 40

cir.vfi at gmail.com cir.vfi at gmail.com
Wed Jul 3 21:49:26 UTC 2013

Milton Soares Filho wrote
> On 2 July 2013 08:49, Ciarán Rehill <

> cir.vfi@

> > wrote:
>> Is it normal not to supply a cross-ldconfig with a toolchain release or
>> is there a standard policy on this?
> I haven't found a cross-ldconfig within both sh4 and broadcom
> toolchains which I have available.

Same story with the cross compiler in the yum repos for Fedora
(gcc-arm-linux-gnu): no ldconfig.

Anyway, what seems to be a (dirty) workaround is to take the
"/sbin/ldconfig.real" from a Ubuntu 12.04 system and place it into the
cross-compiler bin/ directory, renaming with the toolchain tuple,
"~/CodeSourcery/Sourcery_G++/bin/arm-none-linux-gnueabi-ldconfig" in this
case.  The file can be extracted from a .rpm or .deb for the appropriate
I know it's wrong, but it gets over this bump in the absence of a better
solution.  Hopefully one of the elders of the list will suggest something
more appropriate.

View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/ldconfig-unknown-machine-40-tp47588p47834.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

More information about the buildroot mailing list