From: David Laight <David.Laight@ACULAB.COM>
To: "'H. Peter Anvin'" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Borislav Petkov <bp@alien8.de>, Andy Lutomirski <luto@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Kbuild Mailing List" <linux-kbuild@vger.kernel.org>
Subject: RE: [PATCH 0/3] x86 disk image and modules initramfs generation
Date: Tue, 20 Apr 2021 08:30:07 +0000 [thread overview]
Message-ID: <75fc46bae17f4fa4958f5ad7d49d9244@AcuMS.aculab.com> (raw)
In-Reply-To: <20210419230252.1583169-1-hpa@zytor.com>
From: H. Peter Anvin
> Sent: 20 April 2021 00:03
>
> When compiling on a different machine than the runtime target,
> including but not limited to simulators, it is rather handy to be able
> to produce a bootable image. The scripts for that in x86 are
> relatively old, and assume a BIOS system.
I've given up and copied the kernel tree onto all my test systems.
I needed something like 'make modules_install' and 'make install'
that would generated a directory tree that could be copied (scp -r)
onto the target system.
But the script to run 'update-grub' is all intwined in the commands.
You also don't get a copy of the headers.
Even for the local system (as root) you just get a symlink into
the source tree.
This causes a problem trying to build 'out of tree' modules
after updating the kernel source tree (but not rebulding).
I can (and do) write 'horrid' makefiles (gmake and nmake)
but this seemed to need more refactoring that I wanted to do.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2021-04-20 8:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 23:02 H. Peter Anvin
2021-04-19 23:02 ` [PATCH v2 1/3] x86/boot: Modernize genimage script; hdimage support; remove bzlilo H. Peter Anvin
2021-04-19 23:02 ` [PATCH v2 2/3] usr, modules: Add build target for creating a modules initramfs image H. Peter Anvin
2021-04-22 18:55 ` Masahiro Yamada
2021-04-19 23:02 ` [PATCH v2 3/3] x86/boot: Add option to add modules.img to {fd,hd,iso}image H. Peter Anvin
2021-04-20 8:30 ` David Laight [this message]
2021-04-20 8:39 ` [PATCH 0/3] x86 disk image and modules initramfs generation H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2021-04-19 20:54 H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=75fc46bae17f4fa4958f5ad7d49d9244@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®