From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Martin Böh via buildroot" <buildroot@buildroot.org>
Cc: "Gwenhael Goavec-Merou" <gwenhael.goavec-merou@trabucayre.com>,
"Martin Böh" <contact@martb.dev>
Subject: Re: [Buildroot] [PATCH 1/1] package/gr-osmosdr: add missing host-python-six dependency to python support
Date: Thu, 23 Feb 2023 23:13:41 +0100 [thread overview]
Message-ID: <20230223231341.4dcc6d21@windsurf> (raw)
In-Reply-To: <20230223201733.222573-1-contact@martb.dev>
Hello Martin,
On Thu, 23 Feb 2023 21:17:33 +0100
Martin Böh via buildroot <buildroot@buildroot.org> wrote:
> Osmosdr failed to build docs when python support is enabled.
> [ 41%] Copying osmosdr docstring templates as pybind headers ...
> Traceback (most recent call last):
> File "/home/martb/Schreibtisch/DiscoSAT/satos/output/build/gr-osmosdr-0.2.4/docs/doxygen/update_pydoc.py", line 22, in <module>
> from doxyxml import DoxyIndex, DoxyClass, DoxyFriend, DoxyFunction, DoxyFile
> File "/home/martb/Schreibtisch/DiscoSAT/satos/output/build/gr-osmosdr-0.2.4/docs/doxygen/doxyxml/__init__.py", line 69, in <module>
> from .doxyindex import DoxyIndex, DoxyFunction, DoxyParam, DoxyClass, DoxyFile, DoxyNamespace, DoxyGroup, DoxyFriend, DoxyOther
> File "/home/martb/Schreibtisch/DiscoSAT/satos/output/build/gr-osmosdr-0.2.4/docs/doxygen/doxyxml/doxyindex.py", line 31, in <module>
> from .generated import index
> File "/home/martb/Schreibtisch/DiscoSAT/satos/output/build/gr-osmosdr-0.2.4/docs/doxygen/doxyxml/generated/index.py", line 13, in <module>
> from . import compound
> File "/home/martb/Schreibtisch/DiscoSAT/satos/output/build/gr-osmosdr-0.2.4/docs/doxygen/doxyxml/generated/compound.py", line 15, in <module>
> from . import compoundsuper as supermod
> File "/home/martb/Schreibtisch/DiscoSAT/satos/output/build/gr-osmosdr-0.2.4/docs/doxygen/doxyxml/generated/compoundsuper.py", line 15, in <module>
> import six
> ModuleNotFoundError: No module named 'six'
> make[2]: *** [python/bindings/CMakeFiles/osmosdr_docstrings.dir/build.make:73: python/bindings/docstring_status] Fehler 1
> make[1]: *** [CMakeFiles/Makefile2:332: python/bindings/CMakeFiles/osmosdr_docstrings.dir/all] Fehler 2
>
> Signed-off-by: Martin Böh <contact@martb.dev>
Is there potentially a way to disable building documentation instead?
Of course, adding host-python-six in the dependencies is not a huge
deal, but we really don't care about building documentation in the
context of Buildroot.
Best regards,
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-02-23 22:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 20:17 [Buildroot] [PATCH 1/1] package/gr-osmosdr: add missing host-python-six dependency to python support Martin Böh via buildroot
2023-02-23 22:13 ` Thomas Petazzoni via buildroot [this message]
2024-05-12 7:56 ` Thomas Petazzoni via buildroot
2024-06-08 10:56 ` Peter Korsgaard
[not found] <e1ff72dc-06fc-db71-dd1d-64d5d2cf96b3@familie-boeh.de>
2023-02-24 1:04 ` Martin Böh 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=20230223231341.4dcc6d21@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox