[yocto] [meta-selinux][PATCH] audit: update to v2.7.1

[Tim Orling]

Added swig-native to DEPENDS

Signed-off-by: Tim Orling 
---
 recipes-security/audit/{audit_2.7.bb => audit_2.7.1.bb} | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
 rename recipes-security/audit/{audit_2.7.bb => audit_2.7.1.bb} (95%)

diff --git a/recipes-security/audit/audit_2.7.bb 
b/recipes-security/audit/audit_2.7.1.bb
similarity index 95%
rename from recipes-security/audit/audit_2.7.bb
rename to recipes-security/audit/audit_2.7.1.bb
index 6bcbecd..975e6e9 100644
--- a/recipes-security/audit/audit_2.7.bb
+++ b/recipes-security/audit/audit_2.7.1.bb
@@ -15,8 +15,8 @@ SRC_URI = 
"http://people.redhat.com/sgrubb/${BPN}/${BPN}-${PV}.tar.gz \
file://auditd.service \
file://audit-volatile.conf \
 "
-SRC_URI[md5sum] = "d3b1017e259509b9b3054656d0d2b4e9"
-SRC_URI[sha256sum] = 
"05533f5d88d9520ceebfd8bfb3fd998ca4a2b246757fec7bbd8e33c287544537"
+SRC_URI[md5sum] = "b224ea6f000c8281e5deee86903ac5ba"
+SRC_URI[sha256sum] = 
"0441790794fd9375dbca598fa0ffb46c57ff37b3a24b94ffec0bbee3215cca09"
 
 inherit autotools pythonnative update-rc.d systemd
 
@@ -26,7 +26,7 @@ INITSCRIPT_PARAMS = "defaults"
 
 SYSTEMD_SERVICE_${PN} = "auditd.service"
 
-DEPENDS += "python tcp-wrappers libcap-ng linux-libc-headers (>= 2.6.30)"
+DEPENDS += "python tcp-wrappers libcap-ng linux-libc-headers (>= 2.6.30) 
swig-native"
 
 EXTRA_OECONF += "--without-prelude \
--with-libwrap \
-- 
2.9.3

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to gracefully disable a setscene task?

[Gary Thomas]

On 2017-02-11 02:24, Khem Raj wrote:

On Fri, Feb 10, 2017 at 3:05 PM, Xiaohui Liu  wrote:

Hi everyone,

I tried to disable a setscene task as below:

do_populate_lic_setscene () {
   exit 1
}



you could use something like

deltask  do_populate_lic_setscene


It works but shows a warning:

WARNING: Logfile for failed setscene task is
/data/users/xhliu/poky/build-arm/tmp/work/armada39x-poky-linux-gnueabi/linux-terragraph/4.4.8-r0/temp/log.do_populate_lic_setscene.2825388
WARNING: Setscene task 1
(/data/users/xhliu/poky/meta-terragraph/recipes-kernel/linux/linux-terragraph_4.4.8.bb,
do_populate_lic_setscene) failed with exit code '1' - real task will be run
instead

Any way to disable it without the warning? Thanks in advance.


Why would you want to do this?

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to gracefully disable a setscene task?

[Khem Raj]

On Fri, Feb 10, 2017 at 3:05 PM, Xiaohui Liu  wrote:
> Hi everyone,
>
> I tried to disable a setscene task as below:
>
> do_populate_lic_setscene () {
>exit 1
> }
>

you could use something like

deltask  do_populate_lic_setscene

> It works but shows a warning:
>
> WARNING: Logfile for failed setscene task is
> /data/users/xhliu/poky/build-arm/tmp/work/armada39x-poky-linux-gnueabi/linux-terragraph/4.4.8-r0/temp/log.do_populate_lic_setscene.2825388
> WARNING: Setscene task 1
> (/data/users/xhliu/poky/meta-terragraph/recipes-kernel/linux/linux-terragraph_4.4.8.bb,
> do_populate_lic_setscene) failed with exit code '1' - real task will be run
> instead
>
> Any way to disable it without the warning? Thanks in advance.
>
> Best,
> Xiaohui
>
> --
> ___
> 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] How to gracefully disable a setscene task?

[Xiaohui Liu]

Hi everyone,

I tried to disable a setscene task as below:

*do_populate_lic_setscene () {*
*   exit 1*
*}*

It works but shows a warning:

