Yes, I agree and in fact the patch is just now shipping
Alex Franco
On 09/03/2015 04:43 PM, Martin Jansa wrote:
On Thu, Sep 03, 2015 at 03:01:20PM -0500, Alex Franco wrote:
Hello Martin, so the error you are seeing is related to the chmodding
being done in sanity.bbclass, not the chmodding tak
On Thu, Sep 03, 2015 at 03:01:20PM -0500, Alex Franco wrote:
> 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
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.
Alex
On 09/02/2015 07:57 PM, Mart
Warning informing that chmod failed is better than fatal error preventing
me to build anything in that setup with tmpfs.
On Wed, Sep 2, 2015 at 11:27 PM, Alex Franco <
alejandro.fra...@linux.intel.com> wrote:
> Checking may be the better approach, as warning here would do little more
> than what
Yes, it was also suggested to check the directories prior to chmod'ing.
But I'm still not so sure about that, or how extensive the checking
should be. Perhaps cleaning out sticky bits more extensively could be
suggested in the documentation.
Alex Franco
On 09/02/2015 04:47 PM, Peter Seebach w
On Wed, 2 Sep 2015 11:36:45 -0500
Alex Franco wrote:
> -chmod -R -st "$BUILDDIR"
> +chmod -st "$BUILDDIR"
I was about to say! I just did an update to a version with this, and as it
happens, my build dir also contains about four full copies of tmp-glibc and
sstate-cache corresponding to differen
Checking may be the better approach, as warning here would do little
more than what the current failure does (informing that chmod failed)
Alex Franco
On 09/02/2015 01:25 PM, Martin Jansa wrote:
On Wed, Sep 02, 2015 at 06:51:23PM +0100, Richard Purdie wrote:
On Wed, 2015-09-02 at 11:36 -0500,
On Wed, Sep 02, 2015 at 06:51:23PM +0100, Richard Purdie wrote:
> On Wed, 2015-09-02 at 11:36 -0500, Alex Franco wrote:
> > Removing recursive option from chmod -st on BUILDDIR as it would
> > take very long on existing build directories
> >
> > [YOCTO 7669]
> >
> > Signed-off-by: Alex Franco
>
On Wed, 2015-09-02 at 11:36 -0500, Alex Franco wrote:
> Removing recursive option from chmod -st on BUILDDIR as it would
> take very long on existing build directories
>
> [YOCTO 7669]
>
> Signed-off-by: Alex Franco
> ---
> scripts/oe-setup-builddir | 2 +-
> 1 file changed, 1 insertion(+), 1 d
Removing recursive option from chmod -st on BUILDDIR as it would
take very long on existing build directories
[YOCTO 7669]
Signed-off-by: Alex Franco
---
scripts/oe-setup-builddir | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/oe-setup-builddir b/scripts/oe-setup-bu
10 matches
Mail list logo
