From: Jan Kiszka <jan.kiszka@web.de>
To: Alexander Smirnov <asmirnov@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH v2 00/12] Cross-compilation
Date: Wed, 4 Jul 2018 22:03:46 +0200 [thread overview]
Message-ID: <0c20e3f3-1d99-c821-be29-fa8994945f1e@web.de> (raw)
In-Reply-To: <d135d1c2-0111-bf7b-cdd1-e4f172eccfc9@ilbers.de>
[-- Attachment #1.1: Type: text/plain, Size: 1274 bytes --]
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2018-07-04 20:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 8:27 Alexander Smirnov
2018-06-28 8:27 ` [PATCH v2 01/12] isar-bootstrap: Add routine to determine host arch Alexander Smirnov
2018-06-28 8:28 ` [PATCH v2 02/12] isar-bootstrap: Move common part to include Alexander Smirnov
2018-06-28 8:28 ` [PATCH v2 03/12] isar-bootstrap: Add host architecture support Alexander Smirnov
2018-06-28 8:28 ` [PATCH v2 04/12] isar-bootstrap-helper: Add parameter to set arch Alexander Smirnov
2018-06-28 8:28 ` [PATCH v2 05/12] buildchroot-cross: Initial implementation Alexander Smirnov
2018-06-29 17:36 ` Jan Kiszka
2018-07-04 19:56 ` Alexander Smirnov
2018-07-04 20:05 ` Jan Kiszka
2018-06-28 8:28 ` [PATCH v2 06/12] classes/dpkg*: Relocate dependency from buildchroot Alexander Smirnov
2018-06-28 8:28 ` [PATCH v2 07/12] classes/dpkg*: Drop hardcoded buildchroot blobs Alexander Smirnov
2018-06-28 8:28 ` [PATCH v2 08/12] build.sh: Add target parameter Alexander Smirnov
2018-06-28 8:28 ` [PATCH v2 09/12] classes/dpkg-cross: Initial implementation Alexander Smirnov
2018-06-28 8:28 ` [PATCH v2 10/12] dpkg: Resolve dep from buildchroot Alexander Smirnov
2018-06-28 8:28 ` [PATCH v2 11/12] linux: Add cross-compilation support Alexander Smirnov
2018-06-28 8:28 ` [PATCH v2 12/12] local.conf: Add cross-compilation option Alexander Smirnov
2018-06-29 13:31 ` [PATCH v2 00/12] Cross-compilation Henning Schild
2018-06-29 18:28 ` Jan Kiszka
2018-06-30 9:05 ` Jan Kiszka
2018-07-04 19:40 ` Alexander Smirnov
2018-07-04 20:03 ` Jan Kiszka [this message]
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=0c20e3f3-1d99-c821-be29-fa8994945f1e@web.de \
--to=jan.kiszka@web.de \
--cc=asmirnov@ilbers.de \
--cc=isar-users@googlegroups.com \
/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