*WARNING: Logfile for failed setscene task is
/data/users/xhliu/poky/build-arm/tmp/work/armada39x-poky-linux-gnueabi/linux-terragraph/4.4.8-r0/temp/log.do_populate_lic_setscene.2825388*
*WARNING: Setscene task 1
(/data/users/xhliu/poky/meta-terragraph/recipes-kernel/linux/linux-terragraph_4.4.8.bb
, do_populate_lic_setscene) failed with
exit code '1' - real task will be run instead*

Any way to disable it without the warning? Thanks in advance.

Best,
Xiaohui
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH v2 5/5] rmc: add database extraction functionality

[Jianxun Zhang]

Todor,
Appreciate the V2 series. I have only one real concern on using system() in 
this patch and the whole series. The other comments are more for corner cases 
which have less impact.

I could miss some of your feedbacks in V1 threads. Sorry for not to point out 
things earlier before the V2.

Thanks

> On Feb 9, 2017, at 11:17 AM, Todor Minchev  
> wrote:
> 
> The contents of an existing database file can be extracted with the -E option.
> By default the top level of the directory tree is rmc_db_dump, an alternative
> path can be specified with the -o option. The file blobs corresponding
> to a given record will be saved in a separate sub-directory. The sub-directory
> name of each record is the signature corresponding to the fingerprint for that
> record with all non-alphanumeric characters stripped.
> 
> Example:
> ./src/rmc -E -d rmc.db -o output/directory/
> 
> Successfully extracted rmc.db
> 
> Signed-off-by: Todor Minchev 
> ---
> inc/rmc_api.h |   9 +
> inc/rmcl.h|   7 
> src/lib/api.c | 106 +-
> src/lib/common/rmcl.c |  17 +++-
> src/rmc.c |  30 +-
> 5 files changed, 157 insertions(+), 12 deletions(-)
> 
> diff --git a/inc/rmc_api.h b/inc/rmc_api.h
> index a484389..2f8c978 100644
> --- a/inc/rmc_api.h
> +++ b/inc/rmc_api.h
> @@ -109,6 +109,15 @@ extern int read_file(const char *pathname, char **data, 
> rmc_size_t* len);
>  */
> int write_file(const char *pathname, void *data, rmc_size_t len, int append);
> 
> +/* extract the contents of a database file and store the files corresponding 
> to
> + * each record in a separate directory. The name of each directory is the 
> signature
> + * of the fingerpring for that record with all non-alphanumeric characters 
> stripped
> + * (in) db_pathname: The path and file name of a RMC database file generated 
> by RMC tool
> + * (in) output_path: A directory path to extract the database to
> + * return: 0 on success, non-zero on failure.
> + */
> +int dump_db(char *db_pathname, char *output_path) ;
> +
> #else
> /* 2 - API for UEFI context */
> 
> diff --git a/inc/rmcl.h b/inc/rmcl.h
> index 5bbad42..471ebfe 100644
> --- a/inc/rmcl.h
> +++ b/inc/rmcl.h
> @@ -164,4 +164,11 @@ extern int rmcl_generate_db(rmc_record_file_t 
> *record_files, rmc_uint8_t **rmc_d
>  */
> extern int query_policy_from_db(rmc_fingerprint_t *fingerprint, rmc_uint8_t 
> *rmc_db, rmc_uint8_t type, char *blob_name, rmc_file_t *policy);
> 
> +/*
> + * Check if db_blob has a valid rmc database signature
> + *
> + * return 0 if db_blob has a valid signature or non-zero otherwise
> + */
> +int is_rmcdb(rmc_uint8_t *db_blob);
> +
> #endif /* INC_RMCL_H_ */
> diff --git a/src/lib/api.c b/src/lib/api.c
> index 0adb390..56746a4 100644
> --- a/src/lib/api.c
> +++ b/src/lib/api.c
> @@ -3,6 +3,7 @@
>  * RMC API implementation for Linux user space
>  */
> 
> +#define _GNU_SOURCE
> #include 
> #include 
> #include 
> @@ -10,12 +11,15 @@
> #include 
> #include 
> #include 
> +#include 
> +#include 
> 
> #include 
> #include 
> 
> -#define EFI_SYSTAB_PATH "/sys/firmware/efi/systab"
> -#define SYSTAB_LEN 4096 /* assume 4kb is enough...*/
> +#define EFI_SYSTAB_PATH  "/sys/firmware/efi/systab"
> +#define SYSTAB_LEN   4096 /* assume 4kb is enough...*/
> +#define DB_DUMP_DIR  "./rmc_db_dump"  /* directory to store db data dump 
> */
> 
> int read_file(const char *pathname, char **data, rmc_size_t* len) {
> int fd = -1;
> @@ -325,3 +329,101 @@ int rmc_gimme_file(char* db_pathname, char *file_name, 
> rmc_file_t *file) {
> 
> return ret;
> }
> +
> +void remove_non_alphanum(char *in) {
> +char c;
> +unsigned long i = 0, j = 0;
> +
> +while ((c = in[i++]) != '\0'){
> +if (isalnum(c))
> +in[j++] = c;
I think this will work in the almost all the real cases. A corner case, though 
very rare, is two fingerprints differ each other _only_ by non alphnum 
characters. The dumps of two different fingerprints will be wrongly in the same 
dir as a result. (We can’t dictate what FW engineers put into bios)

Maybe in the future we could use ASCII code of hex values of a signature which 
is a field with a fixed length as dir name?

> +}
> +in[j] = '\0';
> +}
> +
> +int dump_db(char *db_pathname, char *output_path) {
> +rmc_meta_header_t meta_header;
> +rmc_db_header_t *db_header = NULL;
> +rmc_record_header_t record_header;
> +rmc_uint64_t record_idx = 0;   /* offset of each reacord in db*/
> +rmc_uint64_t meta_idx = 0; /* offset of each meta in a record */
> +rmc_uint64_t file_idx = 0; /* offset of file in a meta */
> +rmc_file_t file;
> +char *out_dir = NULL, *out_name = NULL, *cmd = NULL, *tmp_dir_name = 
> NULL;
> +rmc_size_t db_len = 0;
> +rmc_uint8_t *rmc_db = NULL;
> +DIR *tmp_dir = NULL;
> +
> +if 

Re: [yocto] [PATCH v2 4/5] rmc: remove unnecessary return variable

[Jianxun Zhang]

Nice. Review +1

> On Feb 9, 2017, at 11:17 AM, Todor Minchev  
> wrote:
> 
> Signed-off-by: Todor Minchev 
> ---
> src/rmc.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/src/rmc.c b/src/rmc.c
> index f3a2a5e..b5c7847 100644
> --- a/src/rmc.c
> +++ b/src/rmc.c
> @@ -218,7 +218,6 @@ read_fp_done:
> static rmc_file_t *read_policy_file(char *pathname, int type) {
> rmc_file_t *tmp = NULL;
> rmc_size_t policy_len = 0;
> -int ret;
> char *path_token;
> 
> if ((tmp = calloc(1, sizeof(rmc_file_t))) == NULL) {
> @@ -230,8 +229,7 @@ static rmc_file_t *read_policy_file(char *pathname, int 
> type) {
> tmp->next = NULL;
> 
> if (type == RMC_GENERIC_FILE) {
> -ret = read_file(pathname, (char **)>blob, _len);
> -if (ret) {
> +if (read_file(pathname, (char **)>blob, _len)) {
> fprintf(stderr, "Failed to read file %s\n\n", pathname);
> free(tmp);
> return NULL;
> -- 
> 2.11.1
> 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH v2 3/5] rmc: Enable reading the contents of an existing fingerprint file

[Jianxun Zhang]

> On Feb 9, 2017, at 11:17 AM, Todor Minchev  
> wrote:
> 
> The contents of an existing fingerprint file can be read and output on
> the command line with the following options:
> 
> rmc -E -f input_fingerprint_file
> 
> Signed-off-by: Todor Minchev 
> ---
> src/rmc.c | 98 ++-
> 1 file changed, 65 insertions(+), 33 deletions(-)
> 
> diff --git a/src/rmc.c b/src/rmc.c
> index 062dd36..f3a2a5e 100644
> --- a/src/rmc.c
> +++ b/src/rmc.c
> @@ -14,43 +14,47 @@
> #include 
> 
> #define USAGE "RMC (Runtime Machine configuration) Tool\n" \
> -"NOTE: Most of usages require root permission (sudo)\n" \
> +"NOTE: Most of usages require root permission (sudo)\n\n" \
> "rmc -F [-o output_fingerprint]\n" \
> "rmc -R [-f ] -b  [-o output_record]\n" 
> \
> "rmc -D  [-o output_database]\n" \
> - "rmc -B  -d  -o output_file\n" \
> - "\n" \
> - "-F: generate board rmc fingerprint of board\n" \
> - "-R: generate board rmc record of board with its fingerprint and file 
> blobs.\n" \
> -"-f: fingerprint file to be packed in record, rmc will create a 
> fingerprint for board and use it internally to\n" \
> -"generate record if -f is missed.\n" \
> -"-b: files to be packed in record\n" \
> - "-G: generate rmc database file with records specified in record file 
> list\n" \
> - "-B: get a flie blob with specified name associated to the board rmc is 
> running on\n" \
> - "-d: database file to be queried\n" \
> - "-o: path and name of output file of a specific command\n" \
> - "\n" \
> -"Examples (Steps in an order to add board support into rmc):\n" \
> -"generate board fingerprint:\n" \
> -"rmc -F\n\n" \
> -"generate a rmc record for the board with two file blobs, output to:\n" \
> -"a specified file:\n" \
> -"rmc -R -f fingerprint -b file_1 file_2 -o my_board.record\n\n" \
> -"generate a rmc database file with records from 3 different boards:\n" \
> -"rmc -D board1_record board2_record board3_record\n\n" \
> -"query a file blob named audio.conf associated to the board rmc is 
> running on in database my_rmc.db and output\n" \
> -"to /tmp/new_audio.conf:\n" \
> -"rmc -B audio.conf -d my_rmc.db -o /tmp/new_audio.conf\n\n"
> +"rmc -B  -d  -o output_file\n\n" \
> +  "-F: manage fingerprint file\n" \
> +"\t-o output_file: store RMC fingerprint of current board in 
> output_file\n" \
> +  "-R: generate board rmc record of board with its fingerprint and file 
> blobs.\n" \
> +"\t-f intput_file : input fingerprint file to be packed in record\n\n" \
> +"\tNOTE: RMC will create a fingerprint for the board and use it to\n" \
> +"\tgenerate record if an input fingerprint file is not provided.\n\n" \
> +"\t-b: files to be packed in record\n\n" \
> +  "-G: generate rmc database file with records specified in record file 
> list\n\n" \
> +  "-B: get a file blob with specified name associated to the board rmc is\n" 
> \
> +  "running on\n" \
> +"\t-d: database file to be queried\n" \
> +"\t-o: path and name of output file of a specific command\n\n" \
> +  "-E: Extract data from fingerprint file and print it to terminal\n" \
> +"\t-f: fingerprint file to extract\n\n" \
> +"Examples (Steps in an order to add board support into rmc):\n\n" \
> +"1. Generate board fingerprint:\n" \
> +"\trmc -F\n\n" \
> +"2. Generate a rmc record for the board with two file blobs and save 
> it\n" \
> +"to a specified file:\n" \
> +"\trmc -R -f fingerprint -b file_1 file_2 -o my_board.record\n\n" \
> +"3. Generate a rmc database file with records from 3 different 
> boards:\n" \
> +"\trmc -D board1_record board2_record board3_record\n\n" \
> +"4. Query a file blob named audio.conf associated to the board rmc is\n" 
> \
> +"running on in database my_rmc.db and output to /tmp/new_audio.conf:\n" \
> +"\trmc -B audio.conf -d my_rmc.db -o /tmp/new_audio.conf\n\n"
> 
> 
> #define RMC_OPT_CAP_F   (1 << 0)
> #define RMC_OPT_CAP_R   (1 << 1)
> #define RMC_OPT_CAP_D   (1 << 2)
> #define RMC_OPT_CAP_B   (1 << 3)
> -#define RMC_OPT_F   (1 << 4)
> -#define RMC_OPT_O   (1 << 5)
> -#define RMC_OPT_B   (1 << 6)
> -#define RMC_OPT_D   (1 << 7)
> +#define RMC_OPT_CAP_E   (1 << 4)
> +#define RMC_OPT_F   (1 << 5)
> +#define RMC_OPT_O   (1 << 6)
> +#define RMC_OPT_B   (1 << 7)
> +#define RMC_OPT_D   (1 << 8)
> 
> static void usage () {
> fprintf(stdout, USAGE);
> @@ -78,7 +82,7 @@ static void dump_fingerprint(rmc_fingerprint_t *fp) {
> static int write_fingerprint_file(const char* pathname, rmc_fingerprint_t 
> *fp) {
> int i;
> int first = 0;
> -
> +/* TODO - do we need to open/close file multiple times to write each 
> field */
> for (i = 0; i < RMC_FINGER_NUM; i++) {
> if (write_file(pathname, 

Re: [yocto] [PATCH v2 2/5] Makefile: add debug target

[Jianxun Zhang]

> On Feb 9, 2017, at 11:17 AM, Todor Minchev  
> wrote:
> 
> A debug version of the rmc binary can be built by using the debug
> Makefile target. This will include debug symbols and will disable
> compiler optimizations.
> 
> Example:
> 
> make debug
> 
> Signed-off-by: Todor Minchev 
> ---
> Makefile | 2 ++
> 1 file changed, 2 insertions(+)
> 
> diff --git a/Makefile b/Makefile
> index c58047a..fdd936f 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -23,6 +23,8 @@ ALL_OBJS := $(RMC_TOOL_OBJ) $(RMC_LIB_OBJ)
> RMC_CFLAGS := -Wall -I$(TOPDIR)/inc
> 
> all: rmc
> +debug: RMC_CFLAGS += -DDEBUG -g -O0
> +debug: rmc
> 
I missed your feedback of V1, just recap it here also with my comment:

- "Yup, the above will have the same effect as 'make debug'.
I thought that 'make debug' might be a convenient way to build a debug
binary? Do you think it makes sense to keep this extra target for
convenience since it doesn't affect the other usages of make?"

You could have to come back to CFLAGS when the a hard coded debug flags is not 
enough.

And, why pass -DDEBUG in RMC_CFLAGS when invoking gcc to compile rmc? I don’t 
see this macro DEBUG in the current rmc code.

Thanks
> $(ALL_OBJS): %.o: %.c
>   $(CC) -c $(CFLAGS) $(RMC_CFLAGS) $< -o $@
> -- 
> 2.11.1
> 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH v2 1/5] Makefile: disable silent mode in Makefiles

[Jianxun Zhang]

Review +1,
Thanks to address my comment

> On Feb 9, 2017, at 11:17 AM, Todor Minchev  
> wrote:
> 
> By default make will output the commands that are executed for each
> target. Silent mode can be enabled with the '-s' option.
> 
> Example:
> make -s
> 
> Signed-off-by: Todor Minchev 
> ---
> Makefile | 21 +++--
> Makefile.efi | 10 +-
> 2 files changed, 16 insertions(+), 15 deletions(-)
> 
> diff --git a/Makefile b/Makefile
> index 9ade775..c58047a 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -25,23 +25,24 @@ RMC_CFLAGS := -Wall -I$(TOPDIR)/inc
> all: rmc
> 
> $(ALL_OBJS): %.o: %.c
> - @$(CC) -c $(CFLAGS) $(RMC_CFLAGS) $< -o $@
> + $(CC) -c $(CFLAGS) $(RMC_CFLAGS) $< -o $@
> 
> librmc: $(RMC_LIB_OBJ)
> - @$(AR) rcs src/lib/$@.a $^
> + $(AR) rcs src/lib/$@.a $^
> 
> rmc: $(RMC_TOOL_OBJ) librmc
> - @$(CC) $(CFLAGS) $(RMC_CFLAGS) -Lsrc/lib/ -lrmc $(RMC_TOOL_OBJ) 
> src/lib/librmc.a -o src/$@
> + $(CC) $(CFLAGS) $(RMC_CFLAGS) -Lsrc/lib/ -lrmc $(RMC_TOOL_OBJ) \
> +  src/lib/librmc.a -o src/$@
> 
> clean:
> - @rm -f $(ALL_OBJS) src/rmc src/lib/librmc.a
> + rm -f $(ALL_OBJS) src/rmc src/lib/librmc.a
> 
> .PHONY: clean rmc librmc
> 
> install:
> - @mkdir -p $(RMC_INSTALL_BIN_PATH)
> - @install -m 755 src/rmc $(RMC_INSTALL_BIN_PATH)
> - @mkdir -p $(RMC_INSTALL_LIB_PATH)
> - @install -m 644 src/lib/librmc.a $(RMC_INSTALL_LIB_PATH)
> - @mkdir -p $(RMC_INSTALL_HEADER_PATH)
> - @install -m 644 $(RMC_INSTALL_HEADERS) $(RMC_INSTALL_HEADER_PATH)
> + mkdir -p $(RMC_INSTALL_BIN_PATH)
> + install -m 755 src/rmc $(RMC_INSTALL_BIN_PATH)
> + mkdir -p $(RMC_INSTALL_LIB_PATH)
> + install -m 644 src/lib/librmc.a $(RMC_INSTALL_LIB_PATH)
> + mkdir -p $(RMC_INSTALL_HEADER_PATH)
> + install -m 644 $(RMC_INSTALL_HEADERS) $(RMC_INSTALL_HEADER_PATH)
> diff --git a/Makefile.efi b/Makefile.efi
> index 3bd417d..66081d7 100644
> --- a/Makefile.efi
> +++ b/Makefile.efi
> @@ -18,16 +18,16 @@ RMC_CFLAGS := -DRMC_EFI -Wall -I$(TOPDIR)/inc -fpic 
> -nostdinc -nostdlib  -fno-bu
> all: librmcefi
> 
> $(RMC_LIB_OBJ): %.efi.o: %.c
> - @$(CC) -c $(CFLAGS) $(RMC_CFLAGS) $< -o $@
> + $(CC) -c $(CFLAGS) $(RMC_CFLAGS) $< -o $@
> 
> librmcefi: $(RMC_LIB_OBJ)
> - @$(AR) rcs src/lib/$@.a $^
> + $(AR) rcs src/lib/$@.a $^
> 
> clean:
> - @rm -f $(RMC_LIB_OBJ) src/lib/librmcefi.a
> + rm -f $(RMC_LIB_OBJ) src/lib/librmcefi.a
> 
> .PHONY: clean librmcefi
> 
> install:
> - @mkdir -p $(RMC_INSTALL_LIB_PATH)
> - @install -m 644 $(RMC_INSTALL_LIBS) $(RMC_INSTALL_LIB_PATH)
> + mkdir -p $(RMC_INSTALL_LIB_PATH)
> + install -m 644 $(RMC_INSTALL_LIBS) $(RMC_INSTALL_LIB_PATH)
> -- 
> 2.11.1
> 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] poky: core-image-minimal cannot login

[Khem Raj]

On 2/9/17 4:23 AM, Belal Hassan wrote:
> 
> Hi,
> 
> I have error when i try to login as root this message is appear login
> can't set groups: operation not permitted. Could you help me.
> 
> I target zynq7 zc702 and i use master meta-xilinx
> 

what kernel version are you on. and what release are you building.
I think you are an old kernel which needs certain backports from upstream

> Thanks,
> Belal Mohamed
> 
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [patchwork][PATCH] parsemail: Split PATCH prefix if not single

[Jose Lamego]

PATCH prefix is not appropriately identified as such if it is not
sepparated from following word in an email Subject line. This leads to
wrong email parsing and revisions not appended to initial series.

This change allows appropriate email parsing by checking if PATCH prefix
in Subject line is not sepparated from following word and adding a space
 between them.

[YOCTO #10823]

Signed-off-by: Jose Lamego 
---
 patchwork/bin/parsemail.py | 7 +++
 1 file changed, 7 insertions(+)

diff --git a/patchwork/bin/parsemail.py b/patchwork/bin/parsemail.py
index c9eb05c..6e13beb 100755
--- a/patchwork/bin/parsemail.py
+++ b/patchwork/bin/parsemail.py
@@ -578,11 +578,18 @@ def find_patch_for_comment(project, refs):
 
 
 split_re = re.compile(r'[,\s]+')
+patch_pref = re.re.compile(r'^.*\[(\s*PATCH\w+).*', re.I)
 
 
 def split_prefixes(prefix):
 """ Turn a prefix string into a list of prefix tokens """
 
+# Check if PATCH prefix is followed by anoter word without a sepparation
+# space. Add missing space to allow appropriate parsing
+if patch_pref.match(prefix):
+index = prefix.find(patch_pref.match(prefix).group(1))
+prefix = prefix[:index + 5] + ' ' + prefix[index + 5:]
+
 matches = split_re.split(prefix)
 return [s for s in matches if s != '']
 
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] ld: cannot find -lgcc in glibc 2.24-r0

[winfried . dobbe]

This problem occur when bitbake core-image-minimal-dev or bitbake
core-image-minimal-dev -c populate_sdk but only for glibc



Did you override variable SDKPATH ? I had the exact same issue last week 
when I tried to include ${TUNE_PKGARCH} in the SDKPATH variable. After 
setting SDKPATH to a simpler value the problem disappeared.


regards,
Winfried
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] intel cpu apollo lake support qusetion

[Wold, Saul]

On Fri, 2017-02-10 at 17:44 +0800, ryan.hsu(許文政) wrote:
> Hi
>  
> Does Yocto 2.2 or other release version support intel Apollo lake ?
>  
Yocto Project 2.2 along with the meta-intel does support Apollo Lake
with the 4.8 kernel.  For the upcoming 2.3 release the 4.9 kernel has
additional support. 

The meta-intel layer (for 2.3) will also have a new linux-intel-4.9
kernel with full support.

Sau!
Meta-Intel Maintainer

> Best Regards,
>  
> Ryan Hsu
> Axiomtek Co., Ltd.
> Software and Solution Division
> TEL: +886-2-2917-4550 ext.7695
> www.axiomtek.com
> 
> A Milestone of Leadership: Axiomtek
> Turns 25
>  
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] ld: cannot find -lgcc in glibc 2.24-r0

[Florian Wulff]

Dear Yocto team,

I have an issues building and linked the glibc (2.24-r0) with Morty Yocto 2.2
It can not find the libgcc -lgcc, but gcc and gcc-multilib are installed in 
/usr/lib/gcc

This problem occur when bitbake core-image-minimal-dev or bitbake 
core-image-minimal-dev -c populate_sdk but only for glibc

How and where can I specify the path for gcc_lib or LIBRARY_PATH or LDFLAGS etc.
Thank you very much

BR Florian

| x86_64-poky-linux-gcc  -m64 -march=corei7 -mtune=corei7 -mfpmath=sse -msse4.2 
--sysroot=/home/developer/yocto/Poky/build/tmp/sysroots/kontron-kbox-a103-tcbootstrap
   -nostdlib -nostartfiles -r -o 
/home/developer/yocto/Poky/build/tmp/work/corei7-64-poky-linux/glibc/2.24-r0/build-x86_64-poky-linux/libc_pic.os
 \
|  -Wl,-d -Wl,--whole-archive 
/home/developer/yocto/Poky/build/tmp/work/corei7-64-poky-linux/glibc/2.24-r0/build-x86_64-poky-linux/libc_pic.a
 -o 
/home/developer/yocto/Poky/build/tmp/work/corei7-64-poky-linux/glibc/2.24-r0/build-x86_64-poky-linux/libc_pic.os
| x86_64-poky-linux-gcc  -m64 -march=corei7 -mtune=corei7 -mfpmath=sse -msse4.2 
--sysroot=/home/developer/yocto/Poky/build/tmp/sysroots/kontron-kbox-a103-tcbootstrap
   -nostdlib -nostartfiles -r -o 
/home/developer/yocto/Poky/build/tmp/work/corei7-64-poky-linux/glibc/2.24-r0/build-x86_64-poky-linux/elf/librtld.map.o
 '-Wl,-(' 
/home/developer/yocto/Poky/build/tmp/work/corei7-64-poky-linux/glibc/2.24-r0/build-x86_64-poky-linux/elf/dl-allobjs.os
 
/home/developer/yocto/Poky/build/tmp/work/corei7-64-poky-linux/glibc/2.24-r0/build-x86_64-poky-linux/libc_pic.a
 -lgcc '-Wl,-)' 
-Wl,-Map,/home/developer/yocto/Poky/build/tmp/work/corei7-64-poky-linux/glibc/2.24-r0/build-x86_64-poky-linux/elf/librtld.mapT
| 
/home/developer/yocto/Poky/build/tmp/sysroots/x86_64-linux/usr/libexec/x86_64-poky-linux.gcc-cross-initial-x86_64/gcc/x86_64-poky-linux/6.2.0/ld:
 cannot find -lgcc
| collect2: error: ld returned 1 exit status
| Makefile:349: recipe for target 
'/home/developer/yocto/Poky/build/tmp/work/corei7-64-poky-linux/glibc/2.24-r0/build-x86_64-poky-linux/elf/librtld.map'
 failed
| make[2]: *** 
[/home/developer/yocto/Poky/build/tmp/work/corei7-64-poky-linux/glibc/2.24-r0/build-x86_64-poky-linux/elf/librtld.map]
 Error 1
| make[2]: *** Waiting for unfinished jobs
| make[2]: Leaving directory 
'/home/developer/yocto/Poky/build/tmp/work/corei7-64-poky-linux/glibc/2.24-r0/git/elf'
| Makefile:234: recipe for target 'elf/subdir_lib' failed
| make[1]: *** [elf/subdir_lib] Error 2
| make[1]: Leaving directory 
'/home/developer/yocto/Poky/build/tmp/work/corei7-64-poky-linux/glibc/2.24-r0/git'
| Makefile:9: recipe for target 'all' failed
| make: *** [all] Error 2
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at 
/home/developer/yocto/Poky/build/tmp/work/corei7-64-poky-linux/glibc/2.24-r0/temp/log.do_compile.106361)
ERROR: Task 
(/home/developer/yocto/Poky/meta/recipes-core/glibc/glibc_2.24.bb:do_compile) 
failed with exit code '1'
NOTE: Tasks Summary: Attempted 1258 tasks of which 1106 didn't need to be rerun 
and 1 failed.

Summary: 1 task failed:
  /home/developer/yocto/Poky/meta/recipes-core/glibc/glibc_2.24.bb:do_compile
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] QA Test Report for Yocto Project 2.3 M2 rc3

[Perez Carranza, Jose]

Hi

Here is the report for Partial QA Cycle on 2.3 M2 rc3

Full Report :  
https://wiki.yoctoproject.org/wiki/WW06_-_2017-02-03_-_Full_Test_Cycle_2.3_M2_rc3

Summary
The QA cycle for 2.3 M2 rc3 is complete, this was a partial test cycle focused 
on testimage, selftest and performance. Bug that was blocking testimage on rc1 
was resolved correctly and hence this unblocked the component to be validated 
on this release candidate. There were 3 new issues found the most important one 
is for Build Appliance images not available to test on AB, the other 2 are 
related to parselogs and a failure in specific workers for selftest; none of 
this 3 seem to be a release blocker; there were also another 4 bugs that are 
still open from previous releases. Performance measurements  were improved 
compared to M2 rc1 but are still above compared to M1, bug 10844[1] was 
reopened to keep the investigation on degradations.

Bugs

  * New

-11022 - Fail to build BA for 2.3 M2 rc3 [2]

-11013 - parselogs: Is failing on Xorg with error " FBDEV(0): mode 
"640x480" test failed " [3]

-11025 - selftest/devtool: Build mdadm failing on Centos7 and Ubuntu 
1404 [4]

  * High / M+ Not New

-10456 - X cannot launch on qemumips64 [5]

-10473 - Fail to launch custom qemu image with runqemu [6]

Full bugs Report : 
https://wiki.yoctoproject.org/wiki/WW06_-_2017-02-03_-_Full_Test_Cycle_2.3_M2_rc3#Bugs_Found_during_QA_Test

Performance
As bug 10844[1] was reopened Fedora machine is being used for debugging 
activities hence only results for Ubuntu machine are being analyzed for this 
Milestone. There were improvements on the measurements against M2 rc1, but the 
numbers are still above of the normal trend from the past releases/milestones.

 rc1 rc3%
sato   1:14:591:11:47-4.27
rootfs4:14  4:02  -4.72
rmwork 1:08:021:05:56-3.09
kernel  5:01 5:00  -0.33
eSDK3:47 3:28  -8.37

Performance Charts : 
https://wiki.yoctoproject.org/charts/perf_milestone_GDC/performance_test.html

Links


1- https://bugzilla.yoctoproject.org/show_bug.cgi?id=10844

2- https://bugzilla.yoctoproject.org/show_bug.cgi?id=11022

3- https://bugzilla.yoctoproject.org/show_bug.cgi?id=11013

4- https://bugzilla.yoctoproject.org/show_bug.cgi?id=11025

5- https://bugzilla.yoctoproject.org/show_bug.cgi?id=10456

6- https://bugzilla.yoctoproject.org/show_bug.cgi?id=10473


Regards,
José

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] poky: core-image-minimal cannot login

[Belal Hassan]

Hi,

I have error when i try to login as root this message is appear login can't
set groups: operation not permitted. Could you help me.

I target zynq7 zc702 and i use master meta-xilinx

Thanks,
Belal Mohamed
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto