From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: can not build yocto on NFS mounted NAS
Date: Thu, 08 Aug 2013 08:53:11 -0600 [thread overview]
Message-ID: <5203B0D7.809@mlbassoc.com> (raw)
In-Reply-To: <CABcZAN=mQ-LOVPeEoi5CUDndj2Xyi1BVq8J7deby+fZQxMFKSw@mail.gmail.com>
On 2013-08-08 08:03, Chris Larson wrote:
> On Thu, Aug 8, 2013 at 6:57 AM, Robert Berger <gmane@reliableembeddedsystems.com <mailto:gmane@reliableembeddedsystems.com>> wrote:
>
> Is it like this by design, or should I file a bug in bugzilla?
>
> Previous experiments (only SSTATE and DL from NFS/NAS) seem to work and
> I guess that's also your autobuilder cluster setup.
>
>
> TMPDIR on NFS has never been supported with oe/yocto, and I doubt it will be at any time in the near future, but if that's changed, I'm sure someone will jump into the thread and
> mention it.
>
> As you say, SSTATE_DIR and DL_DIR work fine there.
Interesting. I'm building now - OEROOT on a local ext3 file system,
build/tmp on NFS - and it's working just fine. My host is Fedora (15).
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2013-08-08 14:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 13:57 can not build yocto on NFS mounted NAS Robert Berger
2013-08-08 14:03 ` Chris Larson
2013-08-08 14:53 ` Gary Thomas [this message]
2013-08-08 15:09 ` Robert Berger
2013-08-08 15:23 ` Gary Thomas
2013-08-08 17:29 ` Robert Berger
2013-08-08 17:52 ` Gary Thomas
2013-08-08 20:56 ` Robert Berger
2013-08-08 22:14 ` Gary Thomas
2013-08-18 20:44 ` Robert Berger
2013-08-20 16:45 ` lothar
2013-08-21 5:58 ` Robert Berger
2013-08-21 8:17 ` lothar
2013-08-21 6:06 ` Robert Berger
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=5203B0D7.809@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=yocto@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.