search

zhemao / zhemao.github.com

Github pages page
http://zhemao.github.com
Other
4 stars 1 forks source link

Problem in part II with rootfs. #9

Closed nigelatta closed 10 years ago

nigelatta commented 10 years ago

Thanks for the interesting blog. Just looking for some pointers with creating the rootfs. I have tried following the procedure several times. Everything seems to build ok and the SD card looks good, but the boot process fails just after the root file system mounts with the following:-

VFS: Mounted root (ext3 filesystem) on device 179:2. devtmpfs: mounted Freeing init memory: 260K /sbin/init: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory

There is a link for libc.so.6 in the lib folder pointing to libc-2.18-2013.10.so. Any clues as to what I'm missing?

Thanks,

Nigel.

zhemao commented 10 years ago

Well that's rather odd. Have you checked that libc-2.18-2013.10.so? You are using Buildroot, right? I don't see any reason why this would be happening.

zhemao commented 10 years ago

Could you try this image and tell me if it works?

nigelatta commented 10 years ago

Yes, I am using Buildroot-2013.11, and I can confirm that using the image above boots ok. I have also followed the Arrow sockit flow and built using Yocto which also boots ok. I see that in your image the linked file is libc-2.15.so and mine is libc-2.18-2013.10.so, although I don't see why that would be a problem as the file has the correct permissions.

kmonkey331 commented 10 years ago

It sounds like the same problem I had... https://bugs.launchpad.net/gcc-linaro/+bug/1208945

My solution was to add two symbolic links to the rootfs before copying it to the sd-card. ln -s /lib /lib/arm-linux-gnueabihf ln -s /usr/lib /usr/lib/arm-linux-gnueabihf

zhemao commented 10 years ago

@nigelatta What version of the cross compiler are you using? Perhaps using a different version will solve your problem.

nigelatta commented 10 years ago

I was trying to follow your steps so I was using the linked to version (4.8-2013.11). The symbolic links mentioned above fix the issue. Many thanks to you both for your help.