Hi Baruch,
You are right !
Running
readelf -l busybox
gave me a huge clue. Busybox is looking for a library in /lib64 which I did
not create.
/lib64 should contain 3 symbolic links to libraries in /lib
Thank you for your help,
Best regards,
Zvi
-----Original Message-----
From: Baruch Siach
Sent: Tuesday, February 16, 2016 7:56 AM
To: Zvi Vered
Cc: [email protected]
Subject: Re: Busybox 1.20.2 for linux-64
Hi Zvi,
On Tue, Feb 16, 2016 at 04:29:37AM +0200, Zvi Vered wrote:
I’m using busybox 1.20.2 with vanilla 3.4.38 compiled with ARCH=x86.
Now I compiled the same kernel with ARCH=x86_64 with a crosstool-ng
toolchain created for x86_64
Should I compile busybox with ARCH=x86_64 ?
When I compiled busybox with the same x86_64 toolchain and ran the system
I
got:
Kernel Panic - not syncing: No init found
Did you build Busybox statically (CONFIG_STATIC)? If not, do you have all
dependency libraries at the correct location on your root filesystem?
Does chroot into your root filesystem work (with /bin/sh linking to
busybox)?
What should I change when moving to linux 64 bits ?
You may be missing the 64bit dynamic loader in case of dynamic build. Look
for
"program interpreter" in the output of 'readelf -l busybox'.
Hope this helps,
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- [email protected] - tel: +972.2.679.5364, http://www.tkos.co.il -
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
