On Sat, 25 Feb 2017 13:23:11 +0100, meino.cra...@gmx.de wrote:
> make bImage fails with
>
> (chroot) make bzImage
> CHK include/config/kernel.release
> CHK include/generated/uapi/linux/version.h
> CHK include/generated/utsrelease.h
> CHK include/generated/bounds.h
> CHK include/generated/timeconst.h
> CHK include/generated/asm-offsets.h
> CALL scripts/checksyscalls.sh
> CHK include/generated/compile.h
> ./scripts/gen_initramfs_list.sh: Cannot open
> '/usr/share/v86d/initramfs' make[1]: *** [usr/Makefile:73:
> usr/initramfs_data.cpio.gz] Error 1 make: *** [Makefile:988: usr] Error
> 2
>
>
> I look for the magic v83d and found (being at my old root)
>
> [I] sys-apps/v86d
> Available versions: 0.1.10 {debug x86emu}
> Installed versions: 0.1.10(02:34:27 02/28/11)(x86emu -debug)
> Homepage:
> https://dev.gentoo.org/~spock/projects/uvesafb/ Description: A
> daemon to run x86 code in an emulated environment
>
> Is this "quite normal" or does the make process of the kernel make
> false conclusion while being chrooted?
>
> Do I really need initram? ... For years I though my grub had
> booted the kernel which runs my linux directlu...
Since kernel 2.6 (I think) the kernel has always had an initramfs built
in, this is separate from the standalone initramfs files built by the
likes of dracut. It is empty by default but it is there, so it is not
surprising to see build output relating to the intiramfs even if you do
not use one.
Are you cross-compiling here? That's the obvious reason for requiring
v86d. If not, there is no need to chroot to build a kernel, just cd to
its directory, although chrooting is needed to run make
{,modules_}install.
--
Neil Bothwick
USENET: Uniting Spammers, Erotomaniacs, Newbies, Extroverts and Trolls
pgpQqHXLbzhrA.pgp
Description: OpenPGP digital signature
