All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: friedtj@free.fr
Cc: gwenhael.goavec-merou@trabucayre.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/gr-osmosdr: add host-python-six dependency needed for generating Python bindings
Date: Sun, 12 May 2024 09:57:21 +0200	[thread overview]
Message-ID: <20240512095721.7695acbd@windsurf> (raw)
In-Reply-To: <299860002.1258357262.1712837263439.JavaMail.zimbra@free.fr>

Hello Jean-Michel,

On Thu, 11 Apr 2024 14:07:43 +0200 (CEST)
friedtj@free.fr wrote:

> Compiling gr-osmosdr when Python3 support is active fails with
> 
> ModuleNotFoundError: No module named 'six' 
> make[3]: *** [python/bindings/CMakeFiles/osmosdr_docstrings.dir/build.make:73: python/bindings/docstring_status] Error 1
> 
> when generating the Python bindings. The following patch solves the problem.
> 
> 
> Signed-off-by: Jean-Michel Friedt <jmfriedt@femto-st.fr>
> ---
>  package/gr-osmosdr/gr-osmosdr.mk | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Thanks for the patch. However, I have applied a similar patch which was
submitted earlier by Martin Böh:

  https://gitlab.com/buildroot.org/buildroot/-/commit/cfda1f0b87ebfb7686b82f319c531d4d28fdfd67

Best regards,

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-05-12  7:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11 12:07 [Buildroot] [PATCH 1/1] package/gr-osmosdr: add host-python-six dependency needed for generating Python bindings friedtj
2024-05-12  7:57 ` 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=20240512095721.7695acbd@windsurf \
    --to=buildroot@buildroot.org \
    --cc=friedtj@free.fr \
    --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.