[Buildroot] [Bug 12941] New: Python GObject fails to build when using BR2_PER_PACKAGE_DIRECTORIES

[Buildroot] [Bug 12941] New: Python GObject fails to build when using BR2_PER_PACKAGE_DIRECTORIES

[bugzilla at busybox.net]

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.

[Buildroot] [Bug 12941] Python GObject fails to build when using BR2_PER_PACKAGE_DIRECTORIES

[bugzilla at busybox.net]

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

Thomas Petazzoni <thomas.petazzoni@bootlin.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|unassigned at buildroot.uclibc |aduskett at gmail.com
                   |.org                        |

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

[Buildroot] [Bug 12941] Python GObject fails to build when using BR2_PER_PACKAGE_DIRECTORIES

[bugzilla at 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.

[Buildroot] [Bug 12941] Python GObject fails to build when using BR2_PER_PACKAGE_DIRECTORIES

[bugzilla at busybox.net]

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

--- Comment #2 from Adam Duskett <aduskett@gmail.com> ---
(In reply to info from comment #0)
Hello;

In collaboration with Yann, we were able to create a patch that will fix this
issue.

If you could test it out for us that would be great!
Even better, if the patch works for you, please respond with a "tested-by" to
the patch series.

Thanks again!

Adam


https://patchwork.ozlabs.org/project/buildroot/patch/20200605205920.465052-1-aduskett at gmail.com/

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

[Buildroot] [Bug 12941] Python GObject fails to build when using BR2_PER_PACKAGE_DIRECTORIES

[bugzilla at busybox.net]

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

--- Comment #3 from info at hifiberry.com ---
It seems to work, but I ran into another issue with another package.
Therefore, I'm not 100% sure yet.

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

[Buildroot] [Bug 12941] Python GObject fails to build when using BR2_PER_PACKAGE_DIRECTORIES

[bugzilla at busybox.net]

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

Yann E. MORIN <yann.morin.1998@free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |yann.morin.1998 at free.fr
         Resolution|---                         |FIXED

--- Comment #4 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Daniel, All,

Thanks for the report. This is now supposedly fixed with the patch from
Adam, that was applied as commit 2158c87206.

Regards,
Yann E. MORIN.

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