All of lore.kernel.org
 help / color / mirror / Atom feed
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: Sun, 18 Aug 2013 23:44:05 +0300	[thread overview]
Message-ID: <52113215.5090102@reliableembeddedsystems.com> (raw)
In-Reply-To: <52041846.8010201@mlbassoc.com>

Hi,

Just for the record I was able to remove the hard link with a small
patch and now things look good (so far) - although it will consume more
disk space.

diff --git a/meta/lib/oe/path.py b/meta/lib/oe/path.py
index faa0f61..3225993 100644
--- a/meta/lib/oe/path.py
+++ b/meta/lib/oe/path.py
@@ -90,7 +90,7 @@ def copyhardlinktree(src, dst):
         if not len(os.listdir(src)):
             return
         src = src + "/*"
-    cmd = 'cp -al %s %s' % (src, dst)
+    cmd = 'cp -a %s %s' % (src, dst)
     check_output(cmd, shell=True, stderr=subprocess.STDOUT)

 def remove(path, recurse=True):

Regards,

Robert
..."But I have a slowly coagulating theory that the size of a project is
directly proportional to the possibility that significant bugs will crop
up. Exponentiate for each additional programmer involved." - Steven K.
Halliburton

My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1




  reply	other threads:[~2013-08-18 20:44 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 [this message]
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=52113215.5090102@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.