On 2018-07-04 21:40, Alexander Smirnov wrote:
> On 06/29/2018 09:28 PM, Jan Kiszka wrote:
>> -Build-Depends: build-essential, wget, cpio, unzip, rsync, python, bc
>> +Build-Depends: build-essential:amd64, wget, cpio, unzip, rsync,
>> python:amd64, bc
> 
> Could please clarify why you added build-essential package to deps? This
> could be problem for cross-compilation, because we always need
> build-essential of *host* architecture, but for example for ARM the
> package with different name should be installed:
> 'crossbuild-essential-armhf', i.e. build-essential:armhf is invalid (it
> will pull lots of other host utils with armhf arch, what will totally
> break cross-buildchroot :-(.
> 
> To be honest, I can't remember if I have ever seen build-essentials in
> debian/control. I've quickly checked Debian policy:
> 
> https://www.debian.org/doc/debian-policy/#relationships-between-source-and-binary-packages-build-depends-build-depends-indep-build-depends-arch-build-conflicts-build-conflicts-indep-build-conflicts-arch
> 
> 
> so build-essential is optional, so I'd suggest to drop it.

I can try, no problem.

Maybe - hopefully - it will resolve the problem for the python
dependency as well because that one can't be removed.

Jan