64 here too. I also went multilib, same problem.
As recommended, going to 14.0 ldconfig works like a charm.
- Mail original -
De: "Stuart Winter"
À: "Slackware ARM port"
Envoyé: Lundi 18 Novembre 2013 11:17:58
Objet: Re: [ARMedslack] Creating a rootfs from a x86 host
o a similar error.
>
> ATB
> David
>
>
>
>
> Il Domenica 17 Novembre 2013 3:04, "openpand...@free.fr"
> ha scritto:
>
> Thanks !
> I appreciate.
>
> - Mail original -
> De: "Stuart Winter"
> À: "Slackware ARM port"
ee.fr"
ha scritto:
Thanks !
I appreciate.
- Mail original -
De: "Stuart Winter"
À: "Slackware ARM port"
Envoyé: Dimanche 17 Novembre 2013 00:00:26
Objet: Re: [ARMedslack] Creating a rootfs from a x86 host: unknown machine 40
> "'These are _not_
Thanks !
I appreciate.
- Mail original -
De: "Stuart Winter"
À: "Slackware ARM port"
Envoyé: Dimanche 17 Novembre 2013 00:00:26
Objet: Re: [ARMedslack] Creating a rootfs from a x86 host: unknown machine 40
> "'These are _not_ just warnings; ldconfi
> "'These are _not_ just warnings; ldconfig ignores the library content, so
> "output/target/etc/ld.so.cache" is left unpopulated, meaning that the
> target device will not boot successfully due to missing libraries (the
> libraries are on the file-system, just the ld.so.cache does not list them).
Hi !
After my upgrade from x86_64 14.0 to 14.1, my pandora rootfs doesn't work
anymore.
Can't find init.
My creation logs show this:
Executing install script for glibc-solibs-2.17-arm-14.tgz.
install/doinst.sh: line 38: sbin/ldconfig: cannot execute binary file
/sbin/ldconfig: ld-2.17.so is for
