Re: [yocto] bitbake is corrupting my files during unpacking
well apparently this is caused by the unzip binary that is compiled by
the openembedded unzip recipe.
If I unzip the same zip file with the unzip binary that is shipped with
my system(manjaro) then the files are not corrupted but when I use the
unzip binary compiled by the openembedded recipe I get error and file
corruptions.
These are some of the errors I get when unzipping with the openembedded
unzip:
lchmod (file attributes) error: Function not implemented
linux-amlogic-amlogic-3.14-nougat/security/keys/request_key_auth.c -> /*
Request key authorisation token key definition.^J *^J * Copyright (C)
2005 Red Hat, Inc. All Rights Reserved.^J * Written by David Howells
(dhowe...@redhat.com)^J *^J * This program is free software; you can
redistribute it and/or^J * modify it under the terms of the GNU General
Public License^J * as published by the Free Software Foundation; either
version^J * 2 of the License, or (at your option) any later version.^J
*^J * See Documentation/security/keys-request-key.txt^J */^J^J#include
^J#include ^J#include
^J#include ^J#include
^J#include ^J#include
"internal.h"^J#include ^J^Jstatic int
request_key_auth_instantiate(struct key *,^J^I^I^I^I^Istruct
key_preparsed_payload *);^Jstatic void request_key_auth_describe(const
struct key *, struct seq_file *);^Jstatic void
request_key_auth_revoke(struct key *);^Jstatic void
request_key_auth_destroy(struct key *);^Jstatic long
request_key_auth_read(const struct key *, char __user *,
size_t);^J^J/*^J * The request-key authorisation key type definition.^J
*/^Jstruct key_type key_type_request_key_auth = {^J^I.name^I^I=
".request_key_auth",^J^I.def_datalen^I= sizeof(struct
request_key_auth),^J^I.instantiate^I=
request_key_auth_instantiate,^J^I.describe^I=
request_key_auth_describe,^J^I.revoke^I^I=
request_key_auth_revoke,^J^I.destroy^I=
request_key_auth_destroy,^J^I.read^I^I=
request_key_auth_read,^J};^J^J/*^J * Instantiate a request-key
authorisation key.^J */^Jstatic int request_key_auth_instantiate(struct
key *key,^J^I^I^I^I^Istruct key_preparsed_payload
*prep)^J{^J^Ikey->payload.data = (struct request_key_auth
*)prep->data;^J^Ireturn 0;^J}^J^J/*^J * Describe an authorisation
token.^J */^Jstatic void request_key_auth_describe(const struct key
*key,^J^I^I^I^I struct seq_file *m)^J{^J^Istruct request_key_auth *rka =
key->payload.data;^J^J^Iseq_puts(m, "key:");^J^Iseq_puts(m,
key->description);^J^Iif (key_is_instantiated(key))^J^I^Iseq_printf(m, "
pid:%d ci:%zu", rka->pid, rka->callout_len);^J}^J^J/*^J * Read the
callout_info data (retrieves the callout information).^J * - the key's
semaphore is read-locked^J */^Jstatic long request_key_auth_read(const
struct key *key,^J^I^I^I^I char __user *buffer, size_t
buflen)^J{^J^Istruct request_key_auth *rka =
key->payload.data;^J^Isize_t datalen;^J^Ilong ret;^J^J^Idatalen =
rka->callout_len;^J^Iret = datalen;^J^J^I/* we can return the data as is
*/^J^Iif (buffer && buflen > 0) {^J^I^Iif (buflen >
datalen)^J^I^I^Ibuflen = datalen;^J^J^I^Iif (copy_to_user(buffer,
rka->callout_info, buflen) != 0)^J^I^I^Iret = -EFAULT;^J^I}^J^J^Ireturn
ret;^J}^J^J/*^J * Handle revocation of an authorisation token key.^J *^J
* Called with the key sem write-locked.^J */^Jstatic void
request_key_auth_revoke(struct key *key)^J{^J^Istruct request_key_auth
*rka = key->payload.data;^J^J^Ikenter("{%d}", key->serial);^J^J^Iif
(rka->cred) {^J^I^Iput_cred(rka->cred);^J^I^Irka->cred =
NULL;^J^I}^J}^J^J/*^J * Destroy an instantiation authorisation token
key.^J */^Jstatic void request_key_auth_destroy(struct key
*key)^J{^J^Istruct request_key_auth *rka =
key->payload.data;^J^J^Ikenter("{%d}", key->serial);^J^J^Iif (rka->cred)
{^J^I^Iput_cred(rka->cred);^J^I^Irka->cred =
NULL;^J^I}^J^J^Ikey_put(rka->target_key);^J^Ikey_put(rka->dest_keyring);^J^Ikfree(rka->callout_info);^J^Ikfree(rka);^J}^J^J/*^J
* Create an authorisation token for /sbin/request-key or whoever to
gain^J * access to the caller's security data.^J */^Jstruct key
*request_key_auth_new(struct key *target, const void
*callout_info,^J^I^I^I^I size_t callout_len, struct key
*dest_keyring)^J{^J^Istruct request_key_auth *rka, *irka;^J^Iconst
struct cred *cred = current->cred;^J^Istruct key *authkey =
NULL;^J^Ichar desc[20];^J^Iint ret;^J^J^Ikenter("%d,",
target->serial);^J^J^I/* allocate a auth record */^J^Irka =
kmalloc(sizeof(*rka), GFP_KERNEL);^J^Iif (!rka) {^J^I^Ikleave(" =
-ENOMEM");^J^I^Ireturn ERR_PTR(-ENOMEM);^J^I}^J^Irka->callout_info =
kmalloc(callout_len, GFP_KERNEL);^J^Iif (!rka->callout_info)
{^J^I^Ikleave(" = -ENOMEM");^J^I^Ikfree(rka);^J^I^Ireturn
ERR_PTR(-ENOMEM);^J^I}^J^J^I/* see if the calling process is already
servicing the key request of^J^I * another process */^J^Iif
(cred->request_key_auth) {^J^I^I/* it is - use that instantiation
context here too
*/^J^I^Idown_read(&cred->request_key_auth->sem);^J^J^I^I/* if the auth
key has been revoked, then the key we're^J^I^I * servicing is
[yocto] can bitbake build offline ?
Hi, is there a way I can run a bitbake build offline? I have all the required sources of the target in the sources directory, and I have built the target multiple times with internet connection, but when I build offline it fails because it needs internet access during parsing recipes. Can I tell bitbake to skip running `git ls-remote` during parsing recipes so I can build offline? Thanks -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] can bitbake build offline ?
This page has a tip on what might be causing 'git ls-remote': https://wiki.yoctoproject.org/wiki/How_do_I#Q:_How_do_I_create_my_own_source_download_mirror_.3F Alex 2018-07-21 10:32 GMT+02:00 MOHAMMAD RASIM : > Hi, is there a way I can run a bitbake build offline? I have all the > required sources of the target in the sources directory, and I have built > the target multiple times with internet connection, but when I build offline > it fails because it needs internet access during parsing recipes. > Can I tell bitbake to skip running `git ls-remote` during parsing recipes so > I can build offline? > > Thanks > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] why compile "xserver-xorg" package on wayland projects?
It shouldn't complain, what is the error? The reason it's being built
is because you've got X11 and Wayland enabled, so it's building
xwayland. When you add wayland to DISTRO_FEATURES, also remove x11.
Ross
On 21 July 2018 at 05:48, tugouxp <13824125...@163.com> wrote:
> hi folks:
> i am working on project with "DISTRO_FEATURE" set to "wayalnd", during
> the compile procedure, i saw the xserver pakage was compiled, which would
> complain compile error and stop the process.
>
> i try to debug the dependciy, it seems the "weston" package bring the
> xorg-server ,package in , so i try to change the default bb file of poky
> poky/meta/recipes-graphics/wayland/weston_2.0.0.bb
> and comment the following line
> #RDEPENDS_${PN}-xwayland += "xserver-xorg-xwayland"
> it seems work.
> i dont know the reason and want to know if any elegant way to dealt with
> this prolbems?
>
> thanks for your supply.
>
> NOTE: linux-tina: compiling from external source tree
> /home/caozilong/WorkSpace/glibc/repo/lichee/linux-4.4
> Currently 2 running tasks (2538 of 4483) 56%
> |
> |
> 0: linux-tina-4.4.89-r0 do_compile - 0s (pid 1550)
> 1: xserver-xorg-2_1.19.3-r0 do_configure - 0s (pid 1578)
>
>
>
>
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] python-cython_0.25.2 Krogoth: EXCLUDE_FROM_WORLD
Hi all
I'd like to add cython 0.25.2 to Krogoth.
I need it to try kivy in Krogoth on IMX6
In my layer under recipes-devtools/python folder I added the recipe
python-cython_0.25.2.bb with this inside
inherit setuptools
require recipes-devtools/python/python-cython.inc
RDEPENDS_${PN} += " \
python-distribute \
"
If I run
bitbake -s -vD | grep cython
this is the behaviour
mauro@z600:~/Sources/bsp/clini5-build$ bitbake -s | grep cython
python-cython :0.24-r0
python-cython-native :0.24-r0
python3-cython :0.24-r0
python3-cython-native :0.24-r0
Why the 0.25.2 version is ignored?
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] SDK and out of tree modules
Hello, I have been building some modules using the SDK for a while now. This is mostly for development flow purposes but we have had a few customers doing this as well. To get this to work we always need to run “make silentoldconfig scripts” inside the RFS of the SDK on the build host. Many folks forget to do this this and thus many, many questions come my way about the SDK being broken and they can’t build their modules (not all users are kernel experts or even intermediates… they just want to apply a patch and quickly move on to their app). Is there a way to do this auto-magically during the installation of the SDK by adding some type of scripts etc… to the recipe? I assume it needs to be done at install time since while the build host is x86… the exact linux distro is not known until then (or does that matter?). —Russ -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] why compile "xserver-xorg" package on wayland projects?
I have patches cooking see
http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/master
On Sat, Jul 21, 2018 at 5:27 AM Burton, Ross wrote:
>
> It shouldn't complain, what is the error? The reason it's being built
> is because you've got X11 and Wayland enabled, so it's building
> xwayland. When you add wayland to DISTRO_FEATURES, also remove x11.
>
> Ross
>
> On 21 July 2018 at 05:48, tugouxp <13824125...@163.com> wrote:
> > hi folks:
> > i am working on project with "DISTRO_FEATURE" set to "wayalnd", during
> > the compile procedure, i saw the xserver pakage was compiled, which would
> > complain compile error and stop the process.
> >
> > i try to debug the dependciy, it seems the "weston" package bring the
> > xorg-server ,package in , so i try to change the default bb file of poky
> > poky/meta/recipes-graphics/wayland/weston_2.0.0.bb
> > and comment the following line
> > #RDEPENDS_${PN}-xwayland += "xserver-xorg-xwayland"
> > it seems work.
> > i dont know the reason and want to know if any elegant way to dealt with
> > this prolbems?
> >
> > thanks for your supply.
> >
> > NOTE: linux-tina: compiling from external source tree
> > /home/caozilong/WorkSpace/glibc/repo/lichee/linux-4.4
> > Currently 2 running tasks (2538 of 4483) 56%
> > |
> > |
> > 0: linux-tina-4.4.89-r0 do_compile - 0s (pid 1550)
> > 1: xserver-xorg-2_1.19.3-r0 do_configure - 0s (pid 1578)
> >
> >
> >
> >
> >
> >
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> >
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] SDK and out of tree modules
On Sat, Jul 21, 2018 at 6:20 AM Russell Peterson wrote: > > Hello, > > I have been building some modules using the SDK for a while now. This is > mostly for development flow purposes but we have had a few customers doing > this as well. To get this to work we always need to run “make > silentoldconfig scripts” inside the RFS of the SDK on the build host. Many > folks forget to do this this and thus many, many questions come my way about > the SDK being broken and they can’t build their modules (not all users are > kernel experts or even intermediates… they just want to apply a patch and > quickly move on to their app). Is there a way to do this auto-magically > during the installation of the SDK by adding some type of scripts etc… to the > recipe? I assume it needs to be done at install time since while the build > host is x86… the exact linux distro is not known until then (or does that > matter?). > are you using extensible SDK ? in that case I think do_make_scripts from module-base.bbclass should be helpful > —Russ > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] python-cython_0.25.2 Krogoth: EXCLUDE_FROM_WORLD
On Sat, Jul 21, 2018 at 5:44 AM Mauro Ziliani wrote:
>
> Hi all
>
> I'd like to add cython 0.25.2 to Krogoth.
>
> I need it to try kivy in Krogoth on IMX6
>
>
> In my layer under recipes-devtools/python folder I added the recipe
>
> python-cython_0.25.2.bb with this inside
>
>
> inherit setuptools
> require recipes-devtools/python/python-cython.inc
>
>
> RDEPENDS_${PN} += " \
> python-distribute \
> "
>
> If I run
>
> bitbake -s -vD | grep cython
>
>
> this is the behaviour
>
> mauro@z600:~/Sources/bsp/clini5-build$ bitbake -s | grep cython
> python-cython :0.24-r0
> python-cython-native :0.24-r0
> python3-cython :0.24-r0
> python3-cython-native :0.24-r0
>
> Why the 0.25.2 version is ignored?
I think its because of layer priority. your layer should be higher
priority than meta-python
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] SDK and out of tree modules
No, just the standard SDK. I was having issues building the eSDK back when we used pyro and never fully figured it out… but we have since upgraded to rocko. I should revisit the eSDK and see if it works for me now or find the root cause since it sounds useful. Thanks, Khem. —Russ > On Jul 21, 2018, at 1:34 PM, Khem Raj wrote: > > On Sat, Jul 21, 2018 at 6:20 AM Russell Peterson > wrote: >> >> Hello, >> >> I have been building some modules using the SDK for a while now. This is >> mostly for development flow purposes but we have had a few customers doing >> this as well. To get this to work we always need to run “make >> silentoldconfig scripts” inside the RFS of the SDK on the build host. Many >> folks forget to do this this and thus many, many questions come my way about >> the SDK being broken and they can’t build their modules (not all users are >> kernel experts or even intermediates… they just want to apply a patch and >> quickly move on to their app). Is there a way to do this auto-magically >> during the installation of the SDK by adding some type of scripts etc… to >> the recipe? I assume it needs to be done at install time since while the >> build host is x86… the exact linux distro is not known until then (or does >> that matter?). >> > > are you using extensible SDK ? in that case I think do_make_scripts > from module-base.bbclass should be helpful > >> —Russ >> >> -- >> ___ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
