Re: [ARMedslack] Creating a rootfs from a x86 host: unknown machine 40
Does your 64 bit system have multybit capabilites ? (ie can you run 32 bit stuff along with the 64 bit stuff ?) If you did that the update may have broken some of the 32 bit stuff and it could lead you to a similar error. ATB David Il Domenica 17 Novembre 2013 3:04, openpand...@free.fr openpand...@free.fr ha scritto: Thanks ! I appreciate. - Mail original - De: Stuart Winter m-li...@biscuit.org.uk À: Slackware ARM port armedslack@lists.armedslack.org 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; 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).' He's right - it's broken. There's a patch that's in Gentoo and Red Hat, but it doesn't fix this problem. There's also this one which I haven't tried: http://patchwork.ozlabs.org/patch/255486/ You're going to have to either try the patch in the last URL and rebuild glibc with it, or take the ldconfig from Slackware 14.0 -- works for me: cd slackware64-14.0/slackware64/l mkdir Q ; cd Q tar xf ../glibc-2.15-x86_64-7.txz cp sbin/ldconfig /sbin/ldconfig-2.15 Go into a dir of ARM shared objects: prisere [p3] # readelf lib/ld-2.17.so -h|grep Machin Machine: ARM prisere [p3] # uname -m x86_64 prisere [p3] # /sbin/ldconfig-2.15 -r . prisere [p3] # strings etc/ld.so.cache |head -n5 ld.so-1.7.0 glibc-ld.so.cache1.1G libz.so.1 /lib/libz.so.1 libuuid.so.1 prisere [p3] # ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Creating a rootfs from a x86 host: unknown machine 40
No - it's pure 64bit. On Mon, 18 Nov 2013, Davide wrote: Does your 64 bit system have multybit capabilites ? (ie can you run 32 bit stuff along with the 64 bit stuff ?) If you did that the update may have broken some of the 32 bit stuff and it could lead you to a similar error. ATB David Il Domenica 17 Novembre 2013 3:04, openpand...@free.fr openpand...@free.fr ha scritto: Thanks ! I appreciate. - Mail original - De: Stuart Winter m-li...@biscuit.org.uk À: Slackware ARM port armedslack@lists.armedslack.org 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; 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).' He's right - it's broken. There's a patch that's in Gentoo and Red Hat, but it doesn't fix this problem. There's also this one which I haven't tried: http://patchwork.ozlabs.org/patch/255486/ You're going to have to either try the patch in the last URL and rebuild glibc with it, or take the ldconfig from Slackware 14.0 -- works for me: cd slackware64-14.0/slackware64/l mkdir Q ; cd Q tar xf ../glibc-2.15-x86_64-7.txz cp sbin/ldconfig /sbin/ldconfig-2.15 Go into a dir of ARM shared objects: prisere [p3] # readelf lib/ld-2.17.so -h|grep Machin Machine: ARM prisere [p3] # uname -m x86_64 prisere [p3] # /sbin/ldconfig-2.15 -r . prisere [p3] # strings etc/ld.so.cache |head -n5 ld.so-1.7.0 glibc-ld.so.cache1.1G libz.so.1 /lib/libz.so.1 libuuid.so.1 prisere [p3] # ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack -- Stuart Winter Slackware ARM: http://arm.slackware.com___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Creating a rootfs from a x86 host: unknown machine 40
Thanks ! I appreciate. - Mail original - De: Stuart Winter m-li...@biscuit.org.uk À: Slackware ARM port armedslack@lists.armedslack.org 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; 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).' He's right - it's broken. There's a patch that's in Gentoo and Red Hat, but it doesn't fix this problem. There's also this one which I haven't tried: http://patchwork.ozlabs.org/patch/255486/ You're going to have to either try the patch in the last URL and rebuild glibc with it, or take the ldconfig from Slackware 14.0 -- works for me: cd slackware64-14.0/slackware64/l mkdir Q ; cd Q tar xf ../glibc-2.15-x86_64-7.txz cp sbin/ldconfig /sbin/ldconfig-2.15 Go into a dir of ARM shared objects: prisere [p3] # readelf lib/ld-2.17.so -h|grep Machin Machine: ARM prisere [p3] # uname -m x86_64 prisere [p3] # /sbin/ldconfig-2.15 -r . prisere [p3] # strings etc/ld.so.cache |head -n5 ld.so-1.7.0 glibc-ld.so.cache1.1G libz.so.1 /lib/libz.so.1 libuuid.so.1 prisere [p3] # ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
