Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gwenhael Goavec-Merou <gwenj@trabucayre.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com>,
	Arnout Vandecappelle via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v2 2/2] package/gnuradio: fix gnuradio python libraries for cross-compile
Date: Mon, 17 Jul 2023 17:17:42 +0200	[thread overview]
Message-ID: <20230717171742.457b0500@x230> (raw)
In-Reply-To: <20230710202503.0219463b@windsurf>

Thomas, Arnout, all
Sorry for delay, was away for a correct/stable connection.

On Mon, 10 Jul 2023 20:25:03 +0200
Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:

> Hello Gwenhael,
> 
> On Fri, 7 Jul 2023 11:44:21 +0200
> Arnout Vandecappelle via buildroot <buildroot@buildroot.org> wrote:
> 
> > > In fact I see I have missed to explain in my message this issue is
> > > related to pybind.
> > > If PYTHON_MODULE_EXTENSION is unset, .cmake uses a python script
> > > containing sysconfig.get_config_var('EXT_SUFFIX')
> > > This one return .cpython-311-x86_64-linux-gnu.so, because host-python is
> > > used.    
> > 
> >   Ah, in that case the environment variable you need is 
> > _PYTHON_SYSCONFIGDATA_NAME="$(PKG_PYTHON_SYSCONFIGDATA_NAME)"
> > This will make sure the sysconfig that gets used is the one for the target 
> > instead of for the host.
> > 
> >   It's quite likely that you need all of PKG_PYTHON_ENV to be present in
> > the environment.  
> 
> Have you had the chance to test this suggestion from Arnout?
> 
Adding:
GNURADIO_CONF_ENV += _PYTHON_SYSCONFIGDATA_NAME="$(PKG_PYTHON_SYSCONFIGDATA_NAME)" \
    PYTHONPATH=$(PYTHON3_PATH)
Do the job.
Thanks. I have to redo my patch
> Thomas

Gwen
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-07-17 15:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26  7:05 [Buildroot] [PATCH v2 1/2] package/gnuradio: fix build with python-pybind > 2.10.0 Gwenhael Goavec-Merou
2023-06-26  7:05 ` [Buildroot] [PATCH v2 2/2] package/gnuradio: fix gnuradio python libraries for cross-compile Gwenhael Goavec-Merou
2023-07-04 20:51   ` Arnout Vandecappelle via buildroot
2023-07-07  8:58     ` Gwenhael Goavec-Merou
2023-07-07  9:44       ` Arnout Vandecappelle via buildroot
2023-07-10 18:25         ` Thomas Petazzoni via buildroot
2023-07-17 15:17           ` Gwenhael Goavec-Merou [this message]
2023-07-04 20:47 ` [Buildroot] [PATCH v2 1/2] package/gnuradio: fix build with python-pybind > 2.10.0 Arnout Vandecappelle via buildroot
2023-07-07  8:40   ` Gwenhael Goavec-Merou

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=20230717171742.457b0500@x230 \
    --to=gwenj@trabucayre.com \
    --cc=buildroot@buildroot.org \
    --cc=gwenhael.goavec-merou@trabucayre.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox