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 12941] Python GObject fails to build when using BR2_PER_PACKAGE_DIRECTORIES
Date: Thu, 28 May 2020 13:15:13 +0000	[thread overview]
Message-ID: <bug-12941-163-iEAtRfw27v@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12941-163@https.bugs.busybox.net/>

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

--- Comment #1 from Asaf Kahlon <asafka7@gmail.com> ---
This failure happens because the evaluation of PKG_PYTHON_SYSCONFIGDATA_NAME at
python-gobject.mk is done on the configure step, but because we haven't rsynced
the dependencies yet there's nothing on the per-package directory.
You can also see that if you do "make python-gobject" twice: on the first time
it will fail, but on the second time everything will be fine because all the
dependencies have been rsynced to the per-package dir.

I'm not sure how to solve this problem, but at least we know why it happens.

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

  parent reply	other threads:[~2020-05-28 13:15 UTC|newest]

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