Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11706] binman (U-boot tool) cannot find libfdt "binman: No module named _libfdt" if python3 selected
Date: Tue, 13 Aug 2019 01:17:32 +0000	[thread overview]
Message-ID: <bug-11706-163-VaBsvasSTr@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11706-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=11706

Carlos Santos <unixmania@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|unassigned at buildroot.uclibc |unixmania at gmail.com
                   |.org                        |
             Status|NEW                         |ASSIGNED

--- Comment #1 from Carlos Santos <unixmania@gmail.com> ---
Sorry for the late answer. I'm taking this bug.

Is this report still valid? If yes, please attach a copy your defconfig. You
can create it with:

   $ make sevedefconfig BR2_DEFCONFIG=/tmp/defconfig

Then attach the generated /tmp/defconfig to this case.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2019-08-13  1:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-27  8:07 [Buildroot] [Bug 11706] New: binman (U-boot tool) cannot find libfdt "binman: No module named _libfdt" if python3 selected bugzilla at busybox.net
2019-08-13  1:17 ` bugzilla at busybox.net [this message]
2019-08-15 14:03 ` [Buildroot] [Bug 11706] " bugzilla at busybox.net
2020-03-03 21:22 ` bugzilla at busybox.net
2020-05-29 21:04 ` bugzilla at busybox.net
2021-02-16 21:48 ` bugzilla at busybox.net

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-11706-163-VaBsvasSTr@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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