From: Hans Ulrich Niedermann <hun@n-dimensional.de>
To: grub-devel@gnu.org
Subject: Re: [MULTIBOOT2 SPEC PATCH v3 3/4] multiboot2: Make example kernel build at least for i386
Date: Thu, 14 May 2020 07:26:18 +0200 [thread overview]
Message-ID: <20200514072618.4f084b36@n-dimensional.de> (raw)
In-Reply-To: <20200513162428.o2fvck445yxiknwh@tomti.i.net-space.pl>
On Wed, 13 May 2020 18:24:28 +0200
Daniel Kiper <dkiper@net-space.pl> wrote:
> On Fri, May 08, 2020 at 06:50:48AM +0200, Hans Ulrich Niedermann
> wrote:
> > The example kernel has assembly language boot code for both
> > i386 and mips, but the mips assembly code used to be built
> > unconditionally, even if the build is using non-mips build
> > tools such as for x86_64 or i386.
> >
> > This makes the example kernel build at least for i386, both
> > on i386 and on x86_64 hosts.
> >
> > * renames the i386 boot code from boot.S to boot_i386.S
> > to go along with the mips boot code in boot_mips.S
> >
> > * adds AC_CANONICAL_HOST to select the proper boot code:
> >
> > * i386 if building on x86_64 (adds -m32) or on i[3456]86
> > * mips if building for mips*
> > * do not build the kernel if building for another system
> >
> > * adds m4 quoting and uses AS_HELP_STRING use in configure.ac
> >
> > * fixes the name of the constants used in boot_i386.S
> > to use the actual constant names from multiboot2.h
> >
> > * documents both boot_i386.S and boot_mips.S in the
> > multiboot.texi page
>
> May I ask you to split this patch into logical parts?
Being a little slow on the uptake, I only just figured out why I ended
up with that big of a patch.
When given a building and working source tree, I usually make my commits
such that they are small, self-contained and keep the source tree in a
building and working state.
That is why I usually add changes until it finally builds/works.
However, that is a useless argument here, as the state of the source
tree *before* my change is non-building maybe-working, so if the source
tree does not build *after* my small, self-contained change, my change
has not made it worse and can thusly still be considered good.
Changing my normal modus operandi accordingly; considering failing
builds as normal for now.
Expect a good dozen patches in a day or two.
Uli
next prev parent reply other threads:[~2020-05-14 5:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 4:50 [MULTIBOOT2 SPEC PATCH v3 0/4] multiboot2: Clean up the example kernel Hans Ulrich Niedermann
2020-05-08 4:50 ` [MULTIBOOT2 SPEC PATCH v3 1/4] multiboot2: Allow autogen.sh to run with current gnulib Hans Ulrich Niedermann
2020-05-13 16:10 ` Daniel Kiper
2020-05-08 4:50 ` [MULTIBOOT2 SPEC PATCH v3 2/4] multiboot2: Use .gitignore files Hans Ulrich Niedermann
2020-05-13 16:21 ` Daniel Kiper
2020-05-13 20:55 ` Hans Ulrich Niedermann
2020-05-13 21:11 ` Hans Ulrich Niedermann
2020-05-14 5:49 ` Hans Ulrich Niedermann
2020-05-08 4:50 ` [MULTIBOOT2 SPEC PATCH v3 3/4] multiboot2: Make example kernel build at least for i386 Hans Ulrich Niedermann
2020-05-13 16:24 ` Daniel Kiper
2020-05-14 5:26 ` Hans Ulrich Niedermann [this message]
2020-05-08 4:50 ` [MULTIBOOT2 SPEC PATCH v3 4/4] multiboot2: fix example kernel header tag alignment Hans Ulrich Niedermann
2020-05-13 16:34 ` Daniel Kiper
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=20200514072618.4f084b36@n-dimensional.de \
--to=hun@n-dimensional.de \
--cc=grub-devel@gnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.