Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Volkov Viacheslav <sv99@inbox.ru>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/zbar: fix python 3.11 compatibility
Date: Tue, 25 Oct 2022 23:00:24 +0200	[thread overview]
Message-ID: <20221025230024.3ab84f31@windsurf> (raw)
In-Reply-To: <20221025180603.886122-1-james.hilliard1@gmail.com>

On Tue, 25 Oct 2022 12:06:03 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:

> Add a patch from upstream pull request to fix build with python 3.11.
> 
> Fixes:
> python/enum.c: In function ‘enumitem_new’:
> python/enum.c:55:25: error: lvalue required as left operand of assignment
>    55 |     Py_SIZE(&self->val) = Py_SIZE(longval);
>       |                         ^
> python/enum.c: In function ‘zbarEnumItem_New’:
> python/enum.c:146:25: error: lvalue required as left operand of assignment
>   146 |     Py_SIZE(&self->val) = Py_SIZE(longval);
>       |                         ^
> 
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
>  ...ython-enum-fix-build-for-Python-3.11.patch | 62 +++++++++++++++++++
>  1 file changed, 62 insertions(+)
>  create mode 100644 package/zbar/0001-python-enum-fix-build-for-Python-3.11.patch

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-10-25 21:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25 18:06 [Buildroot] [PATCH 1/1] package/zbar: fix python 3.11 compatibility James Hilliard
2022-10-25 21:00 ` Thomas Petazzoni via buildroot [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=20221025230024.3ab84f31@windsurf \
    --to=buildroot@buildroot.org \
    --cc=james.hilliard1@gmail.com \
    --cc=sv99@inbox.ru \
    --cc=thomas.petazzoni@bootlin.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