From: Peter Korsgaard <peter@korsgaard.com>
To: Arnout Vandecappelle via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [git commit] package/gnuradio: fix build with python-pybind > 2.10.0
Date: Mon, 17 Jul 2023 14:06:16 +0200 [thread overview]
Message-ID: <87mszuagjr.fsf@48ers.dk> (raw)
In-Reply-To: <20230704205218.46D2186623@busybox.osuosl.org> (Arnout Vandecappelle via buildroot's message of "Tue, 4 Jul 2023 22:44:08 +0200")
>>>>> "Arnout" == Arnout Vandecappelle via buildroot <buildroot@buildroot.org> writes:
> commit: https://git.buildroot.net/buildroot/commit/?id=11aa7ac8fa3a21dc2476dd09539ea3cf3e48f03d
> branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
> Since commit 0e82c360942907f5a2f379e64e0d211aaff80774 (and since release
> 2.10.1), a new variable called PYBIND11_PYTHONLIBS_OVERWRITE was introduced
> and set to ON by default.
> According to comment before this option:
> "Overwrite cached values read from Python library (classic search). Turn off if
> cross-compiling and manually setting these values."
> In buildroot's context this option must be disabled to keep variables
> provided by buildroot and lib/app.
> Fixes:
> - http://autobuild.buildroot.net/results/7423df5db5237d94bb49e32698828d4fe470e39b/
> Signed-off-by: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com>
> Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
Committed to 2023.02.x and 2023.05.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-07-17 12:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 20:44 [Buildroot] [git commit] package/gnuradio: fix build with python-pybind > 2.10.0 Arnout Vandecappelle via buildroot
2023-07-17 12:06 ` 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=87mszuagjr.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.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.