All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robbie Harwood <rharwood@redhat.com>
To: Daniel Kiper <dkiper@net-space.pl>
Cc: grub-devel@gnu.org, development@efficientek.com
Subject: Re: [PATCH v5 0/4] Update gnulib and drop some patches
Date: Tue, 22 Feb 2022 12:35:00 -0500	[thread overview]
Message-ID: <jlg7d9m6bzv.fsf@redhat.com> (raw)
In-Reply-To: <20220222171751.e6lwotgsi3mvct4t@tomti.i.net-space.pl>

[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]

Daniel Kiper <dkiper@net-space.pl> writes:

> Robbie Harwood wrote:
>
>> I don't get that, actually.  What OS/gcc?  It's fine with the gcc-11
>> I'm using here.
>
> Does gcc-11 work with the configure mentioned above?
>
> Anyway, Debian 9, arm-linux-gnueabihf-gcc (Debian 6.3.0-18) 6.3.0 20170516.

Yes, with arm-linux-gnueabihf-gcc (Debian 11.2.0-16) 11.2.0.

> The GRUB INSTALL file says:
>
>   The Requirements
>   ================
>
>   GRUB depends on some software packages installed into your system. If
>   you don't have any of them, please obtain and install them before
>   configuring the GRUB.
>
>   * GCC 5.1.0 or later
>
> So, even if it is old it is perfectly valid compiler according to the
> GRUB docs.
>
> Hmmm... What are the latest gnulib minimal compiler, linker,
> etc. requirements?

It doesn't look formally specified anywhere, beyond what the autotools
requirements are.  I suspect that means in practice it's what the devs
are using.  Also, gnulib's position on sign comparison issues is to
ignore them, so the "fix" from our end would probably be to pragma them
away... but that assumes this is the only issue, which hasn't been
checked yet.

Be well,
--Robbie

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]

  reply	other threads:[~2022-02-22 17:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 21:41 [PATCH v5 0/4] Update gnulib and drop some patches Robbie Harwood
2022-02-16 21:41 ` [PATCH v5 1/4] Use visual indentation in config.h.in Robbie Harwood
2022-02-16 21:41 ` [PATCH v5 2/4] Drop gnulib fix-base64.patch Robbie Harwood
2022-02-16 21:41 ` [PATCH v5 3/4] Drop gnulib no-abort.patch Robbie Harwood
2022-02-16 21:41 ` [PATCH v5 4/4] Update gnulib version and drop most gnulib patches Robbie Harwood
2022-02-18 16:03 ` [PATCH v5 0/4] Update gnulib and drop some patches Glenn Washburn
2022-02-22 15:21 ` Daniel Kiper
2022-02-22 16:44   ` Robbie Harwood
2022-02-22 17:17     ` Daniel Kiper
2022-02-22 17:35       ` Robbie Harwood [this message]
2022-02-24 17:28         ` Daniel Kiper
2022-02-24 19:43           ` Robbie Harwood

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=jlg7d9m6bzv.fsf@redhat.com \
    --to=rharwood@redhat.com \
    --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.