All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14601] Python build fails on 2022.02-rc2
Date: Thu, 24 Feb 2022 06:35:11 +0000	[thread overview]
Message-ID: <bug-14601-163-l2xPHrZYzf@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14601-163@https.bugs.busybox.net/>

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

--- Comment #2 from HiFiBerry (Daniel) <info@hifiberry.com> ---
Might not have to do with the -O option (that was just a guess), but the
install path is clearly incorrect. 

My config here is quite complex and uses lots of additional stuff. However, it
was working fine up to 2021.11

Any recommendation how to go on debugging this?

-- 
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

  parent reply	other threads:[~2022-02-24  6:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23 14:23 [Buildroot] [Bug 14601] New: Python build fails on 2022.02-rc2 bugzilla
2022-02-23 19:23 ` [Buildroot] [Bug 14601] " bugzilla
2022-02-24  6:35 ` bugzilla [this message]
2022-02-24 21:20 ` bugzilla
2022-09-18 12:10 ` 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-14601-163-l2xPHrZYzf@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 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.