From: Glenn Washburn <development@efficientek.com>
To: Daniel Kiper <dkiper@net-space.pl>, grub-devel@gnu.org
Cc: Glenn Washburn <development@efficientek.com>
Subject: [PATCH 0/2] Make build more robust
Date: Wed, 12 Jan 2022 21:40:19 -0600 [thread overview]
Message-ID: <cover.1642044782.git.development@efficientek.com> (raw)
I've found these two patches to be necessary under certain build conditions
that I've not been able to narrow down to a specific cause. I suspect it is
related to the values of some build environment variables (like *CFLAGS).
Either way, these patches allow a successful build finishes without error
and where the test suite succeeds. So I believe these patches are allowing
a usable build. Under normal conditions, these changes should be superflous
and thus not affect the build process.
Glenn
Glenn Washburn (2):
gentpl.py: Fix issue where sometimes marker files have CPP defines
Makefile: Only look for @MARKER@ at the start of a line when
generating libgrub_a_init.lst
Makefile.am | 4 ++--
gentpl.py | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
--
2.27.0
next reply other threads:[~2022-01-13 3:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 3:40 Glenn Washburn [this message]
2022-01-13 3:40 ` [PATCH 1/2] gentpl.py: Fix issue where sometimes marker files have CPP defines Glenn Washburn
2022-01-13 3:40 ` [PATCH 2/2] Makefile: Only look for @MARKER@ at the start of a line when generating libgrub_a_init.lst Glenn Washburn
2022-01-20 17:07 ` [PATCH 0/2] Make build more robust 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=cover.1642044782.git.development@efficientek.com \
--to=development@efficientek.com \
--cc=dkiper@net-space.pl \
--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.