Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Oleg Lyovin via buildroot <buildroot@buildroot.org>
Cc: olegartys@gmail.com, James Hilliard <james.hilliard1@gmail.com>,
	Oleg Lyovin <ovlevin@salutedevices.com>,
	Asaf Kahlon <asafka7@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/python-pycryptodomex: fix package build with gcc 4.8
Date: Mon, 30 Oct 2023 23:00:51 +0100	[thread overview]
Message-ID: <874ji73h4c.fsf@48ers.dk> (raw)
In-Reply-To: <20231027155221.977752-1-ovlevin@salutedevices.com> (Oleg Lyovin via buildroot's message of "Fri, 27 Oct 2023 18:52:21 +0300")

>>>>> "Oleg" == Oleg Lyovin via buildroot <buildroot@buildroot.org> writes:

 > python-pycryptodomex uses C99 features like variable
 > declaration in for-loop statement, while old compilers
 > assumes C89 by default.

 > This patch explicitly specifies C99 standard.

 > Change-Id: I934211714307cea43541167fbc72ff30fb66ad5f
 > Signed-off-by: Oleg Lyovin <ovlevin@salutedevices.com>

Committed to 2023.08.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2023-10-30 22:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231027155221.977752-1-ovlevin@salutedevices.com>
2023-10-28 22:35 ` [Buildroot] [PATCH 1/1] package/python-pycryptodomex: fix package build with gcc 4.8 Yann E. MORIN
2023-10-29 12:18   ` Oleg Lyovin via buildroot
2023-10-30 22:00 ` Peter Korsgaard [this message]

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=874ji73h4c.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=asafka7@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=james.hilliard1@gmail.com \
    --cc=olegartys@gmail.com \
    --cc=ovlevin@salutedevices.com \
    /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