Bug 12941

Summary: Python GObject fails to build when using BR2_PER_PACKAGE_DIRECTORIES
Product: buildroot Reporter: HiFiBerry (Daniel) <info>
Component: OtherAssignee: Adam Duskett <aduskett>
Status: RESOLVED FIXED    
Severity: normal CC: buildroot, yann.morin.1998
Priority: P5    
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Host: Target:
Build:

Description HiFiBerry (Daniel) 2020-05-24 04:29:25 UTC 
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
Comment 1 Asaf Kahlon 2020-05-28 13:15:13 UTC 
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.
Comment 2 Adam Duskett 2020-06-08 17:58:35 UTC 
(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@gmail.com/
Comment 3 HiFiBerry (Daniel) 2020-06-09 13:24:48 UTC 
It seems to work, but I ran into another issue with another package.
Therefore, I'm not 100% sure yet.
Comment 4 Yann E. MORIN 2020-06-15 21:23:59 UTC 
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.