public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Cedric Hombourger <Cedric_Hombourger@mentor.com>
To: <isar-users@googlegroups.com>
Subject: [PATCH 1/1] buildchroot: bind mount our downloads folder
Date: Thu, 1 Mar 2018 09:25:46 +0000	[thread overview]
Message-ID: <20180301092546.47270-2-Cedric_Hombourger@mentor.com> (raw)
In-Reply-To: <20180301092546.47270-1-Cedric_Hombourger@mentor.com>

dpkg-base would only mount our downloads folder if isar-apt is not
yet mounted. When we do a full build, the buildchroot recipe will
mount isar-apt and the mount condition found in the dpkg-base class
will always be false. Bind mount the downloads folder from the
buildchroot (we could have also changed the dpkg-base class).

See https://groups.google.com/forum/#!topic/isar-users/wuxNStTkVtg

Signed-off-by: Cedric Hombourger <Cedric_Hombourger@mentor.com>
---
 meta/recipes-devtools/buildchroot/buildchroot.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-devtools/buildchroot/buildchroot.bb b/meta/recipes-devtools/buildchroot/buildchroot.bb
index 520daf9..2fc5297 100644
--- a/meta/recipes-devtools/buildchroot/buildchroot.bb
+++ b/meta/recipes-devtools/buildchroot/buildchroot.bb
@@ -68,6 +68,7 @@ do_build() {
     sudo mount --bind ${DEPLOY_DIR_APT}/${DISTRO} ${BUILDCHROOT_DIR}/isar-apt
     sudo mount -t devtmpfs -o mode=0755,nosuid devtmpfs ${BUILDCHROOT_DIR}/dev
     sudo mount -t proc none ${BUILDCHROOT_DIR}/proc
+    sudo mount --bind ${DL_DIR} ${BUILDCHROOT_DIR}/downloads
 
     # Create root filesystem
     sudo -E multistrap -a ${DISTRO_ARCH} -d "${BUILDCHROOT_DIR}" -f "${WORKDIR}/multistrap.conf"
-- 
2.11.0


  reply	other threads:[~2018-03-01  9:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-01  9:25 [PATCH 0/1] bind mount our downloads folder from buildchroot Cedric Hombourger
2018-03-01  9:25 ` Cedric Hombourger [this message]
2018-03-02 12:17   ` [PATCH 1/1] buildchroot: bind mount our downloads folder Jan Kiszka
2018-03-02 14:42   ` 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=20180301092546.47270-2-Cedric_Hombourger@mentor.com \
    --to=cedric_hombourger@mentor.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