On 2 July 2016 at 03:12, Takashi Matsuzawa
wrote:
> There seems to be PyPy, Stackless Python, etc. but I am not sure they can
> be tried 'in-place' to see if they work faster.
>
In the context of a bitbake build, the overhead of Python itself is utterly
insignificant in the context of doing the c
Dear All,
The aim of my exercise is to apply "setcap " on an executable during rootfs
creation.
I should be able to view the set capability using getcap utility when this
rootfs is mounted on the target.
As I said earlier none of the suggested approach is working here.Currently I am
qemux86 i
On 2 July 2016 at 10:22, Kumar, Shrawan wrote:
> Can someone review the attached recipe and help solve the problem
> statement ?
>
As has been said, you need to ensure the postinst is delayed so it runs on
the target and not on the build host.
http://www.yoctoproject.org/docs/2.1/dev-manual/de
Hello Ross,
Post-installation scripts run immediately after installing a package on the
target or during image creation when a package is included in an image.
Does it not mean that we can set the file attributes(setcap) during image
creation ?
I understand the delayed approach of executing i
On 2 July 2016 at 11:37, Kumar, Shrawan wrote:
> Post-installation scripts run immediately after installing a package on
> the target *or during image creation when a package is included in an
> image*.
>
> Does it not mean that we can set the file attributes(setcap) during
> image creation ?
>
AUH finished upgrade batch the result patches/logs can be found at:
https://logs.yoctoproject.org/auh//20160630215455.tar.gz, next are the
statistics:
Recipe upgrade statistics:
* Failed(do_fetch): 6
python3-setuptools, 23.1.0, Alejandro Hernandez
git, 2.9.0, Robert Yang
