* Michael Etscheid (Hp.kellner@web.de) wrote:
Sorry for sending first e-mail html formated...
Hello,
Hello Michael,
I started translating the packages from the crux-arm project.
1st ToolchainSetup was OK
2nd PkgutilsCross was OK
3. buildingPackages returns the error messages "/sbin/ldconfig: /lib/libm.so.6 is for unknown machine 40." after compiling glibc.
Once the /etc/ld.so.conf file exists in the toolchain directory, pkgadd calls ldconfig, which fails.
This is a know issue. You'll see the error but packages are built properly. It's a bit annoying to see those errors when pkgadd-cross your packages into your CLFS, but you can check with objdump the created binaries and verify they are for ARM arch.
I found hints on the Internet that from version 2.16 ldconfig no longer accepts the libraries of type EM_ARM if it was compiled for X86 and ejects the error messages from above. What is the recommended procedure? Do I need a compile environment with glibc < 2.16 or is there an adaptation for glibc 2.23/2.24, so that ldconfig also supports libraries of type ARM.
Go ahead building packages since the error should not affect the result. By the way... why starting from the worse task? Why are you cross compiling? You have a prebuilt generic release ready to be deployed to any compat ARM device which can be customized for your needs. Are you working with an old device? Customizing core ports? Learning?
Thanks Helmut _______________________________________________ Regards,
--- Victor Martinez Learning bit by bit | http://vjml.es