From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: "Martin Böh" <contact@martb.dev>,
"Gwenhael Goavec-Merou" <gwenhael.goavec-merou@trabucayre.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH 2/2] package/gnuradio: remove pybind target suffix when crosscompiling
Date: Tue, 1 Aug 2023 00:21:43 +0200 [thread overview]
Message-ID: <20230801002143.58744c00@windsurf> (raw)
In-Reply-To: <20230223231258.0e07045c@windsurf>
Hello Martin,
On Thu, 23 Feb 2023 23:12:58 +0100
Thomas Petazzoni via buildroot <buildroot@buildroot.org> wrote:
> > +This is required as pybind11 uses host python3 and therefore the host platform suffixes.
>
> We need your Signed-off-by here, and also the upstream status of this
> patch.
Unless I missed it, I don't think you followed-up on this. In the mean
time, this issue has been fixed (I believe) in a different way in
commit
https://gitlab.com/buildroot.org/buildroot/-/commit/e22b450692a6d02da43a453f24ec057bb5517422.
Could you verify that the latest Buildroot master works for you?
Thanks for your contribution!
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
next prev parent reply other threads:[~2023-07-31 22:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 20:15 [Buildroot] [PATCH 1/2] package/gnuradio: bump to 3.10.5.1 Martin Böh via buildroot
2023-02-23 20:15 ` [Buildroot] [PATCH 2/2] package/gnuradio: remove pybind target suffix when crosscompiling Martin Böh via buildroot
2023-02-23 22:12 ` Thomas Petazzoni via buildroot
2023-07-31 22:21 ` Thomas Petazzoni via buildroot [this message]
2023-07-31 22:20 ` [Buildroot] [PATCH 1/2] package/gnuradio: bump to 3.10.5.1 Thomas Petazzoni via buildroot
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=20230801002143.58744c00@windsurf \
--to=buildroot@buildroot.org \
--cc=contact@martb.dev \
--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 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.