public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>,
	isar-users@googlegroups.com, Maksim Osipov <mosipov@ilbers.de>
Subject: Re: [PATCH v4 09/10] build.sh: Do not check deps in dpkg-buildpackage
Date: Sat, 11 Aug 2018 17:47:37 +0200	[thread overview]
Message-ID: <99cb3b45-b09a-13f3-31da-782867ac419d@siemens.com> (raw)
In-Reply-To: <20180724190618.19155-10-asmirnov@ilbers.de>

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.

Jan

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

  parent reply	other threads:[~2018-08-11 15:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-24 19:06 [PATCH v4 00/10] Add cross-compilation support Alexander Smirnov
2018-07-24 19:06 ` [PATCH v4 01/10] buildchroot: Add host buildchroot Alexander Smirnov
2018-07-24 19:06 ` [PATCH v4 02/10] isar-bootstrap-helper: Add target architecture for dpkg Alexander Smirnov
2018-07-24 19:06 ` [PATCH v4 03/10] build.sh: Add additional parameter Alexander Smirnov
2018-07-25  8:10   ` Henning Schild
2018-07-25  8:14   ` Henning Schild
2018-07-24 19:06 ` [PATCH v4 04/10] cross-compilation: Introduce variable switch Alexander Smirnov
2018-07-25  6:56   ` Jan Kiszka
2018-07-25  8:25   ` Henning Schild
2018-07-25 12:22     ` Jan Kiszka
2018-07-24 19:06 ` [PATCH v4 05/10] linux: Add ARM cross-compilation support Alexander Smirnov
2018-07-24 19:06 ` [PATCH v4 06/10] isar: Add ARM64 " Alexander Smirnov
2018-07-24 19:06 ` [PATCH v4 07/10] linux-module: Export ARCH and CROSS_COMPILE Alexander Smirnov
2018-07-24 19:06 ` [PATCH v4 08/10] linux: Drop gcc from dependencies Alexander Smirnov
2018-07-24 19:06 ` [PATCH v4 09/10] build.sh: Do not check deps in dpkg-buildpackage Alexander Smirnov
2018-07-24 19:07   ` Alexander Smirnov
2018-08-11 15:47   ` Jan Kiszka [this message]
2018-08-14 11:40     ` Jan Kiszka
2018-08-14 12:39       ` Alexander Smirnov
2018-07-24 19:06 ` [PATCH v4 10/10] linux-module: Enable cross-build for testing Alexander Smirnov
2018-07-24 19:07   ` Alexander Smirnov

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=99cb3b45-b09a-13f3-31da-782867ac419d@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=asmirnov@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=mosipov@ilbers.de \
    /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