From: Robert Berger <gmane@reliableembeddedsystems.com>
To: yocto@yoctoproject.org
Subject: can not build yocto on NFS mounted NAS
Date: Thu, 08 Aug 2013 16:57:20 +0300 [thread overview]
Message-ID: <ku083q$oa8$1@ger.gmane.org> (raw)
Hi,
I tried to build to build bitbake core-image-minimal-dev on some nfs
mounted NAS.
Pseudo is not present but is required, building this first before the
main build
Parsing recipes: 100%
|###################################################################################################################################|
Time: 00:00:20
Parsing of 819 .bb files complete (0 cached, 819 parsed). 1126 targets,
47 skipped, 0 masked, 0 errors.
Build Configuration:
BB_VERSION = "1.18.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-12.04"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "beagle-xm-ml"
DISTRO = "poky"
DISTRO_VERSION = "1.4.1"
TUNE_FEATURES = "armv7a vfp neon"
TARGET_FPU = "vfp-neon"
meta
meta-yocto
meta-yocto-bsp =
"beagleboard_dylan-9.0.1_LOCAL:73f103bf9b2cdf985464dc53bf4f1cfd71d4531f"
It fails pretty soon with:
ERROR: Error executing a python function in
/yoctotmp/manual-build/poky/meta/recipes-devtools/quilt/quilt-native_0.60.bb:
CalledProcessError: Command 'cp -al
/yoctotmp/manual-build/poky/beagle-xm/tmp/work/x86_64-linux/quilt-native/0.60-r0/sysroot-destdir/yoctotmp/manual-build/poky/beagle-xm/tmp/sysroots/x86_64-linux/*
/yoctotmp/manual-build/poky/beagle-xm/tmp/work/x86_64-linux/quilt-native/0.60-r0/sstate-build-populate-sysroot/x86_64-linux'
returned non-zero
exit status 1 with output cp: cannot create hard link
`/yoctotmp/manual-build/poky/beagle-xm/tmp/work/x86_64-linux/quilt-native/0.60-r0/sstate-build-populate-sysroot/x86
_64-linux/usr/share/quilt/compat/awk' to
`/yoctotmp/manual-build/poky/beagle-xm/tmp/work/x86_64-linux/quilt-native/0.60-r0/sysroot-destdir/yoctotmp/manual-build/poky/beag
le-xm/tmp/sysroots/x86_64-linux/usr/share/quilt/compat/awk': Unknown
error 524
A bit of further digging reveals that underneath
/yoctotmp/manual-build/poky/beagle-xm/tmp/work/x86_64-linux/quilt-native/0.60-r0/sysroot-destdir/yoctotmp/manual-build/poky/beagle-xm/tmp/sysroots/x86_64-linux/*
we have a symbolic link to
/yoctotmp/manual-build/poky/beagle-xm/tmp/work/x86_64-linux/quilt-native/0.60-r0/sysroot-destdir/yoctotmp/manual-build/poky/beagle-xm/tmp/sysroots/x86_64-linux/usr/share/quilt/compat/awk
-> /usr/bin/gawk
Since hard links can not be made between different file systems (local
ext4 and nfs) the cp -al fails.
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.
Regards,
Robert
...Under a government which imprisons any unjustly, the true place for a
just man is also a prison. -- Henry David Thoreau
My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
next reply other threads:[~2013-08-08 13:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 13:57 Robert Berger [this message]
2013-08-08 14:03 ` can not build yocto on NFS mounted NAS 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
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='ku083q$oa8$1@ger.gmane.org' \
--to=gmane@reliableembeddedsystems.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.