All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: "Amrun Nisha.R" <amrunnishar@gmail.com>, yocto@lists.yoctoproject.org
Subject: Re: [yocto] Offline Build #yocto
Date: Mon, 20 Jul 2020 16:12:06 +0100	[thread overview]
Message-ID: <8d0258be3275bc76159bdd096d75c8c7984ff6d3.camel@linuxfoundation.org> (raw)
In-Reply-To: <16314.1595254681269487194@lists.yoctoproject.org>

On Mon, 2020-07-20 at 07:18 -0700, Amrun Nisha.R wrote:
> For gnu-config-native-20150728, I have copied the git2 folder from
> older build folder to new build folder. It is fixed now.
> 
> But I'm getting do_fetch error for the ncurses and ncurses_native. I
> have attached the log file for both packages.
> 
> Actually I have doubts regarding the build folders:
> 1. As mentioned above, I have copied the sources and download folder
> to the another machine. While bitbaking, it again doing the do_fetch
> process. Whether I have to copy the build folder (build_wayland)?
> 2. Is there any particular folders should be copy other than the
> sources and download folder to build the yocto project in offline?

When you run the original build, where is DL_DIR pointing? Find that
and make sure the same directory is available to the second build.

It sounds a bit like you have multiple builds are not sharing the same
DL_DIR so either make them share them, or copy them all.

Cheers,

Richard


  reply	other threads:[~2020-07-20 15:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20  6:05 Offline Build #yocto Amrun Nisha.R
2020-07-20 13:54 ` [yocto] " Richard Purdie
2020-07-20 14:18   ` Amrun Nisha.R
2020-07-20 15:12     ` Richard Purdie [this message]
2020-07-20 18:14       ` Amrun Nisha.R
2020-07-20 19:17         ` [yocto] " Martin Jansa
2020-07-21  3:26           ` Amrun Nisha.R
2020-07-24 19:06             ` [yocto] " Fred Baksik
2020-07-27  4:38               ` Amrun Nisha.R
2020-07-27 19:18                 ` [yocto] " Fred Baksik

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=8d0258be3275bc76159bdd096d75c8c7984ff6d3.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=amrunnishar@gmail.com \
    --cc=yocto@lists.yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.