From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Hans Beckérus" <hans.beckerus@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] image/populate_sdk: Ensure symlinks in target sysroot are relative
Date: Thu, 12 Sep 2013 09:02:25 +0100 [thread overview]
Message-ID: <1378972945.3484.217.camel@ted> (raw)
In-Reply-To: <CAFyqS9rx5ycOOzfxkCxr5N+wCKBTgqQYjzzmc3CA5u-MZNHA1g@mail.gmail.com>
On Thu, 2013-09-12 at 09:48 +0200, Hans Beckérus wrote:
> I have a slight problem with this patch. The new
> sysroot-relativelinks.py does not obtain the proper access protection
> bits!?
> Which results in the following error when packaging the SDK
>
> /home/poky/build/tmp/work/zynq_zc706-poky-linux-gnueabi/rootfs-default/1.0-r0/temp/run.populate_sdk_image.20803:
> line 496: /home/poky/scripts/sysroot-relativelinks.py: Permission
> denied
>
> [home/poky]: ls -l scripts/sysroot-relativelinks.py
> -rw-rw-r-- 1 poky poky 959 Sep 12 09:38 scripts/sysroot-relativelinks.py
>
> The execution bit is missing!?
>
> I can of course apply the execution bit manually, but what may cause
> the patch to not set the bits properly in my scripts folder for new
> files? Please advise.
I checked the poky and oe-core trees and they have a+x:
http://git.yoctoproject.org/cgit.cgi/poky/tree/scripts
http://git.openembedded.org/openembedded-core/tree/scripts
so I'm a bit puzzled. How did you update your tree?
Cheers,
Richard
next prev parent reply other threads:[~2013-09-12 8:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 9:42 [PATCH] image/populate_sdk: Ensure symlinks in target sysroot are relative Richard Purdie
2013-09-12 7:48 ` Hans Beckérus
2013-09-12 8:02 ` Richard Purdie [this message]
2013-09-12 8:29 ` Hans Beckérus
2013-09-12 14:54 ` Hans Beckérus
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=1378972945.3484.217.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=hans.beckerus@gmail.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox