From: Daniel Kiper via Grub-devel <grub-devel@gnu.org>
To: Andrew Hamilton <adhamilt@gmail.com>
Cc: Daniel Kiper <daniel.kiper@oracle.com>,
grub-devel@gnu.org, floppym@gentoo.org
Subject: Re: [PATCH 0/2] build: Fixes to Building from dist Archive
Date: Fri, 13 Jun 2025 16:41:14 +0200 [thread overview]
Message-ID: <aEw4imWVP7KnKFjq@tomti.i.net-space.pl> (raw)
In-Reply-To: <20250611031546.450792-1-adhamilt@gmail.com>
On Tue, Jun 10, 2025 at 10:15:44PM -0500, Andrew Hamilton wrote:
> Fix several issues with attempting to create and build from the
> GRUB 'dist' archive.
>
> 1. extra_deps.lst is now automatically generated so remove this
> from the archive to avoid a dependency on running make first.
>
> 2. Add additional header files to the dist archive.
>
> The first patch is a resend of Mike Gilbert's from:
> https://mail.gnu.org/archive/html/grub-devel/2025-03/msg00223.html
>
> Testing performed:
> ./bootstrap
> ./configure
> make dist
> Built generated tar.gz with buildroot and confirmed success
> for x86-64.
>
> Andrew Hamilton (2):
> build: remove extra_deps.lst from EXTRA_DIST
> build: Add new header files to dist to allow building from tar
For both patches Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com>...
Daniel
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
next prev parent reply other threads:[~2025-06-13 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 3:15 [PATCH 0/2] build: Fixes to Building from dist Archive Andrew Hamilton
2025-06-11 3:15 ` [PATCH 1/2] build: remove extra_deps.lst from EXTRA_DIST Andrew Hamilton
2025-06-11 3:15 ` [PATCH 2/2] build: Add new header files to dist to allow building from tar Andrew Hamilton
2025-06-13 14:41 ` Daniel Kiper via Grub-devel [this message]
2025-06-24 17:27 ` [PATCH 0/2] build: Fixes to Building from dist Archive Mike Gilbert
2025-06-24 17:36 ` Andrew Hamilton
2025-06-25 12:05 ` 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=aEw4imWVP7KnKFjq@tomti.i.net-space.pl \
--to=grub-devel@gnu.org \
--cc=adhamilt@gmail.com \
--cc=daniel.kiper@oracle.com \
--cc=floppym@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).