Re: [PATCH v4 09/10] build.sh: Do not check deps in dpkg-buildpackage

[Jan Kiszka <jan.kiszka@siemens.com>]

On 2018-08-11 17:47, [ext] Jan Kiszka wrote:
> On 2018-07-24 21:06, Alexander Smirnov wrote:
>> dpkg-buildpackage could brake the compilation. The build dependencies
>> are already installed at this stage, so there is no need to check them
>> in dpkg-buildpackage.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> Signed-off-by: Alexander Smirnov <asmirnov@ilbers.de>
>> ---
>>   meta/recipes-devtools/buildchroot/files/build.sh | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta/recipes-devtools/buildchroot/files/build.sh 
>> b/meta/recipes-devtools/buildchroot/files/build.sh
>> index 40ba410..aba2042 100644
>> --- a/meta/recipes-devtools/buildchroot/files/build.sh
>> +++ b/meta/recipes-devtools/buildchroot/files/build.sh
>> @@ -61,4 +61,4 @@ for i in configure aclocal.m4 Makefile.am 
>> Makefile.in; do
>>   done
>>   # Build the package
>> -dpkg-buildpackage -a$target_arch
>> +dpkg-buildpackage -a$target_arch --no-check-builddeps
>>
> 
> Any reason why this was not part of v5 and is now not in next? It's 
> still required to cross-compile packages with certain python 
> dependencies, possibly more.
> 

Can we get this into next as well (then I would be patch-free in my 
layer)? Alex asked for an ack on this which I herewith provide.

We can possibly tune the commit message further: This changes is needed 
in order to avoid failures of dpkg-buildpackage when a package provides 
python-pip:native or python-mako:native as build-depends. ":native" 
would make the builddeps check fail while that is needed to install (via 
  mk-build-deps) the host-side version of these packages in a 
cross-build case.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux