<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hello Martin, so the error you are seeing is related to the
chmodding being done in sanity.bbclass, not the chmodding taking
place in oe-setup-builddir. I am adding a catch and a warning for
that, as I reproduce your setup so I can also reproduce the OSError.<br>
<br>
Alex<br>
<br>
<div class="moz-cite-prefix">On 09/02/2015 07:57 PM, Martin Jansa
wrote:<br>
</div>
<blockquote
cite="mid:CA+chaQddNikh4vveg30U8WVYG5XcpewM9OHrgahzr_qTHSF+pw@mail.gmail.com"
type="cite">
<div dir="ltr">Warning informing that chmod failed is better than
fatal error preventing me to build anything in that setup with
tmpfs.
<div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Sep 2, 2015 at 11:27 PM,
Alex Franco <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:alejandro.franco@linux.intel.com"
target="_blank">alejandro.franco@linux.intel.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Checking
may be the better approach, as warning here would do
little more than what the current failure does
(informing that chmod failed)<span class="HOEnZb"><font
color="#888888"><br>
<br>
Alex Franco</font></span>
<div class="HOEnZb">
<div class="h5"><br>
<br>
On 09/02/2015 01:25 PM, Martin Jansa wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, Sep 02, 2015 at 06:51:23PM +0100, Richard
Purdie wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0
0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
On Wed, 2015-09-02 at 11:36 -0500, Alex Franco
wrote:<br>
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
Removing recursive option from chmod -st on
BUILDDIR as it would<br>
take very long on existing build directories<br>
<br>
[YOCTO 7669]<br>
<br>
Signed-off-by: Alex Franco <<a
moz-do-not-send="true"
href="mailto:alejandro.franco@linux.intel.com"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:alejandro.franco@linux.intel.com">alejandro.franco@linux.intel.com</a></a>><br>
---<br>
scripts/oe-setup-builddir | 2 +-<br>
1 file changed, 1 insertion(+), 1
deletion(-)<br>
<br>
diff --git a/scripts/oe-setup-builddir
b/scripts/oe-setup-builddir<br>
index f5b7e4e..44c7dcc 100755<br>
--- a/scripts/oe-setup-builddir<br>
+++ b/scripts/oe-setup-builddir<br>
@@ -24,7 +24,7 @@ if [ -z "$BUILDDIR" ]; then<br>
fi<br>
mkdir -p "$BUILDDIR/conf"<br>
-chmod -R -st "$BUILDDIR"<br>
+chmod -st "$BUILDDIR"<br>
</blockquote>
I think you did this so that conf/ gets the
right permissions too.<br>
Perhaps the best approach is:<br>
<br>
+chmod -st "$BUILDDIR" $BUILDDIR/conf"<br>
</blockquote>
Can we add "|| bbwarn foo"<br>
<br>
for cases when it doesn't work for whatever reason
or check the<br>
permissions of these 2 dirs before calling chmod?<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0
0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
?<br>
<br>
Cheers,<br>
<br>
Richard<br>
<br>
-- <br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a moz-do-not-send="true"
href="mailto:Openembedded-core@lists.openembedded.org"
target="_blank">Openembedded-core@lists.openembedded.org</a><br>
<a moz-do-not-send="true"
href="http://lists.openembedded.org/mailman/listinfo/openembedded-core"
rel="noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
</blockquote>
</blockquote>
<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>