From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: "Stefan Sørensen" <stefan.sorensen@spectralink.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/cracklib: python needs autoreconf
Date: Sun, 11 Feb 2024 22:33:45 +0100 [thread overview]
Message-ID: <20240211223345.2298964c@windsurf> (raw)
In-Reply-To: <20240211170707.524645-1-fontaine.fabrice@gmail.com>
On Sun, 11 Feb 2024 18:07:07 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Set CRACKLIB_AUTORECONF when building python to regenerate
> python/test/Makefile and avoid the following build failure with python
> 3.12 (which removed imp mpodule) raised since commit
> 36e635d2d5c0166476858aa239ccbe78e8f2af14:
>
> Traceback (most recent call last):
> File "<string>", line 2, in <module>
> ModuleNotFoundError: No module named 'imp'
> make[3]: *** [Makefile:485: install-pythonPYTHON] Error 1
>
> Fixes:
> - http://autobuild.buildroot.org/results/aec4c19fdf8087c76c1d5f472e855e0f84fcf7fd
Thanks for the fix. Could you describe a bit how an autoreconf helps in
resolving this? Is it because the new Python comes with a newer set of
.m4 macros?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-02-11 21:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 17:07 [Buildroot] [PATCH 1/1] package/cracklib: python needs autoreconf Fabrice Fontaine
2024-02-11 21:33 ` 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=20240211223345.2298964c@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=stefan.sorensen@spectralink.com \
--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.