crosstool-ng 1.18.0 for x86_64 : No init found

crosstool-ng 1.18.0 for x86_64 : No init found

[Zvi Vered]

Hello,

I created an x86_64 toolchain for linux  3.4.38

Same procedure was used to create an x86 toolchain.

When I lanuched the kernel (compile with ARCH=x86_64) I got:

Kernel Panic - not syncing: No init found

Busybox was compiled without ARCH.

What can cause this problem ?

Best regards,
Z.V

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: crosstool-ng 1.18.0 for x86_64 : No init found

[Zvi Vered]

Hello,

The cause to the problem:
I had to add /lib64 in file system that contains 3 symbolic links to 
libraries in /lib
I ran:
readelf –l busybox

and found that busybox is looking for a specific library in /lib64 (which 
was already in /lib)

After solving the problem, and running linux I ran:
more /proc/version

There is no evidence that this is a 64 bits linux.
Can you tell why ?

Regards,
Z.V

From: Reinoud Koornstra
Sent: Tuesday, February 16, 2016 5:47 AM
To: Zvi Vered
Cc: crossgcc@sourceware.org
Subject: Re: crosstool-ng 1.18.0 for x86_64 : No init found



On Feb 15, 2016 7:35 PM, "Zvi Vered" <veredz72@gmail.com> wrote:
>
> Hello,
>
> I created an x86_64 toolchain for linux  3.4.38
>
> Same procedure was used to create an x86 toolchain.
>
> When I lanuched the kernel (compile with ARCH=x86_64) I got:
>
> Kernel Panic - not syncing: No init found
>
> Busybox was compiled without ARCH.
>
> What can cause this problem ?

It can be multiple things, problem with the filesystem, it can also be that 
the initramfs wasn't created correctly. Missing symlink is also possible.

Without more info it's impossible to say. If you create the kernel for 
x86_64 you should create userland binaries and busybox for x86_64 as well.
>
> Best regards,
> Z.V
>
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
>



--
For unsubscribe information see http://sourceware.org/lists.html#faq