[OE-core] [PATCH 5/5] mdadm: Backport and make fixes for building with gcc7
Signed-off-by: Khem Raj--- ...m-Add-Wimplicit-fallthrough-0-in-Makefile.patch | 37 ++ ...pecify-enough-length-when-write-to-buffer.patch | 75 ...rintf-with-strncpy-at-some-places-to-avoi.patch | 59 ++ ...orced-type-conversion-to-avoid-truncation.patch | 33 ++ ...d-a-comment-to-indicate-valid-fallthrough.patch | 128 + meta/recipes-extended/mdadm/mdadm_4.0.bb | 5 + 6 files changed, 337 insertions(+) create mode 100644 meta/recipes-extended/mdadm/files/0001-mdadm-Add-Wimplicit-fallthrough-0-in-Makefile.patch create mode 100644 meta/recipes-extended/mdadm/files/0002-mdadm-Specify-enough-length-when-write-to-buffer.patch create mode 100644 meta/recipes-extended/mdadm/files/0003-Replace-snprintf-with-strncpy-at-some-places-to-avoi.patch create mode 100644 meta/recipes-extended/mdadm/files/0004-mdadm-Forced-type-conversion-to-avoid-truncation.patch create mode 100644 meta/recipes-extended/mdadm/files/0005-Add-a-comment-to-indicate-valid-fallthrough.patch diff --git a/meta/recipes-extended/mdadm/files/0001-mdadm-Add-Wimplicit-fallthrough-0-in-Makefile.patch b/meta/recipes-extended/mdadm/files/0001-mdadm-Add-Wimplicit-fallthrough-0-in-Makefile.patch new file mode 100644 index 000..ce15170c758 --- /dev/null +++ b/meta/recipes-extended/mdadm/files/0001-mdadm-Add-Wimplicit-fallthrough-0-in-Makefile.patch @@ -0,0 +1,37 @@ +From aa09af0fe2ec0737fa04ffd00957532684e257b9 Mon Sep 17 00:00:00 2001 +From: Xiao Ni +Date: Fri, 17 Mar 2017 19:55:42 +0800 +Subject: [PATCH 1/5] mdadm: Add Wimplicit-fallthrough=0 in Makefile + +There are many errors like 'error: this statement may fall through'. +But the logic is right. So add the flag Wimplicit-fallthrough=0 +to disable the error messages. The method I use is from +https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html +#index-Wimplicit-fallthrough-375 + +Signed-off-by: Xiao Ni +Signed-off-by: Jes Sorensen +--- +Upstream-Status: Backport + Makefile | 5 + + 1 file changed, 5 insertions(+) + +diff --git a/Makefile b/Makefile +index 0f307ec..e1a7058 100644 +--- a/Makefile b/Makefile +@@ -48,6 +48,11 @@ ifdef WARN_UNUSED + CWFLAGS += -Wp,-D_FORTIFY_SOURCE=2 -O3 + endif + ++FALLTHROUGH := $(shell gcc -v --help 2>&1 | grep "implicit-fallthrough" | wc -l) ++ifneq "$(FALLTHROUGH)" "0" ++CWFLAGS += -Wimplicit-fallthrough=0 ++endif ++ + ifdef DEBIAN + CPPFLAGS += -DDEBIAN + endif +-- +2.12.2 + diff --git a/meta/recipes-extended/mdadm/files/0002-mdadm-Specify-enough-length-when-write-to-buffer.patch b/meta/recipes-extended/mdadm/files/0002-mdadm-Specify-enough-length-when-write-to-buffer.patch new file mode 100644 index 000..cbce053a3ae --- /dev/null +++ b/meta/recipes-extended/mdadm/files/0002-mdadm-Specify-enough-length-when-write-to-buffer.patch @@ -0,0 +1,75 @@ +From bb4df273041ba206008bdb0ada75ccd97c29f623 Mon Sep 17 00:00:00 2001 +From: Xiao Ni +Date: Fri, 17 Mar 2017 19:55:43 +0800 +Subject: [PATCH 2/5] mdadm: Specify enough length when write to buffer +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +In Detail.c the buffer path in function Detail is defined as path[200], +in fact the max lenth of content which needs to write to the buffer is +287. Because the length of dname of struct dirent is 255. +During building it reports error: +error: ‘%s’ directive writing up to 255 bytes into a region of size 189 +[-Werror=format-overflow=] + +In function examine_super0 there is a buffer nb with length 5. +But it need to show a int type argument. The lenght of max +number of int is 10. So the buffer length should be 11. + +In human_size function the length of buf is 30. During building +there is a error: +output between 20 and 47 bytes into a destination of size 30. +Change the length to 47. + +Signed-off-by: Xiao Ni +Signed-off-by: Jes Sorensen +--- +Upstream-Status: Backport + Detail.c | 2 +- + super0.c | 2 +- + util.c | 2 +- + 3 files changed, 3 insertions(+), 3 deletions(-) + +diff --git a/Detail.c b/Detail.c +index 509b0d4..cb33794 100644 +--- a/Detail.c b/Detail.c +@@ -575,7 +575,7 @@ This is pretty boring + printf(" Member Arrays :"); + + while (dir && (de = readdir(dir)) != NULL) { +- char path[200]; ++ char path[287]; + char vbuf[1024]; + int nlen = strlen(sra->sys_name); + dev_t devid; +diff --git a/super0.c b/super0.c +index 938cfd9..f5b4507 100644 +--- a/super0.c b/super0.c +@@ -231,7 +231,7 @@ static void examine_super0(struct supertype *st, char *homehost) +d++) { + mdp_disk_t *dp; + char *dv; +- char nb[5]; ++
[OE-core] [PATCH 4/5] aspell: Fix build with gcc7
Signed-off-by: Khem Raj--- meta/recipes-support/aspell/aspell/gcc7.patch | 40 ++ meta/recipes-support/aspell/aspell_0.60.6.1.bb | 4 ++- 2 files changed, 43 insertions(+), 1 deletion(-) create mode 100644 meta/recipes-support/aspell/aspell/gcc7.patch diff --git a/meta/recipes-support/aspell/aspell/gcc7.patch b/meta/recipes-support/aspell/aspell/gcc7.patch new file mode 100644 index 000..6ffd0772fa1 --- /dev/null +++ b/meta/recipes-support/aspell/aspell/gcc7.patch @@ -0,0 +1,40 @@ +From 8089fa02122fed0a6394eba14bbedcb1d18e2384 Mon Sep 17 00:00:00 2001 +From: Kevin Atkinson +Date: Thu, 29 Dec 2016 00:50:31 -0500 +Subject: [PATCH] Compile Fixes for GCC 7. + +Closes #519. +--- +Signed-off-by: Khem Raj +Upstream-Status: Backport + + modules/filter/tex.cpp | 2 +- + prog/check_funs.cpp| 2 +- + 2 files changed, 2 insertions(+), 2 deletions(-) + +diff --git a/modules/filter/tex.cpp b/modules/filter/tex.cpp +index a979539..19ab63c 100644 +--- a/modules/filter/tex.cpp b/modules/filter/tex.cpp +@@ -174,7 +174,7 @@ namespace { + + if (c == '{') { + +- if (top.in_what == Parm || top.in_what == Opt || top.do_check == '\0') ++ if (top.in_what == Parm || top.in_what == Opt || *top.do_check == '\0') + push_command(Parm); + + top.in_what = Parm; +diff --git a/prog/check_funs.cpp b/prog/check_funs.cpp +index db54f3d..89ee09d 100644 +--- a/prog/check_funs.cpp b/prog/check_funs.cpp +@@ -647,7 +647,7 @@ static void print_truncate(FILE * out, const char * word, int width) { + } + } + if (i == width-1) { +-if (word == '\0') ++if (*word == '\0') + put(out,' '); + else if (word[len] == '\0') + put(out, word, len); diff --git a/meta/recipes-support/aspell/aspell_0.60.6.1.bb b/meta/recipes-support/aspell/aspell_0.60.6.1.bb index 5a23754b74b..19a7155d66a 100644 --- a/meta/recipes-support/aspell/aspell_0.60.6.1.bb +++ b/meta/recipes-support/aspell/aspell_0.60.6.1.bb @@ -6,7 +6,9 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=7fbc338309ac38fefcd64b04bb903e34" PR = "r1" -SRC_URI = "${GNU_MIRROR}/aspell/aspell-${PV}.tar.gz" +SRC_URI = "${GNU_MIRROR}/aspell/aspell-${PV}.tar.gz \ + file://gcc7.patch \ + " SRC_URI[md5sum] = "e66a9c9af6a60dc46134fdacf6ce97d7" SRC_URI[sha256sum] = "f52583a83a63633701c5f71db3dc40aab87b7f76b29723aeb27941eff42df6e1" -- 2.12.2 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 2/5] json-c: Upgrade to 0.12.1 release
Backport fix for gcc7 warning along the way Signed-off-by: Khem Raj--- ...-FALLTHRU-comment-to-handle-GCC7-warnings.patch | 74 ++ .../0001-Link-against-libm-when-needed.patch | 53 .../0001-json_tokener-requires-INF-and-NAN.patch | 37 --- .../json-c/{json-c_0.12.bb => json-c_0.12.1.bb}| 18 +++--- 4 files changed, 83 insertions(+), 99 deletions(-) create mode 100644 meta/recipes-devtools/json-c/json-c/0001-Add-FALLTHRU-comment-to-handle-GCC7-warnings.patch delete mode 100644 meta/recipes-devtools/json-c/json-c/0001-Link-against-libm-when-needed.patch delete mode 100644 meta/recipes-devtools/json-c/json-c/0001-json_tokener-requires-INF-and-NAN.patch rename meta/recipes-devtools/json-c/{json-c_0.12.bb => json-c_0.12.1.bb} (70%) diff --git a/meta/recipes-devtools/json-c/json-c/0001-Add-FALLTHRU-comment-to-handle-GCC7-warnings.patch b/meta/recipes-devtools/json-c/json-c/0001-Add-FALLTHRU-comment-to-handle-GCC7-warnings.patch new file mode 100644 index 000..537be5e6d29 --- /dev/null +++ b/meta/recipes-devtools/json-c/json-c/0001-Add-FALLTHRU-comment-to-handle-GCC7-warnings.patch @@ -0,0 +1,74 @@ +From 7b24f8bd95ad4f7d00c93ca2ad998c14a0266dbe Mon Sep 17 00:00:00 2001 +From: marxin +Date: Tue, 21 Mar 2017 08:42:11 +0100 +Subject: [PATCH] Add FALLTHRU comment to handle GCC7 warnings. + +--- +Upstream-Status: Backport +Signed-off-by: Khem Raj + + json_object.c | 1 + + json_tokener.c | 1 + + linkhash.c | 22 +++--- + 3 files changed, 13 insertions(+), 11 deletions(-) + +diff --git a/json_object.c b/json_object.c +index 6cc73bc..77e8b21 100644 +--- a/json_object.c b/json_object.c +@@ -552,6 +552,7 @@ int64_t json_object_get_int64(struct json_object *jso) + return jso->o.c_boolean; + case json_type_string: + if (json_parse_int64(jso->o.c_string.str, ) == 0) return cint; ++ /* FALLTHRU */ + default: + return 0; + } +diff --git a/json_tokener.c b/json_tokener.c +index 9a76293..ae7b1ae 100644 +--- a/json_tokener.c b/json_tokener.c +@@ -305,6 +305,7 @@ struct json_object* json_tokener_parse_ex(struct json_tokener *tok, + tok->err = json_tokener_error_parse_unexpected; + goto out; + } ++ /* FALLTHRU */ + case '"': + state = json_tokener_state_string; + printbuf_reset(tok->pb); +diff --git a/linkhash.c b/linkhash.c +index 712c387..74e3b0f 100644 +--- a/linkhash.c b/linkhash.c +@@ -376,17 +376,17 @@ static uint32_t hashlittle( const void *key, size_t length, uint32_t initval) + /* last block: affect all 32 bits of (c) */ + switch(length) /* all the case statements fall through */ + { +-case 12: c+=((uint32_t)k[11])<<24; +-case 11: c+=((uint32_t)k[10])<<16; +-case 10: c+=((uint32_t)k[9])<<8; +-case 9 : c+=k[8]; +-case 8 : b+=((uint32_t)k[7])<<24; +-case 7 : b+=((uint32_t)k[6])<<16; +-case 6 : b+=((uint32_t)k[5])<<8; +-case 5 : b+=k[4]; +-case 4 : a+=((uint32_t)k[3])<<24; +-case 3 : a+=((uint32_t)k[2])<<16; +-case 2 : a+=((uint32_t)k[1])<<8; ++case 12: c+=((uint32_t)k[11])<<24; /* FALLTHRU */ ++case 11: c+=((uint32_t)k[10])<<16; /* FALLTHRU */ ++case 10: c+=((uint32_t)k[9])<<8; /* FALLTHRU */ ++case 9 : c+=k[8]; /* FALLTHRU */ ++case 8 : b+=((uint32_t)k[7])<<24; /* FALLTHRU */ ++case 7 : b+=((uint32_t)k[6])<<16; /* FALLTHRU */ ++case 6 : b+=((uint32_t)k[5])<<8; /* FALLTHRU */ ++case 5 : b+=k[4]; /* FALLTHRU */ ++case 4 : a+=((uint32_t)k[3])<<24; /* FALLTHRU */ ++case 3 : a+=((uint32_t)k[2])<<16; /* FALLTHRU */ ++case 2 : a+=((uint32_t)k[1])<<8; /* FALLTHRU */ + case 1 : a+=k[0]; + break; + case 0 : return c; +-- +2.12.2 + diff --git a/meta/recipes-devtools/json-c/json-c/0001-Link-against-libm-when-needed.patch b/meta/recipes-devtools/json-c/json-c/0001-Link-against-libm-when-needed.patch deleted file mode 100644 index bfe9d723135..000 --- a/meta/recipes-devtools/json-c/json-c/0001-Link-against-libm-when-needed.patch +++ /dev/null @@ -1,53 +0,0 @@ -From 93582ad85ef48c18ac12f00a9a9e124989b1fcab Mon Sep 17 00:00:00 2001 -From: Thomas Petazzoni -Date: Fri, 1 May 2015 12:52:18 +0200 -Subject: [PATCH] Link against libm when needed - -In certain C libraries (e.g uClibc), isnan() and related functions are -implemented in libm, so json-c needs to link against it. This commit -therefore adds an AC_TRY_LINK() test to check whether a program -calling isnan() can be properly linked with no special flags. If not, -we assume linking against libm is needed. - -The json-c.pc.in file is also adjusted so that in the case of static -linking against json-c, -lm is also used. - -Signed-off-by: Thomas Petazzoni -Upstream-Status:
[OE-core] [PATCH 3/5] pax: Fix build with gcc7
Signed-off-by: Khem Raj--- .../pax/0001-Add-a-comment-for-fallthrough.patch | 38 ++ meta/recipes-extended/pax/pax_3.4.bb | 9 ++--- 2 files changed, 43 insertions(+), 4 deletions(-) create mode 100644 meta/recipes-extended/pax/pax/0001-Add-a-comment-for-fallthrough.patch diff --git a/meta/recipes-extended/pax/pax/0001-Add-a-comment-for-fallthrough.patch b/meta/recipes-extended/pax/pax/0001-Add-a-comment-for-fallthrough.patch new file mode 100644 index 000..b76f85aa458 --- /dev/null +++ b/meta/recipes-extended/pax/pax/0001-Add-a-comment-for-fallthrough.patch @@ -0,0 +1,38 @@ +From e67bb3debe582f0e0b714bd012bb1082fc41 Mon Sep 17 00:00:00 2001 +From: Khem Raj +Date: Wed, 19 Apr 2017 11:32:00 -0700 +Subject: [PATCH] Add a comment for fallthrough + +Fixes warnings with gcc7 e.g. + +../../../../../../../workspace/sources/pax/src/options.c: In function 'tar_options': +../../../../../../../workspace/sources/pax/src/options.c:725:7: error: this statement may fall through [-Werror=implicit-fallthrough=] +if (opt_add ("write_opt=nodir") < 0) + ^ +../../../../../../../workspace/sources/pax/src/options.c:730:2: note: here + case 'O': + ^~~~ +cc1: all warnings being treated as errors + +Upstream-Status: Pending + +Signed-off-by: Khem Raj +--- + src/options.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/src/options.c b/src/options.c +index c663b4e..b80819a 100644 +--- a/src/options.c b/src/options.c +@@ -724,6 +724,7 @@ tar_options (int argc, char **argv) + case 'o': + if (opt_add ("write_opt=nodir") < 0) + tar_usage (); ++/* fallthru */ + case 'O': + Oflag = 1; + break; +-- +2.12.2 + diff --git a/meta/recipes-extended/pax/pax_3.4.bb b/meta/recipes-extended/pax/pax_3.4.bb index 9b4e17b3df7..6df9a8186b6 100644 --- a/meta/recipes-extended/pax/pax_3.4.bb +++ b/meta/recipes-extended/pax/pax_3.4.bb @@ -15,10 +15,11 @@ PR = "r2" DEPENDS_append_libc-musl = " fts " SRC_URI = "http://pkgs.fedoraproject.org/repo/pkgs/${BPN}/${BP}.tar.bz2/fbd9023b590b45ac3ade95870702a0d6/${BP}.tar.bz2 \ - file://fix_for_compile_with_gcc-4.6.0.patch \ - file://pax-3.4_fix_for_x32.patch \ -file://0001-include-sys-sysmacros.h-for-major-minor-definitions.patch \ -" + file://fix_for_compile_with_gcc-4.6.0.patch \ + file://pax-3.4_fix_for_x32.patch \ + file://0001-include-sys-sysmacros.h-for-major-minor-definitions.patch \ + file://0001-Add-a-comment-for-fallthrough.patch \ + " SRC_URI_append_libc-musl = " file://0001-Fix-build-with-musl.patch \ file://0001-use-strtoll-instead-of-strtoq.patch \ -- 2.12.2 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/5] nss: Update to 3.29.1
Also fix build with gcc7 along Signed-off-by: Khem Raj--- .../nss/0001-Fix-warnings-found-with-gcc7.patch| 41 ++ .../nss/{nss_3.28.1.bb => nss_3.29.1.bb} | 28 +++ 2 files changed, 55 insertions(+), 14 deletions(-) create mode 100644 meta/recipes-support/nss/nss/0001-Fix-warnings-found-with-gcc7.patch rename meta/recipes-support/nss/{nss_3.28.1.bb => nss_3.29.1.bb} (90%) diff --git a/meta/recipes-support/nss/nss/0001-Fix-warnings-found-with-gcc7.patch b/meta/recipes-support/nss/nss/0001-Fix-warnings-found-with-gcc7.patch new file mode 100644 index 000..b16fb020c1c --- /dev/null +++ b/meta/recipes-support/nss/nss/0001-Fix-warnings-found-with-gcc7.patch @@ -0,0 +1,41 @@ +From a1d2ef6a8e1bc721e44640bdb85747deaf8edcca Mon Sep 17 00:00:00 2001 +From: Khem Raj +Date: Wed, 19 Apr 2017 10:50:37 -0700 +Subject: [PATCH] Fix warnings found with gcc7 + +GCC7 finds more type conversion issues + +| pkix_pl_ocsprequest.c: In function 'pkix_pl_OcspRequest_Hashcode': +| pkix_pl_ocsprequest.c:92:60: error: '<<' in boolean context, did you mean '<' ? [-Werror=int-in-bool-context] +| *pHashcode = (extensionHash << 8) || certHash) << 8) || +| ^ +| pkix_pl_ocsprequest.c:93:27: error: '<<' in boolean context, did you mean '<' ? [-Werror=int-in-bool-context] +| *pHashcode = (extensionHash << 8) || certHash) << 8) || +| ~~ +| dateHash) << 8) || signerHash; +| ~~^ +| cc1: all warnings being treated as errors + +Upstream-Status: Pending + +Signed-off-by: Khem Raj +--- + nss/lib/libpkix/pkix_pl_nss/pki/pkix_pl_ocsprequest.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/nss/lib/libpkix/pkix_pl_nss/pki/pkix_pl_ocsprequest.c b/nss/lib/libpkix/pkix_pl_nss/pki/pkix_pl_ocsprequest.c +index 171a3d2..d5eef88 100644 +--- a/nss/lib/libpkix/pkix_pl_nss/pki/pkix_pl_ocsprequest.c b/nss/lib/libpkix/pkix_pl_nss/pki/pkix_pl_ocsprequest.c +@@ -89,7 +89,7 @@ pkix_pl_OcspRequest_Hashcode( + PKIX_HASHCODE(ocspRq->signerCert, , plContext, + PKIX_CERTHASHCODEFAILED); + +-*pHashcode = (extensionHash << 8) || certHash) << 8) || ++*pHashcode = ((PKIX_UInt32)(((PKIX_UInt32)((extensionHash << 8) || certHash) << 8) || + dateHash) << 8) || signerHash; + + cleanup: +-- +2.12.2 + diff --git a/meta/recipes-support/nss/nss_3.28.1.bb b/meta/recipes-support/nss/nss_3.29.1.bb similarity index 90% rename from meta/recipes-support/nss/nss_3.28.1.bb rename to meta/recipes-support/nss/nss_3.29.1.bb index fed86fc8e92..48db0312b10 100644 --- a/meta/recipes-support/nss/nss_3.28.1.bb +++ b/meta/recipes-support/nss/nss_3.29.1.bb @@ -14,20 +14,20 @@ LIC_FILES_CHKSUM = "file://nss/COPYING;md5=3b1e88e1b9c0b5a4b2881d46cce06a18 \ file://nss/lib/freebl/mpi/doc/LICENSE;md5=491f158d09d948466afce85d6f1fe18f \ file://nss/lib/freebl/mpi/doc/LICENSE-MPL;md5=5d425c8f3157dbf212db2ec53d9e5132" -SRC_URI = "\ - http://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_28_1_RTM/src/${BP}.tar.gz \ -file://0001-nss-fix-support-cross-compiling.patch \ -file://nss-no-rpath-for-cross-compiling.patch \ -file://nss-fix-incorrect-shebang-of-perl.patch \ -file://nss-fix-nsinstall-build.patch \ -file://disable-Wvarargs-with-clang.patch \ -file://pqg.c-ULL_addend.patch \ -file://Fix-compilation-for-X32.patch \ -file://nss.pc.in \ -file://signlibs.sh \ -" -SRC_URI[md5sum] = "e98d48435cee5792f97ef7fc35a602c3" -SRC_URI[sha256sum] = "58cc0c05c0ed9523e6d820bea74f513538f48c87aac931876e3d3775de1a82ad" +SRC_URI = "http://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_29_1_RTM/src/${BP}.tar.gz \ + file://nss.pc.in \ + file://signlibs.sh \ + file://0001-nss-fix-support-cross-compiling.patch \ + file://nss-no-rpath-for-cross-compiling.patch \ + file://nss-fix-incorrect-shebang-of-perl.patch \ + file://nss-fix-nsinstall-build.patch \ + file://disable-Wvarargs-with-clang.patch \ + file://pqg.c-ULL_addend.patch \ + file://Fix-compilation-for-X32.patch \ + file://0001-Fix-warnings-found-with-gcc7.patch \ + " +SRC_URI[md5sum] = "0525d1a45931892daa0f368d379d4aa4" +SRC_URI[sha256sum] = "47259bc5c4439d8228d7c577ea652ed140588f27eae8ebb39cc91057aea37366" UPSTREAM_CHECK_URI = "https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_Releases; UPSTREAM_CHECK_REGEX = "NSS_(?P.+)_release_notes" -- 2.12.2 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org
[OE-core] [PATCH] libepoxy: 1.4.0 -> 1.4.1
Upgrade libepoxy from 1.4.0 to 1.4.1. Signed-off-by: Huang Qiyu--- .../libepoxy/{libepoxy_1.4.0.bb => libepoxy_1.4.1.bb} | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) rename meta/recipes-graphics/libepoxy/{libepoxy_1.4.0.bb => libepoxy_1.4.1.bb} (70%) diff --git a/meta/recipes-graphics/libepoxy/libepoxy_1.4.0.bb b/meta/recipes-graphics/libepoxy/libepoxy_1.4.1.bb similarity index 70% rename from meta/recipes-graphics/libepoxy/libepoxy_1.4.0.bb rename to meta/recipes-graphics/libepoxy/libepoxy_1.4.1.bb index ee9f694..4b3f56a 100644 --- a/meta/recipes-graphics/libepoxy/libepoxy_1.4.0.bb +++ b/meta/recipes-graphics/libepoxy/libepoxy_1.4.1.bb @@ -5,9 +5,9 @@ SECTION = "libs" LICENSE = "MIT" LIC_FILES_CHKSUM = "file://COPYING;md5=58ef4c80d401e07bd9ee8b6b58cf464b" -SRC_URI = "https://github.com/anholt/${BPN}/releases/download/v1.4/${BP}.tar.xz; -SRC_URI[md5sum] = "d8d8cbf2beb64975d424fcc5167a2a38" -SRC_URI[sha256sum] = "25a906b14a921bc2b488cfeaa21a00486fe92630e4a9dd346e4ecabeae52ab41" +SRC_URI = "https://github.com/anholt/${BPN}/releases/download/${PV}/${BP}.tar.xz; +SRC_URI[md5sum] = "a0dc66910009a99c47c5def50b042d77" +SRC_URI[sha256sum] = "88c6abf5522fc29bab7d6c555fd51a855cbd9253c4315f8ea44e832baef21aa6" UPSTREAM_CHECK_URI = "https://github.com/anholt/libepoxy/releases; inherit autotools pkgconfig distro_features_check -- 2.7.4 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] ✗ patchtest: failure for busybox: fix typo in CVE-2016-2147_2.patch Upstream-Status tag
== Series Details == Series: busybox: fix typo in CVE-2016-2147_2.patch Upstream-Status tag Revision: 1 URL : https://patchwork.openembedded.org/series/6429/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures: * Patchbusybox: fix typo in CVE-2016-2147_2.patch Upstream-Status tag Issue Missing or incorrectly formatted CVE tag in commit message [test_cve_presence_in_commit_message] Suggested fixInclude a "CVE--" tag in the commit message If you believe any of these test results are incorrect, please reply to the mailing list (openembedded-core@lists.openembedded.org) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...). --- Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] busybox: fix typo in CVE-2016-2147_2.patch Upstream-Status tag
Signed-off-by: Andre McCurdy--- meta/recipes-core/busybox/busybox/CVE-2016-2147_2.patch | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-core/busybox/busybox/CVE-2016-2147_2.patch b/meta/recipes-core/busybox/busybox/CVE-2016-2147_2.patch index 1473d46..b8349c0 100644 --- a/meta/recipes-core/busybox/busybox/CVE-2016-2147_2.patch +++ b/meta/recipes-core/busybox/busybox/CVE-2016-2147_2.patch @@ -4,7 +4,7 @@ Date: Fri, 11 Mar 2016 00:26:58 +0100 Subject: [PATCH] udhcpc: fix a warning in debug code Signed-off-by: Denys Vlasenko -Upsteam-Status: Backport +Upstream-Status: Backport CVE: CVE-2016-2147 regression fix https://git.busybox.net/busybox/commit/?id=1b7c17 -- 1.9.1 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [oe] OpenEmbedded 2017 General Meeting
On 2017-04-19 06:10 PM, Trevor Woerner wrote: > Could you please use > https://www.timeanddate.com/worldclock/fixedform.html to specify the > date/time? > Never used it before. Handy. Here's a link to the time: https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+2017+General+Meeting=20170503T08=24=1 Here's a link to a countdown: :) https://www.timeanddate.com/countdown/generic?p0=24=20170503T08=OpenEmbedded%202017%20General%20Meeting I'm adding both to the wiki as well. -- Sean signature.asc Description: OpenPGP digital signature -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [oe] OpenEmbedded 2017 General Meeting
Are there no toll-free numbers that could be used, or at least more options for local area codes? -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [oe] OpenEmbedded 2017 General Meeting
Could you please use https://www.timeanddate.com/worldclock/fixedform.html to specify the date/time? -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] documentation.conf: update TCLIBC[doc] to match current options in oe-core
Signed-off-by: Andre McCurdy--- meta/conf/documentation.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/conf/documentation.conf b/meta/conf/documentation.conf index 06527cb..35b9103 100644 --- a/meta/conf/documentation.conf +++ b/meta/conf/documentation.conf @@ -415,7 +415,7 @@ TARGET_FPU[doc] = "Specifies the method for handling FPU code. For FPU-less targ TARGET_OS[doc] = "Specifies the target's operating system." TARGET_PREFIX[doc] = "The prefix for the cross-compile toolchain (e.g. arm-linux-)." TARGET_SYS[doc] = "The target system is comprised of TARGET_ARCH,TARGET_VENDOR and TARGET_OS." -TCLIBC[doc] = "Specifies GNU standard C library (libc) variant to use during the build process. You can select 'glibc' or 'uclibc'." +TCLIBC[doc] = "Specifies C library (libc) variant to use during the build process. You can select 'baremetal', 'glibc' or 'musl'." TCMODE[doc] = "Enables an external toolchain (where provided by an additional layer) if set to a value other than 'default'." TEST_IMAGE[doc] = "Enables test booting of virtual machine images under the QEMU emulator after any root filesystems are created and runs tests against those images." TEST_QEMUBOOT_TIMEOUT[doc] = "The time in seconds allowed for an image to boot before automated runtime tests begin to run against an image." -- 1.9.1 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] tclibc-musl.inc: fix stray comment reference to uclibc
Signed-off-by: Andre McCurdy--- meta/conf/distro/include/tclibc-musl.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/conf/distro/include/tclibc-musl.inc b/meta/conf/distro/include/tclibc-musl.inc index 1ddd58e..3d3f6ac 100644 --- a/meta/conf/distro/include/tclibc-musl.inc +++ b/meta/conf/distro/include/tclibc-musl.inc @@ -4,7 +4,7 @@ LIBCEXTENSION = "-musl" -# Add uclibc overrides to the overrides. +# Add musl libc overrides to the overrides. LIBCOVERRIDE = ":libc-musl" OVERRIDES .= "${LIBCOVERRIDE}" -- 1.9.1 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] curl: Add certificates dependency to curl build.
The built curl is used during the builds, and any download using an https link (e.g. from github) requires the certificates, so these must be installed before curl is available. This was breaking stb-kodi builds on openViX. (Actually, absolute links get installed, so you also need to be using a build system with the relevant certs in place but this will be true, and anyway is a separate issue). Signed-off-by: Gordon Lack--- meta/recipes-support/curl/curl_7.53.1.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-support/curl/curl_7.53.1.bb b/meta/recipes-support/curl/curl_7.53.1.bb index bc78ffb..8fc9e87 100644 --- a/meta/recipes-support/curl/curl_7.53.1.bb +++ b/meta/recipes-support/curl/curl_7.53.1.bb @@ -9,6 +9,8 @@ SRC_URI = "http://curl.haxx.se/download/curl-${PV}.tar.bz2 \ file://0001-replace-krb5-config-with-pkg-config.patch \ " +DEPENDS = "ca-certificates" + # curl likes to set -g0 in CFLAGS, so we stop it # from mucking around with debug options # -- 2.7.4 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] sstate: Ensure PACKAGE_EXTRA_ARCHS are part of SSTATE_ARCHS
On Wed, 2017-04-19 at 15:17 -0700, Saul Wold wrote: > Since BSPs also define package archs that are included in > PACKAGE_EXTRA_ARCHS > we should also enure they are accounted for in SSTATE_ARCH. > > This helps with the license manifest issue in some cases. > > Signed-off-by: Saul Wold> --- > meta/classes/sstate.bbclass | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/meta/classes/sstate.bbclass > b/meta/classes/sstate.bbclass > index e50a385..614c3a0 100644 > --- a/meta/classes/sstate.bbclass > +++ b/meta/classes/sstate.bbclass > @@ -45,6 +45,7 @@ SSTATE_ARCHS = " \ > ${SDK_ARCH}_${PACKAGE_ARCH} \ > allarch \ > ${PACKAGE_ARCH} \ > +${PACKAGE_EXTRA_ARCHS} \ > ${MACHINE}" > > SSTATE_MANMACH ?= "${SSTATE_PKGARCH}" You really need to explain more about the problem this is solving. I'm nervous of this change as it has the potential to complicate multimachine builds and hide real issues. For example, currently if you build an armv5 and an armv7 machine, the files will be left alone for both. After this change, building the armv7 machine will cause the armv5 files to be removed as they are not "reachable" from the v7 build but are listed as an extra package arch. At that point we may as well go though all index files and remove anything which isn't reachable by the current configured machine. It actually gets worse with multiconfig as with this change building an armv7 and armv5 machine would fail. If you're solving a package feed issue, the answer might be to limit the package feeds only to currently builable package architectures. I'm not sure what license issue you're addressing here though so I can't really help give pointers on what to do here... Cheers, Richard -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] sstate: Ensure PACKAGE_EXTRA_ARCHS are part of SSTATE_ARCHS
Since BSPs also define package archs that are included in PACKAGE_EXTRA_ARCHS we should also enure they are accounted for in SSTATE_ARCH. This helps with the license manifest issue in some cases. Signed-off-by: Saul Wold--- meta/classes/sstate.bbclass | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass index e50a385..614c3a0 100644 --- a/meta/classes/sstate.bbclass +++ b/meta/classes/sstate.bbclass @@ -45,6 +45,7 @@ SSTATE_ARCHS = " \ ${SDK_ARCH}_${PACKAGE_ARCH} \ allarch \ ${PACKAGE_ARCH} \ +${PACKAGE_EXTRA_ARCHS} \ ${MACHINE}" SSTATE_MANMACH ?= "${SSTATE_PKGARCH}" -- 2.7.4 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [oe] OpenEmbedded 2017 General Meeting
All - please note the time zone carefully when planning to attend. On Wed, Apr 19, 2017 at 1:48 PM, Sean Hudsonwrote: > The board would like to hold a general meeting with all members. Under > the new by-laws of the OpenEmbedded organization, we can meet > electronically. This will also fulfill the requirement for an annual, > general meeting. > > Planned Date/Time: > Wednesday, May 3rd, at 8am US-CDT(UTC-06:00)/3pm CET(UTC+01:00) > > Wiki page with full details, including teleconference information here: > http://www.openembedded.org/wiki/2017_General_Meeting > > Please take a moment to add your name to the list if you are planning to > attend and any agenda items you would like to discuss. > > -- > Sean > > > -- > ___ > Openembedded-devel mailing list > openembedded-de...@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-devel > > -- Jeff Osier-Mixon - Open Source Community Engineer, Intel Corporation -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] cmake.bbclass: Do not use bitbake variable syntax for shell variables
Using bitbake variable syntax (i.e., ${FOO}) for shell variables is bad practice. First of all it is confusing, but more importantly it can lead to weird problems if someone actually defines a bitbake variable with the same name as the shell variable. Also use lower case for local shell variables. Signed-off-by: Peter Kjellerstedt--- meta/classes/cmake.bbclass | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/meta/classes/cmake.bbclass b/meta/classes/cmake.bbclass index 3f670919a8..20d8a61069 100644 --- a/meta/classes/cmake.bbclass +++ b/meta/classes/cmake.bbclass @@ -43,12 +43,12 @@ def map_target_arch_to_uname_arch(target_arch): cmake_do_generate_toolchain_file() { if [ "${BUILD_SYS}" = "${HOST_SYS}" ]; then - CMAKE_CROSSCOMPILING="set( CMAKE_CROSSCOMPILING FALSE )" + cmake_crosscompiling="set( CMAKE_CROSSCOMPILING FALSE )" fi cat > ${WORKDIR}/toolchain.cmake
[OE-core] [PATCH 2/2] kexec-tools: Add again the x32 patch
kexec-tools upstream previously integrated the patch into master rev 587778e24c9 but for a bug report it was remove [1][2], after an intensive testing on OpenSUSE 13.1 64 bits and in poky variants: qemux86 [3], qemux86-64-x32 [4] and generix86-64 (minnow) [5] it worked. I think that the upstream revert was due to some integration issue while testing into OpenSUSE [2], i will try to push again to upstream. [1] http://lists.infradead.org/pipermail/kexec/2015-March/013482.html [2] https://github.com/horms/kexec-tools/commit/5041d45b1c6b66a0e6c48f6121c24cd9be506c68 [3] https://bugzilla.yoctoproject.org/show_bug.cgi?id=11050#c3 [4] https://bugzilla.yoctoproject.org/show_bug.cgi?id=11050#c4 [5] https://bugzilla.yoctoproject.org/show_bug.cgi?id=11050#c4 [YOCTO #11050] Signed-off-by: Aníbal Limón--- meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb b/meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb index 1062457..90d5985 100644 --- a/meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb +++ b/meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb @@ -18,6 +18,7 @@ SRC_URI += "${KERNELORG_MIRROR}/linux/utils/kernel/kexec/kexec-tools-${PV}.tar.g file://0010-kexec-ARM-Fix-add_buffer_phys_virt-align-issue.patch \ file://0001-x86-x86_64-Fix-format-warning-with-die.patch \ file://0002-ppc-Fix-format-warning-with-die.patch \ +file://kexec-x32.patch \ " SRC_URI[md5sum] = "b2b2c5e6b29d467d6e99d587fb6b7cf5" -- 2.1.4 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/2] Revert "kexec-tools: Remove unused patch"
This reverts commit ec1f1c4abe1d40708fefd56f01c58fff38f28960. Signed-off-by: Aníbal Limón--- .../kexec/kexec-tools/kexec-x32.patch | 88 ++ 1 file changed, 88 insertions(+) create mode 100644 meta/recipes-kernel/kexec/kexec-tools/kexec-x32.patch diff --git a/meta/recipes-kernel/kexec/kexec-tools/kexec-x32.patch b/meta/recipes-kernel/kexec/kexec-tools/kexec-x32.patch new file mode 100644 index 000..26d18eb --- /dev/null +++ b/meta/recipes-kernel/kexec/kexec-tools/kexec-x32.patch @@ -0,0 +1,88 @@ +x86_64: Add support to build kexec-tools with x32 ABI + +Summary of changes, + +configure.ac: Add test for detect x32 ABI. +purgatory/arch/x86_64/Makefile: Not use mcmodel large when + x32 ABI is set. +kexec/arch/x86_64/kexec-elf-rel-x86_64.c: When x32 ABI is set + use ELFCLASS32 instead of ELFCLASS64. +kexec/kexec-syscall.h: Add correct syscall number for x32 ABI. + +Upstream-Status: Submitted + +Signed-off-by: Aníbal Limón +Signed-off-by: Mariano Lopez + +--- + configure.ac | 9 + + kexec/arch/x86_64/kexec-elf-rel-x86_64.c | 4 + kexec/kexec-syscall.h| 4 + purgatory/arch/x86_64/Makefile | 4 +++- + 4 files changed, 20 insertions(+), 1 deletion(-) + +Index: kexec-tools-2.0.10/configure.ac +=== +--- kexec-tools-2.0.10.orig/configure.ac kexec-tools-2.0.10/configure.ac +@@ -56,6 +56,15 @@ case $target_cpu in + ;; + ia64|x86_64|alpha|m68k ) + ARCH="$target_cpu" ++ ++ dnl ---Test for x32 ABI in x86_64 ++ if test "x$ARCH" = "xx86_64" ; then ++ AC_EGREP_CPP(x32_test, ++ [#if defined(__x86_64__) && defined (__ILP32__) ++ x32_test ++ #endif ++ ], SUBARCH='x32', SUBARCH='64') ++ fi + ;; + * ) + AC_MSG_ERROR([unsupported architecture $target_cpu]) +Index: kexec-tools-2.0.10/kexec/arch/x86_64/kexec-elf-rel-x86_64.c +=== +--- kexec-tools-2.0.10.orig/kexec/arch/x86_64/kexec-elf-rel-x86_64.c kexec-tools-2.0.10/kexec/arch/x86_64/kexec-elf-rel-x86_64.c +@@ -8,7 +8,11 @@ int machine_verify_elf_rel(struct mem_eh + if (ehdr->ei_data != ELFDATA2LSB) { + return 0; + } ++#ifdef __ILP32__ ++ if (ehdr->ei_class != ELFCLASS32) { ++#else + if (ehdr->ei_class != ELFCLASS64) { ++#endif + return 0; + } + if (ehdr->e_machine != EM_X86_64) { +Index: kexec-tools-2.0.10/kexec/kexec-syscall.h +=== +--- kexec-tools-2.0.10.orig/kexec/kexec-syscall.h kexec-tools-2.0.10/kexec/kexec-syscall.h +@@ -31,8 +31,12 @@ + #define __NR_kexec_load 268 + #endif + #ifdef __x86_64__ ++#ifdef __ILP32__ ++#define __NR_kexec_load 528 ++#else + #define __NR_kexec_load 246 + #endif ++#endif + #ifdef __s390x__ + #define __NR_kexec_load 277 + #endif +Index: kexec-tools-2.0.10/purgatory/arch/x86_64/Makefile +=== +--- kexec-tools-2.0.10.orig/purgatory/arch/x86_64/Makefile kexec-tools-2.0.10/purgatory/arch/x86_64/Makefile +@@ -23,4 +23,6 @@ x86_64_PURGATORY_SRCS += purgatory/arch/ + x86_64_PURGATORY_SRCS += purgatory/arch/i386/vga.c + x86_64_PURGATORY_SRCS += purgatory/arch/i386/pic.c + +-x86_64_PURGATORY_EXTRA_CFLAGS = -mcmodel=large ++ifeq ($(SUBARCH),64) ++x86_64_PURGATORY_EXTRA_CFLAGS = -mcmodel=large ++endif -- 2.1.4 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/2] Revert "kexec-tools: Remove unused patch"
This reverts commit ec1f1c4abe1d40708fefd56f01c58fff38f28960. Signed-off-by: Aníbal Limón--- .../kexec/kexec-tools/kexec-x32.patch | 88 ++ 1 file changed, 88 insertions(+) create mode 100644 meta/recipes-kernel/kexec/kexec-tools/kexec-x32.patch diff --git a/meta/recipes-kernel/kexec/kexec-tools/kexec-x32.patch b/meta/recipes-kernel/kexec/kexec-tools/kexec-x32.patch new file mode 100644 index 000..26d18eb --- /dev/null +++ b/meta/recipes-kernel/kexec/kexec-tools/kexec-x32.patch @@ -0,0 +1,88 @@ +x86_64: Add support to build kexec-tools with x32 ABI + +Summary of changes, + +configure.ac: Add test for detect x32 ABI. +purgatory/arch/x86_64/Makefile: Not use mcmodel large when + x32 ABI is set. +kexec/arch/x86_64/kexec-elf-rel-x86_64.c: When x32 ABI is set + use ELFCLASS32 instead of ELFCLASS64. +kexec/kexec-syscall.h: Add correct syscall number for x32 ABI. + +Upstream-Status: Submitted + +Signed-off-by: Aníbal Limón +Signed-off-by: Mariano Lopez + +--- + configure.ac | 9 + + kexec/arch/x86_64/kexec-elf-rel-x86_64.c | 4 + kexec/kexec-syscall.h| 4 + purgatory/arch/x86_64/Makefile | 4 +++- + 4 files changed, 20 insertions(+), 1 deletion(-) + +Index: kexec-tools-2.0.10/configure.ac +=== +--- kexec-tools-2.0.10.orig/configure.ac kexec-tools-2.0.10/configure.ac +@@ -56,6 +56,15 @@ case $target_cpu in + ;; + ia64|x86_64|alpha|m68k ) + ARCH="$target_cpu" ++ ++ dnl ---Test for x32 ABI in x86_64 ++ if test "x$ARCH" = "xx86_64" ; then ++ AC_EGREP_CPP(x32_test, ++ [#if defined(__x86_64__) && defined (__ILP32__) ++ x32_test ++ #endif ++ ], SUBARCH='x32', SUBARCH='64') ++ fi + ;; + * ) + AC_MSG_ERROR([unsupported architecture $target_cpu]) +Index: kexec-tools-2.0.10/kexec/arch/x86_64/kexec-elf-rel-x86_64.c +=== +--- kexec-tools-2.0.10.orig/kexec/arch/x86_64/kexec-elf-rel-x86_64.c kexec-tools-2.0.10/kexec/arch/x86_64/kexec-elf-rel-x86_64.c +@@ -8,7 +8,11 @@ int machine_verify_elf_rel(struct mem_eh + if (ehdr->ei_data != ELFDATA2LSB) { + return 0; + } ++#ifdef __ILP32__ ++ if (ehdr->ei_class != ELFCLASS32) { ++#else + if (ehdr->ei_class != ELFCLASS64) { ++#endif + return 0; + } + if (ehdr->e_machine != EM_X86_64) { +Index: kexec-tools-2.0.10/kexec/kexec-syscall.h +=== +--- kexec-tools-2.0.10.orig/kexec/kexec-syscall.h kexec-tools-2.0.10/kexec/kexec-syscall.h +@@ -31,8 +31,12 @@ + #define __NR_kexec_load 268 + #endif + #ifdef __x86_64__ ++#ifdef __ILP32__ ++#define __NR_kexec_load 528 ++#else + #define __NR_kexec_load 246 + #endif ++#endif + #ifdef __s390x__ + #define __NR_kexec_load 277 + #endif +Index: kexec-tools-2.0.10/purgatory/arch/x86_64/Makefile +=== +--- kexec-tools-2.0.10.orig/purgatory/arch/x86_64/Makefile kexec-tools-2.0.10/purgatory/arch/x86_64/Makefile +@@ -23,4 +23,6 @@ x86_64_PURGATORY_SRCS += purgatory/arch/ + x86_64_PURGATORY_SRCS += purgatory/arch/i386/vga.c + x86_64_PURGATORY_SRCS += purgatory/arch/i386/pic.c + +-x86_64_PURGATORY_EXTRA_CFLAGS = -mcmodel=large ++ifeq ($(SUBARCH),64) ++x86_64_PURGATORY_EXTRA_CFLAGS = -mcmodel=large ++endif -- 2.1.4 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 2/2] kexec-tools: Add again the x32 patch
kexec-tools upstream previously integrated the patch into master rev 587778e24c9 but for a bug report it was remove [1][2], after an intensive testing on OpenSUSE 13.1 64 bits and in poky variants: qemux86 [3], qemux86-64-x32 [4] and generix86-64 (minnow) [5] it worked. I think that the upstream revert was due to some integration issue while testing into OpenSUSE [2], i will try to push again to upstream. [1] http://lists.infradead.org/pipermail/kexec/2015-March/013482.html [2] https://github.com/horms/kexec-tools/commit/5041d45b1c6b66a0e6c48f6121c24cd9be506c68 [3] https://bugzilla.yoctoproject.org/show_bug.cgi?id=11050#c3 [4] https://bugzilla.yoctoproject.org/show_bug.cgi?id=11050#c4 [5] https://bugzilla.yoctoproject.org/show_bug.cgi?id=11050#c4 [YOCTO #11050] Signed-off-by: Aníbal Limón--- meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb b/meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb index 1062457..90d5985 100644 --- a/meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb +++ b/meta/recipes-kernel/kexec/kexec-tools_2.0.14.bb @@ -18,6 +18,7 @@ SRC_URI += "${KERNELORG_MIRROR}/linux/utils/kernel/kexec/kexec-tools-${PV}.tar.g file://0010-kexec-ARM-Fix-add_buffer_phys_virt-align-issue.patch \ file://0001-x86-x86_64-Fix-format-warning-with-die.patch \ file://0002-ppc-Fix-format-warning-with-die.patch \ +file://kexec-x32.patch \ " SRC_URI[md5sum] = "b2b2c5e6b29d467d6e99d587fb6b7cf5" -- 2.1.4 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] OpenEmbedded 2017 General Meeting
The board would like to hold a general meeting with all members. Under the new by-laws of the OpenEmbedded organization, we can meet electronically. This will also fulfill the requirement for an annual, general meeting. Planned Date/Time: Wednesday, May 3rd, at 8am US-CDT(UTC-06:00)/3pm CET(UTC+01:00) Wiki page with full details, including teleconference information here: http://www.openembedded.org/wiki/2017_General_Meeting Please take a moment to add your name to the list if you are planning to attend and any agenda items you would like to discuss. -- Sean signature.asc Description: OpenPGP digital signature -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 3/3] qemuboot.bbclass: save relative paths in conf file
This saves relative paths in the qemuboot.conf file instead of absolute paths. This is to allow the images and kernels to be relocated and still have the testimage and runqemu work. [YOCTO #11375] Signed-off-by: brian avery--- meta/classes/qemuboot.bbclass | 7 +++ 1 file changed, 7 insertions(+) diff --git a/meta/classes/qemuboot.bbclass b/meta/classes/qemuboot.bbclass index cc5314e..86b3060 100644 --- a/meta/classes/qemuboot.bbclass +++ b/meta/classes/qemuboot.bbclass @@ -84,6 +84,7 @@ python do_write_qemuboot_conf() { qemuboot = "%s/%s.qemuboot.conf" % (d.getVar('IMGDEPLOYDIR'), d.getVar('IMAGE_NAME')) qemuboot_link = "%s/%s.qemuboot.conf" % (d.getVar('IMGDEPLOYDIR'), d.getVar('IMAGE_LINK_NAME')) +topdir="%s/"%(d.getVar('TOPDIR')).replace("//","/") cf = configparser.ConfigParser() cf.add_section('config_bsp') for k in qemuboot_vars(d): @@ -94,6 +95,9 @@ python do_write_qemuboot_conf() { 'qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/') else: val = d.getVar(k) +# we only want to write out relative paths so that we can relocate images +# and still run them +val=val.replace(topdir,"") cf.set('config_bsp', k, '%s' % val) # QB_DEFAULT_KERNEL's value of KERNEL_IMAGETYPE is the name of a symlink @@ -101,6 +105,9 @@ python do_write_qemuboot_conf() { # Read the link and replace it with the full filename of the target. kernel_link = os.path.join(d.getVar('DEPLOY_DIR_IMAGE'), d.getVar('QB_DEFAULT_KERNEL')) kernel = os.path.realpath(kernel_link) +# we only want to write out relative paths so that we can relocate images +# and still run them +kernel=kernel.replace(topdir,"") cf.set('config_bsp', 'QB_DEFAULT_KERNEL', kernel) bb.utils.mkdirhier(os.path.dirname(qemuboot)) -- 1.9.1 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/3] meta: add search, replace strings to export2json
We want to be able to save relative paths so that we can relocate the deploy dir images and kernels, yet still have qemu and testimage work correctly. This extends export2json with 2 named arguments so a search/replace operation can be done to remove the leading path. [YOCTO #11375] Signed-off-by: brian avery--- meta/lib/oe/data.py | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/meta/lib/oe/data.py b/meta/lib/oe/data.py index 80bba2b..b8901e6 100644 --- a/meta/lib/oe/data.py +++ b/meta/lib/oe/data.py @@ -17,7 +17,7 @@ def typed_value(key, d): except (TypeError, ValueError) as exc: bb.msg.fatal("Data", "%s: %s" % (key, str(exc))) -def export2json(d, json_file, expand=True): +def export2json(d, json_file, expand=True, searchString="",replaceString=""): data2export = {} keys2export = [] @@ -37,9 +37,11 @@ def export2json(d, json_file, expand=True): for key in keys2export: try: -data2export[key] = d.getVar(key, expand) +data2export[key] = d.getVar(key, expand).replace(searchString,replaceString) except bb.data_smart.ExpansionError: data2export[key] = '' +except AttributeError: +pass with open(json_file, "w") as f: json.dump(data2export, f, skipkeys=True, indent=4, sort_keys=True) -- 1.9.1 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 2/3] rootfs-postcommands.bbclass: save relative paths
We pass the TOPDIR to do a search/replace in export2json so that we save relative paths in the testdata.json file rather than absolute paths. This is to allow the images and kernels to be relocated yet still allow testimage to work. [YOCTO #11375] Signed-off-by: brian avery--- meta/classes/rootfs-postcommands.bbclass | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/meta/classes/rootfs-postcommands.bbclass b/meta/classes/rootfs-postcommands.bbclass index c42829d..498174a 100644 --- a/meta/classes/rootfs-postcommands.bbclass +++ b/meta/classes/rootfs-postcommands.bbclass @@ -132,7 +132,7 @@ zap_empty_root_password () { if [ -e ${IMAGE_ROOTFS}/etc/passwd ]; then sed -i 's%^root::%root:*:%' ${IMAGE_ROOTFS}/etc/passwd fi -} +} # # allow dropbear/openssh to accept root logins and logins from accounts with an empty password string @@ -243,7 +243,7 @@ python write_image_manifest () { os.symlink(os.path.basename(manifest_name), manifest_link) } -# Can be use to create /etc/timestamp during image construction to give a reasonably +# Can be use to create /etc/timestamp during image construction to give a reasonably # sane default time setting rootfs_update_timestamp () { date -u +%4Y%2m%2d%2H%2M%2S >${IMAGE_ROOTFS}/etc/timestamp @@ -286,6 +286,7 @@ rootfs_sysroot_relativelinks () { sysroot-relativelinks.py ${SDK_OUTPUT}/${SDKTARGETSYSROOT} } + # Generated test data json file python write_image_test_data() { from oe.data import export2json @@ -294,7 +295,8 @@ python write_image_test_data() { testdata_link = "%s/%s.testdata.json" % (d.getVar('DEPLOY_DIR_IMAGE'), d.getVar('IMAGE_LINK_NAME')) bb.utils.mkdirhier(os.path.dirname(testdata)) -export2json(d, testdata) +searchString = "%s/"%(d.getVar("TOPDIR")).replace("//","/") +export2json(d, testdata,searchString=searchString,replaceString="") if os.path.lexists(testdata_link): os.remove(testdata_link) -- 1.9.1 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/3] meta: save relative paths to qemuboot.conf and testdata.json
This patch set changes the behaviour to save relative paths instead of absolute paths into the qemuboot.conf and the testdata.json files. A sed test verified that this seems to work without complication. If certain variables, need to be excluded from this relative path fix, that can be done with subsequent patches. This is to fix YOCTO #11375 https://bugzilla.yoctoproject.org/show_bug.cgi?id=11375 -brian The following changes since commit 1423508b29fc557d8a1305f39c33de33e28d9003: bitbake: bitbake: Update version to 1.34.0 for stable release (2017-04-19 10:42:12 +0100) are available in the git repository at: git://git.yoctoproject.org/poky-contrib bavery/poky/relpath_11375 http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/poky/relpath_11375 brian avery (3): meta: add search,replace strings to export2json rootfs-postcommands.bbclass: save relative paths qemuboot.bbclass: save relative paths in conf file meta/classes/qemuboot.bbclass| 7 +++ meta/classes/rootfs-postcommands.bbclass | 8 +--- meta/lib/oe/data.py | 6 -- 3 files changed, 16 insertions(+), 5 deletions(-) -- 1.9.1 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] ✗ patchtest: failure for Add files via upload
== Series Details == Series: Add files via upload Revision: 1 URL : https://patchwork.openembedded.org/series/6421/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures: * PatchAdd files via upload Issue Shortlog does not follow expected format [test_shortlog_format] Suggested fixCommit shortlog (first line of commit message) should follow the format ": " * PatchAdd files via upload Issue Patch is missing Signed-off-by [test_signed_off_by_presence] Suggested fixSign off the patch (either manually or with "git commit --amend -s") If you believe any of these test results are incorrect, please reply to the mailing list (openembedded-core@lists.openembedded.org) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...). --- Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] Add files via upload
From: original-birdmanThe built curl is used during the builds, and any download using an https link (e.g. from github) requires the certificates, so these must be installed before curl is available. (Actually, absolute links get installed, so you also need to be using a build system with the relevant certs in place but this will be true). This was breaking stb-kodi builds on openViX. --- meta/recipes-support/curl/curl_7.53.1.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-support/curl/curl_7.53.1.bb b/meta/recipes-support/curl/curl_7.53.1.bb index bc78ffb..c953591 100644 --- a/meta/recipes-support/curl/curl_7.53.1.bb +++ b/meta/recipes-support/curl/curl_7.53.1.bb @@ -9,6 +9,8 @@ SRC_URI = "http://curl.haxx.se/download/curl-${PV}.tar.bz2 \ file://0001-replace-krb5-config-with-pkg-config.patch \ " +DEPENDS = "ca-certificates" + # curl likes to set -g0 in CFLAGS, so we stop it # from mucking around with debug options # -- 2.7.4 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH V2 2/5] libtirpc: Expose key_secretkey_is_set API
libnsl needs this API Signed-off-by: Khem Raj--- - v1 -> v2 - Document the change in the patch a bit more with upstream references .../libtirpc/export_key_secretkey_is_set.patch | 24 ++ meta/recipes-extended/libtirpc/libtirpc_1.0.1.bb | 1 + 2 files changed, 25 insertions(+) create mode 100644 meta/recipes-extended/libtirpc/libtirpc/export_key_secretkey_is_set.patch diff --git a/meta/recipes-extended/libtirpc/libtirpc/export_key_secretkey_is_set.patch b/meta/recipes-extended/libtirpc/libtirpc/export_key_secretkey_is_set.patch new file mode 100644 index 000..a276ba27a59 --- /dev/null +++ b/meta/recipes-extended/libtirpc/libtirpc/export_key_secretkey_is_set.patch @@ -0,0 +1,24 @@ +Add key_secretkey_is_set to exported symbols map + +key_secret_is_set is a typo in libtirpc map +Patch taken from + +https://sourceforge.net/p/libtirpc/discussion/637321/thread/fd73d431/ + +Upstream-Status: Pending + +Signed-off-by: Khem Raj + +Index: libtirpc-1.0.1/src/libtirpc.map +=== +--- libtirpc-1.0.1.orig/src/libtirpc.map libtirpc-1.0.1/src/libtirpc.map +@@ -298,7 +298,7 @@ TIRPC_0.3.2 { + key_gendes; + key_get_conv; + key_setsecret; +-key_secret_is_set; ++key_secretkey_is_set; + key_setnet; + netname2host; + netname2user; diff --git a/meta/recipes-extended/libtirpc/libtirpc_1.0.1.bb b/meta/recipes-extended/libtirpc/libtirpc_1.0.1.bb index 8ba547506bf..b96abc4d57e 100644 --- a/meta/recipes-extended/libtirpc/libtirpc_1.0.1.bb +++ b/meta/recipes-extended/libtirpc/libtirpc_1.0.1.bb @@ -13,6 +13,7 @@ SRC_URI = "${SOURCEFORGE_MIRROR}/${BPN}/${BP}.tar.bz2;name=libtirpc \ ${GENTOO_MIRROR}/${BPN}-glibc-nfs.tar.xz;name=glibc-nfs \ file://libtirpc-1.0.2-rc3.patch \ file://libtirpc-0.2.1-fortify.patch \ + file://export_key_secretkey_is_set.patch \ " SRC_URI_append_libc-uclibc = " file://remove-des-functionality.patch \ -- 2.12.2 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] wic: Add option to not change fstab
Create an option to wic doesn't change fstab file, the final fstab file will be same that in rootfs and wic doesn't update file, e.g adding a new mount point. Users can control the fstab file content in base-files recipe. This is useful if you want to only create an partition but not add fstab mount point or add new mount point using label e.g: LABEL=recovery /recovery auto defaults 0 1 Signed-off-by: Fabio Berton--- scripts/lib/wic/help.py | 7 ++- scripts/lib/wic/plugins/imager/direct.py | 6 +- scripts/wic | 2 ++ 3 files changed, 13 insertions(+), 2 deletions(-) diff --git a/scripts/lib/wic/help.py b/scripts/lib/wic/help.py index aee2451a72..1112192c6c 100644 --- a/scripts/lib/wic/help.py +++ b/scripts/lib/wic/help.py @@ -154,7 +154,7 @@ SYNOPSIS [-e | --image-name] [-s, --skip-build-check] [-D, --debug] [-r, --rootfs-dir] [-b, --bootimg-dir] [-k, --kernel-dir] [-n, --native-sysroot] [-f, --build-rootfs] -[-c, --compress-with] [-m, --bmap] +[-c, --compress-with] [-m, --bmap] [--no-fstab-update] DESCRIPTION This command creates an OpenEmbedded image based on the 'OE @@ -226,6 +226,11 @@ DESCRIPTION The -m option is used to produce .bmap file for the image. This file can be used to flash image using bmaptool utility. + +The --no-fstab-update option is used to doesn't change fstab file. When +using this option the final fstab file will be same that in rootfs and +wic doesn't update file, e.g adding a new mount point. User can control +the fstab file content in base-files recipe. """ wic_list_usage = """ diff --git a/scripts/lib/wic/plugins/imager/direct.py b/scripts/lib/wic/plugins/imager/direct.py index f2e6127331..a5afec9a14 100644 --- a/scripts/lib/wic/plugins/imager/direct.py +++ b/scripts/lib/wic/plugins/imager/direct.py @@ -68,6 +68,7 @@ class DirectPlugin(ImagerPlugin): self.outdir = options.outdir self.compressor = options.compressor self.bmap = options.bmap +self.no_fstab_update = options.no_fstab_update self.name = "%s-%s" % (os.path.splitext(os.path.basename(wks_file))[0], strftime("%Y%m%d%H%M")) @@ -156,7 +157,10 @@ class DirectPlugin(ImagerPlugin): filesystems from the artifacts directly and combine them into a partitioned image. """ -fstab_path = self._write_fstab(self.rootfs_dir.get("ROOTFS_DIR")) +if self.no_fstab_update: +fstab_path = None +else: +fstab_path = self._write_fstab(self.rootfs_dir.get("ROOTFS_DIR")) for part in self.parts: # get rootfs size from bitbake variable if it's not set in .ks file diff --git a/scripts/wic b/scripts/wic index a5f2dbfc6f..5907098b3a 100755 --- a/scripts/wic +++ b/scripts/wic @@ -133,6 +133,8 @@ def wic_create_subcommand(args, usage_str): dest='compressor', help="compress image with specified compressor") parser.add_option("-m", "--bmap", action="store_true", help="generate .bmap") +parser.add_option("", "--no-fstab-update" ,action="store_true", + help="Do not change fstab file.") parser.add_option("-v", "--vars", dest='vars_dir', help="directory with .env files that store " "bitbake variables") -- 2.11.0 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [morty][PATCH] logrotate: replace fedorahosted.org SRC_URI with github.com source
On 04/18/2017 12:57 PM, Davis, Michael wrote: From: Choong YinThongfedorahosted.org was retired on March 1st, 2017. This is to update the SRC_URI to point to github.com. Update the ${PN} to ${BPN} in order to pass the autobuilder mulitlib enable configuration. [YOCTO #11226] in staging Thanks, Armin Signed-off-by: Choong YinThong Signed-off-by: Richard Purdie --- meta/recipes-extended/logrotate/logrotate_3.9.1.bb | 17 + 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/meta/recipes-extended/logrotate/logrotate_3.9.1.bb b/meta/recipes-extended/logrotate/logrotate_3.9.1.bb index 5f1a601..5bd3381 100644 --- a/meta/recipes-extended/logrotate/logrotate_3.9.1.bb +++ b/meta/recipes-extended/logrotate/logrotate_3.9.1.bb @@ -1,6 +1,6 @@ SUMMARY = "Rotates, compresses, removes and mails system log files" SECTION = "console/utils" -HOMEPAGE = "https://fedorahosted.org/logrotate/; +HOMEPAGE = "https://github.com/logrotate/logrotate/issues; LICENSE = "GPLv2" # TODO: logrotate 3.8.8 adds autotools/automake support, update recipe to use it. @@ -10,14 +10,23 @@ DEPENDS="coreutils popt" LIC_FILES_CHKSUM = "file://COPYING;md5=18810669f13b87348459e611d31ab760" -SRC_URI = "https://fedorahosted.org/releases/l/o/logrotate/logrotate-${PV}.tar.gz \ +# When updating logrotate to latest upstream, SRC_URI should point to +# a proper release tarball from https://github.com/logrotate/logrotate/releases +# and we have to take the snapshot for now because there is no such +# tarball available for 3.9.1. + +S = "${WORKDIR}/${BPN}-r3-9-1" + +UPSTREAM_CHECK_URI = "https://github.com/${BPN}/${BPN}/releases; + +SRC_URI = "https://github.com/${BPN}/${BPN}/archive/r3-9-1.tar.gz \ file://act-as-mv-when-rotate.patch \ file://update-the-manual.patch \ file://disable-check-different-filesystems.patch \ " -SRC_URI[md5sum] = "4492b145b6d542e4a2f41e77fa199ab0" -SRC_URI[sha256sum] = "022769e3288c80981559a8421703c88e8438b447235e36dd3c8e97cd94c52545" +SRC_URI[md5sum] = "8572b7c2cf9ade09a8a8e10098500fb3" +SRC_URI[sha256sum] = "5bf8e478c428e7744fefa465118f8296e7e771c981fb6dffb7527856a0ea3617" PACKAGECONFIG ?= "\ ${@bb.utils.contains('DISTRO_FEATURES', 'acl', 'acl', '', d)} \ -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 2/5] libtirpc: Expose key_secretkey_is_set API
On Wed, Apr 19, 2017 at 9:36 AM, Burton, Rosswrote: > > On 19 April 2017 at 17:25, Khem Raj wrote: >> >> key_secret_is_set is a typo in libtirpc map file which is fixed here. > > > Can you resubmit with that in the commit log. Are you pushing these > upstream? Upstream already has a report and a patch for this https://sourceforge.net/p/libtirpc/discussion/637321/thread/fd73d431/ > > Ross -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 5/5] libidn: Fix build with gcc7
On Wed, Apr 19, 2017 at 8:06 AM, André Draszikwrote: > On Tue, 2017-04-18 at 18:58 -0700, Khem Raj wrote: >> Replace a local patch for format warning with the one >> that got committed upstream > > This commit message is confusing, as the two patches are unrelated and they > are addressing different issues. > > You are: > - removing a patch that fixed Wformat-security warnings / errors > (not upstreamed) > - adding a patch that fixes other (unrelated) Wformat warnings > (from upstream) > The backport obviously is a different patch and works fine with security flags turned on. Can you point whats missing from outgoing patch that we need ? > > Cheers, > Andre' > >> >> Signed-off-by: Khem Raj >> --- >> ...1-idn-fix-printf-format-security-warnings.patch | 825 >> + >> .../libidn/libidn/gcc7-compatibility.patch | 334 + >> meta/recipes-extended/libidn/libidn_1.33.bb| 1 + >> 3 files changed, 1004 insertions(+), 156 deletions(-) >> create mode 100644 meta/recipes-extended/libidn/libidn/gcc7- >> compatibility.patch >> >> diff --git a/meta/recipes-extended/libidn/libidn/0001-idn-fix-printf- >> format-security-warnings.patch b/meta/recipes-extended/libidn/libidn/0001- >> idn-fix-printf-format-security-warnings.patch >> index 5adc7d9fd98..2d5faabb240 100644 >> --- a/meta/recipes-extended/libidn/libidn/0001-idn-fix-printf-format- >> security-warnings.patch >> +++ b/meta/recipes-extended/libidn/libidn/0001-idn-fix-printf-format- >> security-warnings.patch >> @@ -1,181 +1,694 @@ >> -From 82f98dcbc429bbe89a9837c533cbcbc02e77c790 Mon Sep 17 00:00:00 2001 >> -From: =?UTF-8?q?Andr=C3=A9=20Draszik?= >> -Date: Tue, 28 Jun 2016 12:43:31 +0100 >> -Subject: [PATCH] idn: fix printf() format security warnings >> -MIME-Version: 1.0 >> -Content-Type: text/plain; charset=UTF-8 >> -Content-Transfer-Encoding: 8bit >> +From 7148adf34dae30345c2e4d9d437838a45ba6f6e8 Mon Sep 17 00:00:00 2001 >> +From: =?utf8?q?Tim=20R=C3=BChsen?= >> +Date: Wed, 1 Feb 2017 11:06:39 +0100 >> +Subject: [PATCH] Fix -Wformat warnings >> >> -| ../../libidn-1.32/src/idn.c: In function 'main': >> -| ../../libidn-1.32/src/idn.c:172:7: error: format not a string literal >> and no format arguments [-Werror=format-security] >> -|error (0, 0, _("only one of -s, -e, -d, -a, -u or -n can be >> specified")); >> -|^ >> -| ../../libidn-1.32/src/idn.c:187:5: error: format not a string literal >> and no format arguments [-Werror=format-security] >> -| fprintf (stderr, _("Type each input string on a line by itself, " >> -| ^~~ >> -| ../../libidn-1.32/src/idn.c:202:4: error: format not a string literal >> and no format arguments [-Werror=format-security] >> -| error (EXIT_FAILURE, errno, _("input error")); >> -| ^ >> -| ../../libidn-1.32/src/idn.c:220:8: error: format not a string literal >> and no format arguments [-Werror=format-security] >> -| _("could not convert from UTF-8 to UCS-4")); >> -| ^ >> -| ../../libidn-1.32/src/idn.c:245:8: error: format not a string literal >> and no format arguments [-Werror=format-security] >> -| _("could not convert from UTF-8 to UCS-4")); >> -| ^ >> -| ../../libidn-1.32/src/idn.c:281:6: error: format not a string literal >> and no format arguments [-Werror=format-security] >> -| _("could not convert from UTF-8 to UCS-4")); >> -| ^ >> -| ../../libidn-1.32/src/idn.c:340:6: error: format not a string literal >> and no format arguments [-Werror=format-security] >> -| _("could not convert from UCS-4 to UTF-8")); >> -| ^ >> -| ../../libidn-1.32/src/idn.c:364:6: error: format not a string literal >> and no format arguments [-Werror=format-security] >> -| _("could not convert from UCS-4 to UTF-8")); >> -| ^ >> -| ../../libidn-1.32/src/idn.c:442:8: error: format not a string literal >> and no format arguments [-Werror=format-security] >> -| _("could not convert from UCS-4 to UTF-8")); >> -| ^ >> -| ../../libidn-1.32/src/idn.c:498:6: error: format not a string literal >> and no format arguments [-Werror=format-security] >> -| _("could not convert from UTF-8 to UCS-4")); >> -| ^ >> -| ../../libidn-1.32/src/idn.c:527:5: error: format not a string literal >> and no format arguments [-Werror=format-security] >> -| _("could not convert from UTF-8 to UCS-4")); >> -| ^ >> -| ../../libidn-1.32/src/idn.c:540:6: error: format not a string literal >> and no format arguments [-Werror=format-security] >> -| error (EXIT_FAILURE, 0, _("could not do NFKC normalization")); >> -| ^ >> -| ../../libidn-1.32/src/idn.c:551:5: error: format not a string literal >> and no format arguments [-Werror=format-security] >> -| _("could not convert from UTF-8 to UCS-4")); >> -| ^ >> - >> -Signed-off-by: André Draszik >> --- >> -Upstream-Status:
Re: [OE-core] [PATCH 2/5] libtirpc: Expose key_secretkey_is_set API
On 19 April 2017 at 17:25, Khem Rajwrote: > key_secret_is_set is a typo in libtirpc map file which is fixed here. > Can you resubmit with that in the commit log. Are you pushing these upstream? Ross -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 3/5] libtirpc: Enable des APIs for musl
On Wed, Apr 19, 2017 at 1:57 AM, André Draszikwrote: > On Tue, 2017-04-18 at 18:58 -0700, Khem Raj wrote: >> Use memset() API instead of __bzero() >> Drop the patch removing des_* functions for musl >> >> Signed-off-by: Khem Raj >> --- >> .../0001-replace-__bzero-with-memset-API.patch | 28 + >> .../libtirpc/remove-des-functionality.patch| 139 >> - >> meta/recipes-extended/libtirpc/libtirpc_1.0.1.bb | 5 +- >> 3 files changed, 31 insertions(+), 141 deletions(-) >> create mode 100644 meta/recipes-extended/libtirpc/libtirpc/0001-replace- >> __bzero-with-memset-API.patch >> delete mode 100644 meta/recipes-extended/libtirpc/libtirpc/remove-des- >> functionality.patch >> >> [...] >> >> >> SRC_URI_append_libc-uclibc = " file://remove-des-functionality.patch \ > > This patch is being removed with this change, and so uclibc builds will > fail. yes I know. one should move it to bbappend in own layer if using uclibc. Is it time to remove all remaining references to uclibc? Probably. > > Cheers, > Andre' > > -- > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 2/5] libtirpc: Expose key_secretkey_is_set API
On Wed, Apr 19, 2017 at 1:52 AM, Burton, Rosswrote: > > On 19 April 2017 at 02:58, Khem Raj wrote: >> >> +-key_secret_is_set; >> ++key_secretkey_is_set; > > > This removes key_secret_is_set, was this a typo upstream or a mistake in the > patch? key_secret_is_set is a typo in libtirpc map file which is fixed here. > > Ross -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 5/5] libidn: Fix build with gcc7
On Tue, 2017-04-18 at 18:58 -0700, Khem Raj wrote: > Replace a local patch for format warning with the one > that got committed upstream This commit message is confusing, as the two patches are unrelated and they are addressing different issues. You are: - removing a patch that fixed Wformat-security warnings / errors (not upstreamed) - adding a patch that fixes other (unrelated) Wformat warnings (from upstream) Cheers, Andre' > > Signed-off-by: Khem Raj> --- > ...1-idn-fix-printf-format-security-warnings.patch | 825 > + > .../libidn/libidn/gcc7-compatibility.patch | 334 + > meta/recipes-extended/libidn/libidn_1.33.bb| 1 + > 3 files changed, 1004 insertions(+), 156 deletions(-) > create mode 100644 meta/recipes-extended/libidn/libidn/gcc7- > compatibility.patch > > diff --git a/meta/recipes-extended/libidn/libidn/0001-idn-fix-printf- > format-security-warnings.patch b/meta/recipes-extended/libidn/libidn/0001- > idn-fix-printf-format-security-warnings.patch > index 5adc7d9fd98..2d5faabb240 100644 > --- a/meta/recipes-extended/libidn/libidn/0001-idn-fix-printf-format- > security-warnings.patch > +++ b/meta/recipes-extended/libidn/libidn/0001-idn-fix-printf-format- > security-warnings.patch > @@ -1,181 +1,694 @@ > -From 82f98dcbc429bbe89a9837c533cbcbc02e77c790 Mon Sep 17 00:00:00 2001 > -From: =?UTF-8?q?Andr=C3=A9=20Draszik?= > -Date: Tue, 28 Jun 2016 12:43:31 +0100 > -Subject: [PATCH] idn: fix printf() format security warnings > -MIME-Version: 1.0 > -Content-Type: text/plain; charset=UTF-8 > -Content-Transfer-Encoding: 8bit > +From 7148adf34dae30345c2e4d9d437838a45ba6f6e8 Mon Sep 17 00:00:00 2001 > +From: =?utf8?q?Tim=20R=C3=BChsen?= > +Date: Wed, 1 Feb 2017 11:06:39 +0100 > +Subject: [PATCH] Fix -Wformat warnings > > -| ../../libidn-1.32/src/idn.c: In function 'main': > -| ../../libidn-1.32/src/idn.c:172:7: error: format not a string literal > and no format arguments [-Werror=format-security] > -|error (0, 0, _("only one of -s, -e, -d, -a, -u or -n can be > specified")); > -|^ > -| ../../libidn-1.32/src/idn.c:187:5: error: format not a string literal > and no format arguments [-Werror=format-security] > -| fprintf (stderr, _("Type each input string on a line by itself, " > -| ^~~ > -| ../../libidn-1.32/src/idn.c:202:4: error: format not a string literal > and no format arguments [-Werror=format-security] > -| error (EXIT_FAILURE, errno, _("input error")); > -| ^ > -| ../../libidn-1.32/src/idn.c:220:8: error: format not a string literal > and no format arguments [-Werror=format-security] > -| _("could not convert from UTF-8 to UCS-4")); > -| ^ > -| ../../libidn-1.32/src/idn.c:245:8: error: format not a string literal > and no format arguments [-Werror=format-security] > -| _("could not convert from UTF-8 to UCS-4")); > -| ^ > -| ../../libidn-1.32/src/idn.c:281:6: error: format not a string literal > and no format arguments [-Werror=format-security] > -| _("could not convert from UTF-8 to UCS-4")); > -| ^ > -| ../../libidn-1.32/src/idn.c:340:6: error: format not a string literal > and no format arguments [-Werror=format-security] > -| _("could not convert from UCS-4 to UTF-8")); > -| ^ > -| ../../libidn-1.32/src/idn.c:364:6: error: format not a string literal > and no format arguments [-Werror=format-security] > -| _("could not convert from UCS-4 to UTF-8")); > -| ^ > -| ../../libidn-1.32/src/idn.c:442:8: error: format not a string literal > and no format arguments [-Werror=format-security] > -| _("could not convert from UCS-4 to UTF-8")); > -| ^ > -| ../../libidn-1.32/src/idn.c:498:6: error: format not a string literal > and no format arguments [-Werror=format-security] > -| _("could not convert from UTF-8 to UCS-4")); > -| ^ > -| ../../libidn-1.32/src/idn.c:527:5: error: format not a string literal > and no format arguments [-Werror=format-security] > -| _("could not convert from UTF-8 to UCS-4")); > -| ^ > -| ../../libidn-1.32/src/idn.c:540:6: error: format not a string literal > and no format arguments [-Werror=format-security] > -| error (EXIT_FAILURE, 0, _("could not do NFKC normalization")); > -| ^ > -| ../../libidn-1.32/src/idn.c:551:5: error: format not a string literal > and no format arguments [-Werror=format-security] > -| _("could not convert from UTF-8 to UCS-4")); > -| ^ > - > -Signed-off-by: André Draszik > --- > -Upstream-Status: Pending > +Upstream-Status: Backport > +Signed-off-by: Khem Raj > > - src/idn.c | 27 ++- > - 1 file changed, 14 insertions(+), 13 deletions(-) > + examples/example.c | 6 +++--- > + examples/example3.c| 4 ++-- > + examples/example4.c| 4 ++-- > + examples/example5.c| 2 +- > +
[OE-core] [PATCH] package_manager.py: Reverse rpm arch order
The architecture list used by dnf/libsolv was in the wrong order. As a result, the images were built with wrong and unpredictable packages. $ MACHINE=intel-corei7-64 bitbake core-image-sato $ MACHINE=qemux86-64 bitbake core-image-sato $ MACHINE=intel-corei7-64 bitbake -ccleansstate core-image-sato $ MACHINE=intel-corei7-64 bitbake core-image-sato The first image had 0 core2_64 packages in it, but the last one had 583 core2_64 packages (which were built for the qemu image in between). Reverse the arch order in etc/dnf/vars/arch. Fixes [YOCTO #11384]. Signed-off-by: Jussi Kukkonen--- The fix was suggested by Kanavin. It works correctly in my tests but obviously there is potential to break things for rpm builds here. Thanks, Jussi meta/lib/oe/package_manager.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/lib/oe/package_manager.py b/meta/lib/oe/package_manager.py index f7190cf..f1b65bd 100644 --- a/meta/lib/oe/package_manager.py +++ b/meta/lib/oe/package_manager.py @@ -489,7 +489,7 @@ class RpmPM(PackageManager): def _configure_dnf(self): # libsolv handles 'noarch' internally, we don't need to specify it explicitly -archs = [i for i in self.archs.split() if i not in ["any", "all", "noarch"]] +archs = [i for i in reversed(self.archs.split()) if i not in ["any", "all", "noarch"]] # This prevents accidental matching against libsolv's built-in policies if len(archs) <= 1: archs = archs + ["bogusarch"] -- 2.1.4 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [morty] glibc: Security fix CVE-2016-6323
arm: mark __startcontext as .cantunwind, GNU CVE: CVE-2016-6323 Signed-off-by: Andrej ValekSigned-off-by: Pascal Bach --- meta/recipes-core/glibc/glibc/CVE-2016-6323.patch | 39 +++ meta/recipes-core/glibc/glibc_2.24.bb | 1 + 2 files changed, 40 insertions(+) create mode 100644 meta/recipes-core/glibc/glibc/CVE-2016-6323.patch diff --git a/meta/recipes-core/glibc/glibc/CVE-2016-6323.patch b/meta/recipes-core/glibc/glibc/CVE-2016-6323.patch new file mode 100644 index 000..f9b9fa5 --- /dev/null +++ b/meta/recipes-core/glibc/glibc/CVE-2016-6323.patch @@ -0,0 +1,39 @@ +glibc-2.24: Fix CVE-2016-6323 + +[No upstream tracking] -- https://sourceware.org/bugzilla/show_bug.cgi?id=20435 + +arm: mark __startcontext as .cantunwind, GNU + +Glibc bug where the makecontext function would create +an execution context which is incompatible with the unwinder, +causing it to hang when the generation of a backtrace is attempted. + +Upstream-Status: Backport [https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=9e2ff6c9cc54c0b4402b8d49e4abe7000fde7617] +CVE: CVE-2016-6323 +Signed-off-by: Andrej Valek +Signed-off-by: Pascal Bach + +diff --git a/sysdeps/unix/sysv/linux/arm/setcontext.S b/sysdeps/unix/sysv/linux/arm/setcontext.S +index 603e508..d1f168f 100644 +--- a/sysdeps/unix/sysv/linux/arm/setcontext.S b/sysdeps/unix/sysv/linux/arm/setcontext.S +@@ -86,12 +86,19 @@ weak_alias(__setcontext, setcontext) + + /* Called when a makecontext() context returns. Start the + context in R4 or fall through to exit(). */ ++ /* Unwind descriptors are looked up based on PC - 2, so we have to ++ make sure to mark the instruction preceding the __startcontext ++ label as .cantunwind. */ ++ .fnstart ++ .cantunwind ++ nop + ENTRY(__startcontext) + movsr0, r4 + bne PLTJMP(__setcontext) + + @ New context was 0 - exit + b PLTJMP(HIDDEN_JUMPTARGET(exit)) ++ .fnend + END(__startcontext) + + #ifdef PIC diff --git a/meta/recipes-core/glibc/glibc_2.24.bb b/meta/recipes-core/glibc/glibc_2.24.bb index f5a21b2..bce06c7 100644 --- a/meta/recipes-core/glibc/glibc_2.24.bb +++ b/meta/recipes-core/glibc/glibc_2.24.bb @@ -37,6 +37,7 @@ SRC_URI = "${GLIBC_GIT_URI};branch=${SRCBRANCH};name=glibc \ file://0024-eglibc-Forward-port-cross-locale-generation-support.patch \ file://0025-Define-DUMMY_LOCALE_T-if-not-defined.patch \ file://0026-build_local_scope.patch \ + file://CVE-2016-6323.patch \ " SRC_URI += "\ -- 2.1.4 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [krogoth] glibc: Security fix CVE-2016-6323
arm: mark __startcontext as .cantunwind, GNU CVE: CVE-2016-6323 Signed-off-by: Andrej ValekSigned-off-by: Pascal Bach --- meta/recipes-core/glibc/glibc/CVE-2016-6323.patch | 39 +++ meta/recipes-core/glibc/glibc_2.23.bb | 1 + 2 files changed, 40 insertions(+) create mode 100644 meta/recipes-core/glibc/glibc/CVE-2016-6323.patch diff --git a/meta/recipes-core/glibc/glibc/CVE-2016-6323.patch b/meta/recipes-core/glibc/glibc/CVE-2016-6323.patch new file mode 100644 index 000..f9b9fa5 --- /dev/null +++ b/meta/recipes-core/glibc/glibc/CVE-2016-6323.patch @@ -0,0 +1,39 @@ +glibc-2.24: Fix CVE-2016-6323 + +[No upstream tracking] -- https://sourceware.org/bugzilla/show_bug.cgi?id=20435 + +arm: mark __startcontext as .cantunwind, GNU + +Glibc bug where the makecontext function would create +an execution context which is incompatible with the unwinder, +causing it to hang when the generation of a backtrace is attempted. + +Upstream-Status: Backport [https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=9e2ff6c9cc54c0b4402b8d49e4abe7000fde7617] +CVE: CVE-2016-6323 +Signed-off-by: Andrej Valek +Signed-off-by: Pascal Bach + +diff --git a/sysdeps/unix/sysv/linux/arm/setcontext.S b/sysdeps/unix/sysv/linux/arm/setcontext.S +index 603e508..d1f168f 100644 +--- a/sysdeps/unix/sysv/linux/arm/setcontext.S b/sysdeps/unix/sysv/linux/arm/setcontext.S +@@ -86,12 +86,19 @@ weak_alias(__setcontext, setcontext) + + /* Called when a makecontext() context returns. Start the + context in R4 or fall through to exit(). */ ++ /* Unwind descriptors are looked up based on PC - 2, so we have to ++ make sure to mark the instruction preceding the __startcontext ++ label as .cantunwind. */ ++ .fnstart ++ .cantunwind ++ nop + ENTRY(__startcontext) + movsr0, r4 + bne PLTJMP(__setcontext) + + @ New context was 0 - exit + b PLTJMP(HIDDEN_JUMPTARGET(exit)) ++ .fnend + END(__startcontext) + + #ifdef PIC diff --git a/meta/recipes-core/glibc/glibc_2.23.bb b/meta/recipes-core/glibc/glibc_2.23.bb index 85b5215..3844587 100644 --- a/meta/recipes-core/glibc/glibc_2.23.bb +++ b/meta/recipes-core/glibc/glibc_2.23.bb @@ -41,6 +41,7 @@ SRC_URI = "${GLIBC_GIT_URI};branch=${SRCBRANCH};name=glibc \ file://CVE-2016-1234.patch \ file://CVE-2016-3075.patch \ file://CVE-2016-5417.patch \ + file://CVE-2016-6323.patch \ " SRC_URI += "\ -- 2.1.4 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] openssl: Fix symlink creation
On mercredi 19 avril 2017 13:57:40 CEST Alexander Kanavin wrote: > On 04/19/2017 02:53 PM, David Vincent wrote: > >> This kind of thing is better done via ROOTFS_POSTPROCESS_COMMAND, I > >> think. Look for examples in rootfs-postcommands.bbclass. > > > > The problem of ROOTFS_POSTPROCESS_COMMAND is that it is a one shot > > function > > that is run at image creation. In my case, I must be able to upgrade the > > package over time via package management tools. Sorry for not bringing > > that up before. > > What is it in the openssl config file that must be managed via package > updates? The problem is that I must be able to manage the configuration of a machine without physical intervention and only via package upgrades. A new configuration can be applied simply by incrementing the PR of a configuration package. But maybe this is a use case only needed by me and I should manage it in my own specific layer ? Now that I think of it, I have the same kind of problem for all machine specific configurations. For now, I just replace the PACKAGE_ARCH in my BSP layer with a machine specific one to indicate that a package contains a configuration valid only for a specific machine. Maybe, in a future release, it should be desirable to create -conf packages based on the CONFFILES variable ? I don't know if it's a good idea, but maybe I could bring that up on the architecture mailing list ? > > Alex David -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] openssl: Fix symlink creation
On 04/19/2017 02:57 PM, Alexander Kanavin wrote: On 04/19/2017 02:53 PM, David Vincent wrote: This kind of thing is better done via ROOTFS_POSTPROCESS_COMMAND, I think. Look for examples in rootfs-postcommands.bbclass. The problem of ROOTFS_POSTPROCESS_COMMAND is that it is a one shot function that is run at image creation. In my case, I must be able to upgrade the package over time via package management tools. Sorry for not bringing that up before. What is it in the openssl config file that must be managed via package updates? I mean, if you need to perform a customization to openssl.cnf, why not patch it in the source tree via openssl.bbappend? Alex -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 3/5] libtirpc: Enable des APIs for musl
On 19 April 2017 at 09:57, André Draszikwrote: > This patch is being removed with this change, and so uclibc builds will > fail. Is it time to remove all remaining references to uclibc? > Yes! Ross -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] openssl: Fix symlink creation
On 04/19/2017 02:53 PM, David Vincent wrote: This kind of thing is better done via ROOTFS_POSTPROCESS_COMMAND, I think. Look for examples in rootfs-postcommands.bbclass. The problem of ROOTFS_POSTPROCESS_COMMAND is that it is a one shot function that is run at image creation. In my case, I must be able to upgrade the package over time via package management tools. Sorry for not bringing that up before. What is it in the openssl config file that must be managed via package updates? Alex -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] openssl: Fix symlink creation
On mercredi 19 avril 2017 12:21:18 CEST Alexander Kanavin wrote: > On 04/19/2017 11:27 AM, David Vincent wrote: > > The package is then chosen during image creation based on some > > MACHINE_FEATURES, i.e. if the machine provides a crypto accelerator to use > > instead of relying on software implementations. I hope that these new > > details will help you understand what I was trying to achieve. > > This kind of thing is better done via ROOTFS_POSTPROCESS_COMMAND, I > think. Look for examples in rootfs-postcommands.bbclass. The problem of ROOTFS_POSTPROCESS_COMMAND is that it is a one shot function that is run at image creation. In my case, I must be able to upgrade the package over time via package management tools. Sorry for not bringing that up before. > > Alex David -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] openssl: Fix symlink creation
On 04/19/2017 11:27 AM, David Vincent wrote: The package is then chosen during image creation based on some MACHINE_FEATURES, i.e. if the machine provides a crypto accelerator to use instead of relying on software implementations. I hope that these new details will help you understand what I was trying to achieve. This kind of thing is better done via ROOTFS_POSTPROCESS_COMMAND, I think. Look for examples in rootfs-postcommands.bbclass. Alex -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [meta-oe][PATCH 1/1] autogen-native: Set POSIX_SHELL to /bin/sh
Setting POSIX_SHELL to "/usr/bin/env sh" fails when tested in libopts.m4 with test -x "$POSIX_SHELL". This patch sets the POSIX_SHELL variable to "/bin/sh". Signed-off-by: Gabriel Ionescu--- meta/recipes-devtools/autogen/autogen-native_5.18.12.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-devtools/autogen/autogen-native_5.18.12.bb b/meta/recipes-devtools/autogen/autogen-native_5.18.12.bb index 853477c..9be03fc 100644 --- a/meta/recipes-devtools/autogen/autogen-native_5.18.12.bb +++ b/meta/recipes-devtools/autogen/autogen-native_5.18.12.bb @@ -31,7 +31,7 @@ inherit autotools texinfo native pkgconfig export GUILE_LOAD_PATH = "${STAGING_DATADIR_NATIVE}/guile/2.0" export GUILE_LOAD_COMPILED_PATH = "${STAGING_LIBDIR_NATIVE}/guile/2.0/ccache" -export POSIX_SHELL = "/usr/bin/env sh" +export POSIX_SHELL = "/bin/sh" do_install_append () { create_wrapper ${D}/${bindir}/autogen \ -- 2.7.4 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] Yocto cups serial port support
Hi, Generally, cups serial backend is supported by “cups-filter” package. You can find that package in the “meta-printing” layer: https://github.com/rossburton/meta-printing Hope this helps, Maxin From: openembedded-core-boun...@lists.openembedded.org [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of Weng Josn Sent: Tuesday, April 18, 2017 3:25 PM To: yo...@yoctoproject.org; openembedded-de...@lists.openembedded.org; Patches and discussions about the oe-core layerSubject: [OE-core] Yocto cups serial port support Hello, I checked /usr/lib/cups/backend not inclued "serial" backend. How can enable cups serial port ? Thanks. -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/3] runqemu: fix incorrect calls to get variable values
Sorry, this should be my fault, this fix is fine to me. // Robert On 04/19/2017 04:57 PM, Paul Eggleton wrote: We were specifying a default parameter; the get() function defined here does not take such a parameter. I appears this code had not been tested. This fixes runqemu erroring out immediately when used within the eSDK. Signed-off-by: Paul Eggleton--- scripts/runqemu | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/runqemu b/scripts/runqemu index 3744c67..605bcf2 100755 --- a/scripts/runqemu +++ b/scripts/runqemu @@ -732,8 +732,8 @@ class BaseConfig(object): # be able to call `bitbake -e`, then try: # - get OE_TMPDIR from environment and guess paths based on it # - get OECORE_NATIVE_SYSROOT from environment (for sdk) -tmpdir = self.get('OE_TMPDIR', None) -oecore_native_sysroot = self.get('OECORE_NATIVE_SYSROOT', None) +tmpdir = self.get('OE_TMPDIR') +oecore_native_sysroot = self.get('OECORE_NATIVE_SYSROOT') if tmpdir: logger.info('Setting STAGING_DIR_NATIVE and STAGING_BINDIR_NATIVE relative to OE_TMPDIR (%s)' % tmpdir) hostos, _, _, _, machine = os.uname() -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 3/5] libtirpc: Enable des APIs for musl
On Tue, 2017-04-18 at 18:58 -0700, Khem Raj wrote: > Use memset() API instead of __bzero() > Drop the patch removing des_* functions for musl > > Signed-off-by: Khem Raj> --- > .../0001-replace-__bzero-with-memset-API.patch | 28 + > .../libtirpc/remove-des-functionality.patch| 139 > - > meta/recipes-extended/libtirpc/libtirpc_1.0.1.bb | 5 +- > 3 files changed, 31 insertions(+), 141 deletions(-) > create mode 100644 meta/recipes-extended/libtirpc/libtirpc/0001-replace- > __bzero-with-memset-API.patch > delete mode 100644 meta/recipes-extended/libtirpc/libtirpc/remove-des- > functionality.patch > > [...] > > > SRC_URI_append_libc-uclibc = " file://remove-des-functionality.patch \ This patch is being removed with this change, and so uclibc builds will fail. Is it time to remove all remaining references to uclibc? Cheers, Andre' -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/3] eSDK / runqemu fixes
The following changes since commit ba2884f6ad3a4e746fc80cbd707f83fa8abd4210: oe-run-native: print more error messages (2017-04-14 10:26:10 +0100) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib paule/esdk-runqemu-fixes http://cgit.openembedded.org/openembedded-core-contrib/log/?h=paule/esdk-runqemu-fixes Paul Eggleton (3): runqemu: fix incorrect calls to get variable values classes/populate_sdk_ext: work around runqemu behaviour within the eSDK ext-sdk-prepare.py: use quiet mode when preparing sysroot meta/classes/populate_sdk_ext.bbclass | 2 ++ meta/files/ext-sdk-prepare.py | 2 +- scripts/runqemu | 4 ++-- 3 files changed, 5 insertions(+), 3 deletions(-) -- 2.9.3 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 3/3] ext-sdk-prepare.py: use quiet mode when preparing sysroot
In order to have a shared sysroot usable within the eSDK after recipe specific sysroots were implemented, we need to run bitbake build-sysroots as a separate call. However, unlike the first call, --quiet wasn't being specified and that somewhat undermined the earlier effort to clean up the eSDK installation output. Make this second call quiet as well so that the output is tidier. Signed-off-by: Paul Eggleton--- meta/files/ext-sdk-prepare.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/files/ext-sdk-prepare.py b/meta/files/ext-sdk-prepare.py index ef09639..96c5212 100644 --- a/meta/files/ext-sdk-prepare.py +++ b/meta/files/ext-sdk-prepare.py @@ -54,7 +54,7 @@ def main(): ret = run_command_interruptible('BB_SETSCENE_ENFORCE=1 bitbake --quiet %s' % ' '.join(sdk_targets)) if not ret: -ret = run_command_interruptible('bitbake build-sysroots') +ret = run_command_interruptible('bitbake --quiet build-sysroots') lastlog = get_last_consolelog() if lastlog: with open(lastlog, 'r') as f: -- 2.9.3 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 2/3] classes/populate_sdk_ext: work around runqemu behaviour within the eSDK
Currently, in order to figure out variable values when run within the eSDK, runqemu does not use the standard SDK method nor is it able to run bitbake (since the eSDK environment isn't initialised like the normal OE build environment). runqemu really ought to be fixed, but the quick workaround is to set DEPLOY_DIR_IMAGE in the environment so that runqemu can find image files. Fixes [YOCTO #10447]. Signed-off-by: Paul Eggleton--- meta/classes/populate_sdk_ext.bbclass | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/classes/populate_sdk_ext.bbclass b/meta/classes/populate_sdk_ext.bbclass index 3e1858c..4dfb94c 100644 --- a/meta/classes/populate_sdk_ext.bbclass +++ b/meta/classes/populate_sdk_ext.bbclass @@ -577,6 +577,8 @@ sdk_ext_postinst() { # Allow bitbake environment setup to be ran as part of this sdk. echo "export OE_SKIP_SDK_CHECK=1" >> $env_setup_script + # Work around runqemu not knowing how to get this information within the eSDK + echo "export DEPLOY_DIR_IMAGE=$target_sdk_dir/tmp/${@os.path.relpath(d.getVar('DEPLOY_DIR_IMAGE'), d.getVar('TMPDIR'))}" >> $env_setup_script # A bit of another hack, but we need this in the path only for devtool # so put it at the end of $PATH. -- 2.9.3 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/3] runqemu: fix incorrect calls to get variable values
We were specifying a default parameter; the get() function defined here does not take such a parameter. I appears this code had not been tested. This fixes runqemu erroring out immediately when used within the eSDK. Signed-off-by: Paul Eggleton--- scripts/runqemu | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/runqemu b/scripts/runqemu index 3744c67..605bcf2 100755 --- a/scripts/runqemu +++ b/scripts/runqemu @@ -732,8 +732,8 @@ class BaseConfig(object): # be able to call `bitbake -e`, then try: # - get OE_TMPDIR from environment and guess paths based on it # - get OECORE_NATIVE_SYSROOT from environment (for sdk) -tmpdir = self.get('OE_TMPDIR', None) -oecore_native_sysroot = self.get('OECORE_NATIVE_SYSROOT', None) +tmpdir = self.get('OE_TMPDIR') +oecore_native_sysroot = self.get('OECORE_NATIVE_SYSROOT') if tmpdir: logger.info('Setting STAGING_DIR_NATIVE and STAGING_BINDIR_NATIVE relative to OE_TMPDIR (%s)' % tmpdir) hostos, _, _, _, machine = os.uname() -- 2.9.3 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 2/5] libtirpc: Expose key_secretkey_is_set API
On 19 April 2017 at 02:58, Khem Rajwrote: > +-key_secret_is_set; > ++key_secretkey_is_set; > This removes key_secret_is_set, was this a typo upstream or a mistake in the patch? Ross -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] openssl: Fix symlink creation
On jeudi 13 avril 2017 10:05:29 CEST Jussi Kukkonen wrote: > Hi David, > > Just a heads-up: I will propose a revert of this patch this week unless > better ideas come up in the mean time. Sorry, I've been away last week so didn't have time to respond to your previous mails. I've seen the revert proposal but I think I could provide some heads-up to find a better solution to deal with my problem after the revert. > > I get that you have an actual problem you're solving but I don't think > postinstall is a correct solution. I'm sorry I don't have an alternative > solution ready for you: if you share your other configuration recipe and > explain how you use the two, maybe we can figure something out. This is my other recipe that installs the alternative configuration: FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" SRC_URI += "file://openssl-hwengine.cnf" do_install_append () { install -m 0644 ${WORKDIR}/openssl-hwengine.cnf ${D}${sysconfdir}/ssl/ } PACKAGES =+ "${PN}-conf-hwengine" FILES_${PN}-conf-hwengine = "${sysconfdir}/ssl/openssl-hwengine.cnf" CONFFILES_${PN}-conf-hwengine = "${sysconfdir}/ssl/openssl-hwengine.cnf" RPROVIDES_${PN}-conf-hwengine += "${PN}-conf" RCONFLICTS_${PN}-conf-hwengine += "${PN}-conf" RREPLACES_${PN}-conf-hwengine += "${PN}-conf" RDEPENDS_${PN}-conf-hwengine = "libp11-engine" RDEPENDS_${PN}-conf-hwengine_class-native = "" RDEPENDS_${PN}-conf-hwengine_class-nativesdk = "" pkg_postinst_${PN}-conf-hwengine () { #!/bin/sh if [ -e $D${libdir}/ssl/openssl.cnf ]; then rm -f $D${libdir}/ssl/openssl.cnf fi # If openssl-conf is installed before openssl, we must ensure that the symlink # destination exists mkdir -p $D${libdir}/ssl/ ln -s ${sysconfdir}/ssl/openssl-hwengine.cnf $D${libdir}/ssl/openssl.cnf } The package is then chosen during image creation based on some MACHINE_FEATURES, i.e. if the machine provides a crypto accelerator to use instead of relying on software implementations. I hope that these new details will help you understand what I was trying to achieve. > > Jussi > David -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] cmake.bbclass: Set CMAKE_CROSSCOMPILING correctly
On 19 April 2017 at 04:45, Kyle Russellwrote: > Thank you. Do I need to submit an amended patch to the mailing list, or > will your fixup get merged in from your staging branch pending no problems? > Don't worry about it, I've fixed it. Ross -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/1][V2] libsdl2: backport patch to fix build failures on powerpc
From: Kai KangI didn't find out this patch, so add a gcc option in V1. Thanks for Ross's help. The following changes since commit def638ebd69cef217ca567352bc08920b79ca03d: poky.ent: Removed "python3-expect" package from 3 distros. (2017-04-18 15:51:44 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib kangkai/libsdl2 http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kangkai/libsdl2 Kai Kang (1): libsdl2: fix build failures on powerpc .../libsdl2/libsdl2/fix-build-failure-on-ppc.patch | 50 ++ meta/recipes-graphics/libsdl2/libsdl2_2.0.5.bb | 1 + 2 files changed, 51 insertions(+) create mode 100644 meta/recipes-graphics/libsdl2/libsdl2/fix-build-failure-on-ppc.patch -- 2.10.1 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/1] libsdl2: fix build failures on powerpc
From: Kai KangBackport patch from upstream to fix build failures on ppc and ppc64. Signed-off-by: Kai Kang --- .../libsdl2/libsdl2/fix-build-failure-on-ppc.patch | 50 ++ meta/recipes-graphics/libsdl2/libsdl2_2.0.5.bb | 1 + 2 files changed, 51 insertions(+) create mode 100644 meta/recipes-graphics/libsdl2/libsdl2/fix-build-failure-on-ppc.patch diff --git a/meta/recipes-graphics/libsdl2/libsdl2/fix-build-failure-on-ppc.patch b/meta/recipes-graphics/libsdl2/libsdl2/fix-build-failure-on-ppc.patch new file mode 100644 index 000..1520bcf --- /dev/null +++ b/meta/recipes-graphics/libsdl2/libsdl2/fix-build-failure-on-ppc.patch @@ -0,0 +1,50 @@ +Upstream-Status: Backport [https://hg.libsdl.org/SDL/rev/5184186d4366] + +Backport patch from upstream to fix build failures on ppc and ppc64. + +Signed-off-by: Kai Kang +--- +# HG changeset patch +# User Sam Lantinga +# Date 1477159315 25200 +# Node ID 5184186d4366169617b434f5b71c618a7035cde4 +# Parent 71d4148e32de5088c4bc2f04c1e5ded647a2bf82 +Fixed bug 3466 - Can't build 2.0.5 on ppc64 + +/home/fedora/SDL2-2.0.5/src/video/SDL_blit_N.c: In function 'calc_swizzle32': +/home/fedora/SDL2-2.0.5/src/video/SDL_blit_N.c:127:5: error: ISO C90 forbids mixed declarations and code [-Werror=declaration-after-statement] + const vector unsigned char plus = VECUINT8_LITERAL(0x00, 0x00, 0x00, 0x00, + ^ + +diff -r 71d4148e32de -r 5184186d4366 src/video/SDL_blit_N.c +--- a/src/video/SDL_blit_N.c Wed Oct 19 21:22:42 2016 -0700 b/src/video/SDL_blit_N.c Sat Oct 22 11:01:55 2016 -0700 +@@ -118,12 +118,6 @@ + 16, 8, 0, 24, + 0, NULL + }; +-if (!srcfmt) { +-srcfmt = _pixel_format; +-} +-if (!dstfmt) { +-dstfmt = _pixel_format; +-} + const vector unsigned char plus = VECUINT8_LITERAL(0x00, 0x00, 0x00, 0x00, +0x04, 0x04, 0x04, 0x04, +0x08, 0x08, 0x08, 0x08, +@@ -136,6 +130,14 @@ + Uint32 gmask = RESHIFT(srcfmt->Gshift) << (dstfmt->Gshift); + Uint32 bmask = RESHIFT(srcfmt->Bshift) << (dstfmt->Bshift); + Uint32 amask; ++ ++if (!srcfmt) { ++srcfmt = _pixel_format; ++} ++if (!dstfmt) { ++dstfmt = _pixel_format; ++} ++ + /* Use zero for alpha if either surface doesn't have alpha */ + if (dstfmt->Amask) { + amask = + diff --git a/meta/recipes-graphics/libsdl2/libsdl2_2.0.5.bb b/meta/recipes-graphics/libsdl2/libsdl2_2.0.5.bb index d747cf1..12d3aaf 100644 --- a/meta/recipes-graphics/libsdl2/libsdl2_2.0.5.bb +++ b/meta/recipes-graphics/libsdl2/libsdl2_2.0.5.bb @@ -19,6 +19,7 @@ SRC_URI = " \ file://linkage.patch \ file://0001-prepend-our-sysroot-path-so-that-make-finds-our-wayl.patch \ file://0002-Avoid-finding-build-host-s-wayland-scanner.patch \ +file://fix-build-failure-on-ppc.patch \ " S = "${WORKDIR}/SDL2-${PV}" -- 2.10.1 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core