All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Andreas Naumann <anaumann@ultratronik.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/evemu: needs autoreconf for python 3.12 compatibility
Date: Tue, 16 Jul 2024 23:26:20 +0200	[thread overview]
Message-ID: <20240716232620.6bf94528@windsurf> (raw)
In-Reply-To: <20240716183259.113591-1-anaumann@ultratronik.de>

On Tue, 16 Jul 2024 20:32:59 +0200
Andreas Naumann <anaumann@ultratronik.de> wrote:

> evemu ships with an ancient py-compile script (from 2011) depending
> the imp module, which was finally removed in Python 3.12.
> Set autoreconf in order to get an up to date version of py-compile
> which automatically handles the different python versions.
> 
> This is a similar problem as in
> 42eae73ef1 package/cracklib: python needs autoreconf
> 
> Fixes:
> 
>  http://autobuild.buildroot.org/results/a52/a520583be6e86993d268d6535f727a352bd92028/
> 
> and many other configs where Python3 is selected and thus evemu
> is configured to build the python-bindings.
> 
> Signed-off-by: Andreas Naumann <anaumann@ultratronik.de>
> ---
>  package/evemu/evemu.mk | 1 +
>  1 file changed, 1 insertion(+)

Applied to master after adding missing spaces around "=" sign. Thanks a
lot!

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:[~2024-07-16 21:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-16 18:32 [Buildroot] [PATCH 1/1] package/evemu: needs autoreconf for python 3.12 compatibility Andreas Naumann
2024-07-16 21:26 ` 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=20240716232620.6bf94528@windsurf \
    --to=buildroot@buildroot.org \
    --cc=anaumann@ultratronik.de \
    --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 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.