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: Thu, 08 Aug 2013 20:29:56 +0300	[thread overview]
Message-ID: <5203D594.8090400@reliableembeddedsystems.com> (raw)
In-Reply-To: <5203B7F9.20001@mlbassoc.com>

Hi,

On 08/08/2013 06:23 PM, Gary Thomas wrote:
>>
>> How you do this?
>>
>> Do you use some magic build setting for this or a symlink to the nfs?
> 
> 
> I used the standard setup script, like this:
>   % . /local/poky/oe-init-build-env /MY_NFS_VOLUME/build_dir
> 
> This will create a build tree on MY_NFS_VOLUME named 'build_dir'.  Then
> I adjusted /MY_NFS_VOLUME/build_dir/conf/local.conf as needed and ran
> bitbake...
> 
> Note: I NEVER build inside of my Poky/Yocto tree - always in a separate
> build directory and quite often on a separate file system.
> 

I just tried this and with Ubuntu 12.04.2 LTS it does __NOT__ work (as
expected). I'm really surprised that you can have
/MY_NFS_VOLUME/build_dir due to the fact that there are hard links
required between the /MY_NFS_VOLUME/build_dir and where your host Linux
rootfs resides.

So either we have a different NFS setup or cp -al behaves differently.

Do you happen to have an Ubuntu build machine to test? I'm currently on
the road so it's a bit tricky for me to try with Fedora.

Regards,

Robert



..."As far as I know we never had an undetected error." - Anonymous

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




  reply	other threads:[~2013-08-08 17:30 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 [this message]
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=5203D594.8090400@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.