From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14556] python-crossbar fails to build
Date: Mon, 04 Apr 2022 01:06:52 +0000 [thread overview]
Message-ID: <bug-14556-163-465k6dvODX@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14556-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14556
--- Comment #4 from Emile Cormier <emile.cormier.jr@gmail.com> ---
Created attachment 9266
--> https://bugs.busybox.net/attachment.cgi?id=9266&action=edit
Simple tests
Python commands issued via the command line, as well as their outputs. Not
exhaustive, but at least demonstrates that the affected Python modules can
still be imported and used.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-04-04 1:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 23:22 [Buildroot] [Bug 14556] New: python-crossbar fails to build bugzilla
2022-02-07 22:16 ` [Buildroot] [Bug 14556] " bugzilla
2022-04-03 22:25 ` bugzilla
2022-04-03 22:38 ` bugzilla
2022-04-04 1:06 ` bugzilla [this message]
2022-08-08 20:28 ` bugzilla
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=bug-14556-163-465k6dvODX@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox