From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH 1/1] buildhcroot/build.sh: Disable deps checking
Date: Wed, 15 Aug 2018 09:58:15 +0200 [thread overview]
Message-ID: <de518421-1b7f-da09-a61b-aafc6a0bc9f3@siemens.com> (raw)
In-Reply-To: <20180815074553.27353-2-asmirnov@ilbers.de>
On 2018-08-15 09:45, Alexander Smirnov wrote:
> This change 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.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
As this is now "your" patch (according to the authorship), my signed-off
would come at most after yours. But you probably better add my acked-by
here.
Thanks,
Jan
> 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 c2967d2..e2dabab 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 -d
>
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2018-08-15 7:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 7:45 [PATCH 0/1] Drop " Alexander Smirnov
2018-08-15 7:45 ` [PATCH 1/1] buildhcroot/build.sh: Disable " Alexander Smirnov
2018-08-15 7:58 ` Jan Kiszka [this message]
2018-08-15 7:55 ` [PATCH 0/1] Drop " Jan Kiszka
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=de518421-1b7f-da09-a61b-aafc6a0bc9f3@siemens.com \
--to=jan.kiszka@siemens.com \
--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