From: "Andreas J. Reichel" <andreas.reichel.ext@siemens.com>
To: isar-users@googlegroups.com
Cc: Andreas Reichel <andreas.reichel.ext@siemens.com>
Subject: [PATCH 1/1] Add proxy support to isar-image-*.bb and buildchroot.bb
Date: Thu, 7 Sep 2017 17:03:35 +0200 [thread overview]
Message-ID: <20170907150335.30970-2-andreas.reichel.ext@siemens.com> (raw)
In-Reply-To: <20170907150335.30970-1-andreas.reichel.ext@siemens.com>
From: Andreas Reichel <andreas.reichel.ext@siemens.com>
* BB_ENV_EXTRAWHITE provides a list for variables that are kept in the
environment by bitbake. However, isar init script clears any additional
settings. Thus, add proxy variables to BB_ENV_EXTRAWHITE in
isar-buildenv-internal.
* Bitbake clears environment variables for each task within a recipe.
However, bb.utils.export_proxies function can be used with an
inline-python call to reexport the proxy settings.
* Sudo loses environment variables again, thus call multistrap with sudo
with the -E option to preserve (the already cleaned) environment for the
task's multistrap command.
Note:
Downloads are normally done by the fetcher task, which calls a python
function that in turn uses bb.util.export_proxies. However we have a
non-fetcher task, which needs download capabilities as well.
Signed-off-by: Andreas Reichel <andreas.reichel.ext@siemens.com>
---
meta-isar/recipes-core/images/isar-image-base.bb | 8 +++++++-
meta/recipes-devtools/buildchroot/buildchroot.bb | 9 +++++++--
scripts/isar-buildenv-internal | 2 +-
3 files changed, 15 insertions(+), 4 deletions(-)
diff --git a/meta-isar/recipes-core/images/isar-image-base.bb b/meta-isar/recipes-core/images/isar-image-base.bb
index b679d97..a826b88 100644
--- a/meta-isar/recipes-core/images/isar-image-base.bb
+++ b/meta-isar/recipes-core/images/isar-image-base.bb
@@ -24,6 +24,11 @@ IMAGE_ROOTFS = "${S}"
do_rootfs[stamp-extra-info] = "${MACHINE}-${DISTRO}"
do_rootfs() {
+ # Bitbake clears environment for all task functions, but we need the proxy
+ # settings in this task so do an inline python call which exports them
+ # again to the environment
+ E="${@ bb.utils.export_proxies(d)}"
+
install -d -m 755 ${WORKDIR}/hooks_multistrap
# Copy config file
@@ -46,7 +51,8 @@ do_rootfs() {
cd ${TOPDIR}
# Create root filesystem
- sudo multistrap -a ${DISTRO_ARCH} -d "${S}" -f "${WORKDIR}/multistrap.conf" || true
+ # We must use sudo -E here to preserve the environment because of proxy settings
+ sudo -E multistrap -a ${DISTRO_ARCH} -d "${S}" -f "${WORKDIR}/multistrap.conf" || true
# Configure root filesystem
sudo chroot ${S} /configscript.sh ${MACHINE_SERIAL} ${BAUDRATE_TTY} \
diff --git a/meta/recipes-devtools/buildchroot/buildchroot.bb b/meta/recipes-devtools/buildchroot/buildchroot.bb
index ccba683..7627015 100644
--- a/meta/recipes-devtools/buildchroot/buildchroot.bb
+++ b/meta/recipes-devtools/buildchroot/buildchroot.bb
@@ -26,6 +26,11 @@ WORKDIR = "${TMPDIR}/work/${PF}/${DISTRO}"
do_build[stamp-extra-info] = "${DISTRO}-${DISTRO_ARCH}"
do_build() {
+ # Bitbake clears environment for all task functions, but we need the proxy
+ # settings in this task so do an inline python call which exports them
+ # again to the environment
+ E="${@ bb.utils.export_proxies(d)}"
+
install -d -m 755 ${WORKDIR}/hooks_multistrap
# Copy config files
@@ -48,11 +53,11 @@ do_build() {
cd ${TOPDIR}
# Create root filesystem
- sudo multistrap -a ${DISTRO_ARCH} -d "${BUILDCHROOT_DIR}" -f "${WORKDIR}/multistrap.conf" || true
+ sudo -E multistrap -a ${DISTRO_ARCH} -d "${BUILDCHROOT_DIR}" -f "${WORKDIR}/multistrap.conf" || true
# Install package builder script
sudo install -m 755 ${THISDIR}/files/build.sh ${BUILDCHROOT_DIR}
# Configure root filesystem
- sudo chroot ${BUILDCHROOT_DIR} /configscript.sh
+ sudo -E chroot ${BUILDCHROOT_DIR} /configscript.sh
}
diff --git a/scripts/isar-buildenv-internal b/scripts/isar-buildenv-internal
index f14d1ff..94d7eb1 100755
--- a/scripts/isar-buildenv-internal
+++ b/scripts/isar-buildenv-internal
@@ -66,5 +66,5 @@ export PATH
BBPATH="${BUILDDIR}"
export BBPATH
-BB_ENV_EXTRAWHITE="BASEDIR BUILDDIR"
+BB_ENV_EXTRAWHITE="BASEDIR BUILDDIR http_proxy https_proxy ftp_proxy no_proxy"
export BB_ENV_EXTRAWHITE
--
2.14.1
next prev parent reply other threads:[~2017-09-07 15:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 15:03 [PATCH 0/1] Make do_rootfs work with proxy settings Andreas J. Reichel
2017-09-07 15:03 ` Andreas J. Reichel [this message]
2017-09-08 7:37 ` [PATCH 1/1] Add proxy support to isar-image-*.bb and buildchroot.bb Henning Schild
2017-09-08 8:02 ` Henning Schild
2017-09-11 10:55 ` Andreas Reichel
2017-09-11 16:50 ` Henning Schild
2017-09-11 9:24 ` Andreas Reichel
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=20170907150335.30970-2-andreas.reichel.ext@siemens.com \
--to=andreas.reichel.ext@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