From: Robert Berger <gmane@reliableembeddedsystems.com>
To: yocto@yoctoproject.org
Cc: public-yocto-EtnWKYl6rD/WsZ/bQMPhNw@plane.gmane.org
Subject: Re: can not build yocto on NFS mounted NAS
Date: Wed, 21 Aug 2013 08:58:54 +0300 [thread overview]
Message-ID: <5214571E.7040904@reliableembeddedsystems.com> (raw)
In-Reply-To: <c98ff6d31f5118f8f3154ed5746e3fc7@denx.de>
Hi,
On 08/20/2013 07:45 PM, lothar@denx.de wrote:
>
> Hi,
> I have just two points here to ask:
>
> 1) Wouldn't simply using SSTATE_MIRRORS be a better solution here, instead?
It's not the same.
SSTATE and DL_DIR are on an nfs export anyhow and this works.
The problem here is with TMP dir (and an nfs server with a funny
underlying filesystem like UFS) and hard links.
>
> 2) Patch: wouldn't it be nicer to try the cp -al, and catch the
> CalledProcessError Exception, if it is thrown, and then run the brute
> force cp -a? Perhaps even as a general approach?
In theory yes, in practice you will find out that if you build something
like core-image-sato-sdk "cp -al" is not the only place which creates
hard links.
Regards,
Robert
..."There's an infinite number of ways to make a simple problem seem
difficult; only a handful to make a difficult problem seem simple" -
Jack Crenshaw's Law #1
My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
next prev parent reply other threads:[~2013-08-21 5:59 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
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 [this message]
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=5214571E.7040904@reliableembeddedsystems.com \
--to=gmane@reliableembeddedsystems.com \
--cc=public-yocto-EtnWKYl6rD/WsZ/bQMPhNw@plane.gmane.org \
--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.