All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxim Fomin <maxim@fomin.one>
To: "grub-devel@gnu.org" <grub-devel@gnu.org>
Cc: development@efficientek.com, "dkiper@net-space.pl" <dkiper@net-space.pl>
Subject: Re: [PATCH v8 1/1] plainmount: Support plain encryption mode
Date: Wed, 28 Dec 2022 18:05:11 +0000	[thread overview]
Message-ID: <0Qcs75cDPyZfsiuxG6njat8bl8S2RLSEPOyQNBGr3vGUBziWT8GCHRUMp9nrKqqR2J9ThXBQys_UQ21Zkm61j2RNO1fDJp_LttHDm2eqjfI=@fomin.one> (raw)
In-Reply-To: <20221223200933.3deeaf81@crass-HP-ZBook-15-G2>

------- Original Message -------
On Saturday, December 24th, 2022 at 2:09 AM, Glenn Washburn <development@efficientek.com> wrote:
> 
> On Fri, 23 Dec 2022 19:54:47 -0600
> Glenn Washburn development@efficientek.com wrote:
> 
> > On Fri, 02 Dec 2022 17:11:23 +0000
> > Maxim Fomin maxim@fomin.one wrote:
> > 
> > > ------- Original Message -------
> > > On Friday, December 2nd, 2022 at 0:00, Glenn Washburn
> > > development@efficientek.com wrote:
> > > 
> > > > I'm now compiling this patch and found a few compile issues below.
> > > > You're compile testing this right?
> > > 
> > > First versions of the patch were tested in pure grub src directory.
> > > Later I switched to directly making and installing GRUB package for
> > > my distro using its source script syntax. It seems this process was
> > > affected by environment options which hided these errors/warnings.
> > > 
> > > I test the patch on my two old laptops - one with UEFI BIOS
> > > (x86_64-efi) and one is pre-UEFI (i386-pc). I was compiling i386-pc
> > > target too, because otherwise the second laptop was unbootable.
> > > During i386-pc compilation I noticed some warnings related to
> > > 'PRIuGRUB_XXX' macros which were absent during efi target
> > > compilation. I noticed that there are similar warnings in other
> > > modules and decided that there are issues with 'PRIuGRUB_XXX' macros
> > > at i386-pc platform at global level. In any case, these issues
> > > didn't cause compilation fail in my working environment because I
> > > would not be able to compile and boot pre-UEFI lap. Do you use
> > > -Werror?
> > 
> > I didn't see this until just now. In case you're still interested, no
> > I don't use -Werror or any special compiler flags. And I'm using gcc
> > version 10.2.1 from a Debian 11 container.
> 
> 
> Correction, -Werror is being used. Perhaps that's a default compiler
> flag on Debian systems.
> 
> Glenn
> 

This explains why you have found these issues. However, it does not explain
how you can compile grub with -Werror because currently there are following
warnings in x86_64-efi mode:
grub-core/lib/libgcrypt-grub/mpi/mpi-internal.h:150:24: warning: variable ‘_ql’ set but not used [-Wunused-but-set-variable]
grub-core/lib/libgcrypt-grub/mpi/mpih-div.c:53:9: warning: variable ‘dummy’ set but not used [-Wunused-but-set-variable]

When I was working with the patch earlier this year I remember having these
and several more warnings which prevented me from using -Werror. Back then
I have removed the switch and have forgotten about this issue completely.

Best regards,
Maxim Fomin



  reply	other threads:[~2022-12-28 18:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-29 17:40 [PATCH v8 1/1] plainmount: Support plain encryption mode Maxim Fomin
2022-11-29 17:13 ` Daniel Kiper
2022-12-01  5:58   ` Glenn Washburn
2022-12-01 19:38     ` Daniel Kiper
2022-12-02 16:41   ` Maxim Fomin
2022-12-01 21:00 ` Glenn Washburn
2022-12-02 17:11   ` Maxim Fomin
2022-12-24  1:54     ` Glenn Washburn
2022-12-24  2:09       ` Glenn Washburn
2022-12-28 18:05         ` Maxim Fomin [this message]
2023-01-10 18:19           ` Glenn Washburn
2023-01-14 12:07             ` Maxim Fomin

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='0Qcs75cDPyZfsiuxG6njat8bl8S2RLSEPOyQNBGr3vGUBziWT8GCHRUMp9nrKqqR2J9ThXBQys_UQ21Zkm61j2RNO1fDJp_LttHDm2eqjfI=@fomin.one' \
    --to=maxim@fomin.one \
    --cc=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.