All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12941] New: Python GObject fails to build when using BR2_PER_PACKAGE_DIRECTORIES
Date: Sun, 24 May 2020 04:29:25 +0000	[thread overview]
Message-ID: <bug-12941-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 12941
           Summary: Python GObject fails to build when using
                    BR2_PER_PACKAGE_DIRECTORIES
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: info at hifiberry.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

When using the new BR2_PER_PACKAGE_DIRECTORIES setting, Python GObject fails to
build.

Tested with 202005-rc2

../buildroot-4/build/python-gobject-3.36.0/meson.build:16:0: ERROR:
<ExternalProgram 'python3' ->
['/home/matuschd/buildroot-4/per-package/python-gobject/host/bin/python3']> is
not a valid python or it is missing setuptools

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

             reply	other threads:[~2020-05-24  4:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-24  4:29 bugzilla at busybox.net [this message]
2020-05-25  7:14 ` [Buildroot] [Bug 12941] Python GObject fails to build when using BR2_PER_PACKAGE_DIRECTORIES bugzilla at busybox.net
2020-05-28 13:15 ` bugzilla at busybox.net
2020-06-08 17:58 ` bugzilla at busybox.net
2020-06-09 13:24 ` bugzilla at busybox.net
2020-06-15 21:23 ` 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-12941-163@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 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.