From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: [PATCH 1/8] Forward proxy settings to dpkg build
Date: Thu, 8 Feb 2018 16:05:34 +0100 [thread overview]
Message-ID: <5678c68ac55a37ddd521421d1ffb95676fa37f63.1518102341.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1518102341.git.jan.kiszka@siemens.com>
In-Reply-To: <cover.1518102341.git.jan.kiszka@siemens.com>
From: Jan Kiszka <jan.kiszka@siemens.com>
Required when the package needs to install build dependencies.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
meta/classes/dpkg.bbclass | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/classes/dpkg.bbclass b/meta/classes/dpkg.bbclass
index c10f5ba..9cd4403 100644
--- a/meta/classes/dpkg.bbclass
+++ b/meta/classes/dpkg.bbclass
@@ -5,5 +5,6 @@ inherit dpkg-base
# Build package from sources using build script
dpkg_runbuild() {
- sudo chroot ${BUILDCHROOT_DIR} /build.sh ${PP}/${SRC_DIR}
+ E="${@ bb.utils.export_proxies(d)}"
+ sudo -E chroot ${BUILDCHROOT_DIR} /build.sh ${PP}/${SRC_DIR}
}
--
2.13.6
next prev parent reply other threads:[~2018-02-08 15:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 15:05 [PATCH 0/8] Provide infrastructure and examples for custom kernels and modules Jan Kiszka
2018-02-08 15:05 ` Jan Kiszka [this message]
2018-02-08 15:05 ` [PATCH 2/8] Prioritize isar-apt repo over all others Jan Kiszka
2018-02-08 15:05 ` [PATCH 3/8] Replace SRC_DIR with S Jan Kiszka
2018-02-08 15:05 ` [PATCH 4/8] Install kernel via replaceable recipe Jan Kiszka
2018-02-08 15:05 ` [PATCH 5/8] Provide include file for easy custom kernel builds Jan Kiszka
2018-02-08 15:05 ` [PATCH 6/8] Add custom kernel examples Jan Kiszka
2018-02-08 15:05 ` [PATCH 7/8] Provide include file for easy custom module builds Jan Kiszka
2018-02-08 15:05 ` [PATCH 8/8] Add exemplary kernel module 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=5678c68ac55a37ddd521421d1ffb95676fa37f63.1518102341.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--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