[OE-core] [PATCH] kernel-yocto: check git config during checkout
Initialize the git config prior creating a git repository in a plain directory. Signed-off-by: Justin Bronder--- meta/classes/kernel-yocto.bbclass | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass index 60979a218f..0eb631cfb1 100644 --- a/meta/classes/kernel-yocto.bbclass +++ b/meta/classes/kernel-yocto.bbclass @@ -247,6 +247,7 @@ do_kernel_checkout() { fi rm -f .gitignore git init + check_git_config git add . git commit -q -m "baseline commit: creating repo for ${PN}-${PV}" git clean -d -f -- 2.13.6 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] kernel-yocto: create dummy git user if necessary
On 09/02/18 15:27 -0500, Bruce Ashfield wrote: > On Fri, Feb 9, 2018 at 2:53 PM, Justin Bronder> wrote: > > The user's global git configuration may not have the name and email set > > and git autodetection can fail. The initialization commit for a non-git > > kernel directory doesn't really need to be tied back to them anyways. > > Instead, create a user and email that's clearly tied back to > > kernel-yocto.bbclass. > > > > Signed-off-by: Justin Bronder > > --- > > meta/classes/kernel-yocto.bbclass | 2 ++ > > 1 file changed, 2 insertions(+) > > > > diff --git a/meta/classes/kernel-yocto.bbclass > > b/meta/classes/kernel-yocto.bbclass > > index 60979a218f..dbf01f86b6 100644 > > --- a/meta/classes/kernel-yocto.bbclass > > +++ b/meta/classes/kernel-yocto.bbclass > > @@ -247,6 +247,8 @@ do_kernel_checkout() { > > fi > > rm -f .gitignore > > git init > > + git config user.name 'Yocto Kernel Git Initializer' > > + git config user.email 'kernel-yocto.bbclass@invalid' > > > This is already handled in the utility classes via the > check_git_config routine and it is called in > kernel-yocto's do_patch routine. > > If it is needed earlier (as it appears it is), move that call to > do_kernel_checkout. Ah, didn't see that. Thanks. I'll send a new patch shortly. -- Justin Bronder -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] kernel-yocto: create dummy git user if necessary
On Fri, Feb 9, 2018 at 2:53 PM, Justin Bronderwrote: > The user's global git configuration may not have the name and email set > and git autodetection can fail. The initialization commit for a non-git > kernel directory doesn't really need to be tied back to them anyways. > Instead, create a user and email that's clearly tied back to > kernel-yocto.bbclass. > > Signed-off-by: Justin Bronder > --- > meta/classes/kernel-yocto.bbclass | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/meta/classes/kernel-yocto.bbclass > b/meta/classes/kernel-yocto.bbclass > index 60979a218f..dbf01f86b6 100644 > --- a/meta/classes/kernel-yocto.bbclass > +++ b/meta/classes/kernel-yocto.bbclass > @@ -247,6 +247,8 @@ do_kernel_checkout() { > fi > rm -f .gitignore > git init > + git config user.name 'Yocto Kernel Git Initializer' > + git config user.email 'kernel-yocto.bbclass@invalid' This is already handled in the utility classes via the check_git_config routine and it is called in kernel-yocto's do_patch routine. If it is needed earlier (as it appears it is), move that call to do_kernel_checkout. Bruce > git add . > git commit -q -m "baseline commit: creating repo for > ${PN}-${PV}" > git clean -d -f > -- > 2.13.6 > > -- > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] ✗ patchtest: failure for gstd: Add Gst-Deamon recipe
== Series Details == Series: gstd: Add Gst-Deamon recipe Revision: 1 URL : https://patchwork.openembedded.org/series/10918/ 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: * Issue A patch file has been added, but does not have a Signed-off-by tag [test_signed_off_by_presence] Suggested fixSign off the added patch file (meta-multimedia/recipes-multimedia/gstreamer-1.0/gstd/0001-gstd-yocto-compatibility.patch) * Issue Added patch file is missing Upstream-Status in the header [test_upstream_status_presence_format] Suggested fixAdd Upstream-Status: to the header of meta-multimedia/recipes-multimedia/gstreamer-1.0/gstd/0001-gstd-yocto-compatibility.patch Standard format Upstream-Status: Valid status Pending, Accepted, Backport, Denied, Inappropriate [reason], Submitted [where] 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] -> ...). --- Guidelines: https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines 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] kernel-yocto: create dummy git user if necessary
The user's global git configuration may not have the name and email set and git autodetection can fail. The initialization commit for a non-git kernel directory doesn't really need to be tied back to them anyways. Instead, create a user and email that's clearly tied back to kernel-yocto.bbclass. Signed-off-by: Justin Bronder--- meta/classes/kernel-yocto.bbclass | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass index 60979a218f..dbf01f86b6 100644 --- a/meta/classes/kernel-yocto.bbclass +++ b/meta/classes/kernel-yocto.bbclass @@ -247,6 +247,8 @@ do_kernel_checkout() { fi rm -f .gitignore git init + git config user.name 'Yocto Kernel Git Initializer' + git config user.email 'kernel-yocto.bbclass@invalid' git add . git commit -q -m "baseline commit: creating repo for ${PN}-${PV}" git clean -d -f -- 2.13.6 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 4/5] musl: Update to 1.1.18
On Fri, Dec 1, 2017 at 4:41 PM, Andre McCurdywrote: > On Fri, Dec 1, 2017 at 4:37 PM, Khem Raj wrote: >> On Fri, Dec 1, 2017 at 4:31 PM, Andre McCurdy wrote: >>> On Wed, Nov 8, 2017 at 5:58 PM, Khem Raj wrote: Rich Felker (9): fix access by setjmp and longjmp to __hwcap on arm built as thumb2 for executing init array functions, use function type with prototype fix read-after-free type error in pthread_detach fix incorrect base name offset from nftw when pathname ends in slash(es) in dns parsing callback, enforce MAXADDRS to preclude overflow release 1.1.17 fix regression in glob with literal . or .. path component fix build regression on ARM for ISA levels less than v5 release 1.1.18 Szabolcs Nagy (1): math: rewrite fma with mostly int arithmetics Will Dietz (1): posix_spawn: use larger stack to cover worst-case in execvpe >>> >>> With the version of musl currently included in rocko, various apps >>> (including bash) segfault at startup when compiled as Thumb2. The "fix >>> access by setjmp and longjmp to __hwcap on arm built as thumb2" commit >>> from musl 1.1.18 fixes that. >>> >>> However the other changes in musl 1.1.18 look pretty useful too, so >>> unless there's strong objection, I'd like to suggest aligning rocko >>> with the musl 1.1.18 release. ie cherry-picking the following two >>> commits from oe-core master to rocko: >>> >>> c3f0a70 musl: Update to 1.1.18 >>> 3953c54 musl: Update to latest >> >> It seems good to me. Please send a pull and CC Armin > > Armin, please consider the following two commits for rocko: > > c3f0a70 musl: Update to 1.1.18 > 3953c54 musl: Update to latest Ping. Any comments Armin? -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [meta-oe][PATCH v2] gstd: Add Gst-Deamon recipe
GStreamer Daemon, also called gstd, is a GStreamer framework for controlling audio and video streaming using TCP connection messages. Qt applications, web interfaces, and GStreamer element test suites show different ways the framework can be utilized. GStreamer Daemon is gst-launch on steroids where you can create a GStreamer pipeline, play, pause, change speed, skip around, and even change element parameter settings all while the pipeline is active. Signed-off-by: Carlos Rodriguez--- .../recipes-multimedia/gstreamer-1.0/gstd.inc | 25 + .../gstd/0001-gstd-yocto-compatibility.patch | 63 ++ .../recipes-multimedia/gstreamer-1.0/gstd_1.0.bb | 3 ++ 3 files changed, 91 insertions(+) create mode 100644 meta-multimedia/recipes-multimedia/gstreamer-1.0/gstd.inc create mode 100644 meta-multimedia/recipes-multimedia/gstreamer-1.0/gstd/0001-gstd-yocto-compatibility.patch create mode 100644 meta-multimedia/recipes-multimedia/gstreamer-1.0/gstd_1.0.bb diff --git a/meta-multimedia/recipes-multimedia/gstreamer-1.0/gstd.inc b/meta-multimedia/recipes-multimedia/gstreamer-1.0/gstd.inc new file mode 100644 index 000..3e23521 --- /dev/null +++ b/meta-multimedia/recipes-multimedia/gstreamer-1.0/gstd.inc @@ -0,0 +1,25 @@ +DESCRIPTION = "RidgeRun Gstreamer Daemon 1.0" +SUMMARY = "GStreamer framework for controlling audio and video streaming using TCP connection messages" +HOMEPAGE = "https://developer.ridgerun.com/wiki/index.php?title=Gstd-1.0; +SECTION = "multimedia" +LICENSE = "GPLv2+" + +DEPENDS = "gstreamer1.0 gstreamer1.0-plugins-base gstreamer1.0-plugins-bad gstreamer1.0-rtsp-server json-glib libdaemon" + +SRCBRANCH ?= "master" +SRCREV = "097a086a8606dcb368c7d38c7ec4fefc2497401b" +SRC_URI = "git://g...@github.com/RidgeRun/gstd-1.x.git;protocol=https;branch=${SRCBRANCH} \ + file://0001-gstd-yocto-compatibility.patch" + +S = "${WORKDIR}/git" + +PACKAGECONFIG_CONFARGS = " \ + --disable-gtk-doc \ +" + +inherit autotools pkgconfig gettext + +do_configure() { +${S}/autogen.sh +oe_runconf +} diff --git a/meta-multimedia/recipes-multimedia/gstreamer-1.0/gstd/0001-gstd-yocto-compatibility.patch b/meta-multimedia/recipes-multimedia/gstreamer-1.0/gstd/0001-gstd-yocto-compatibility.patch new file mode 100644 index 000..ddc1831 --- /dev/null +++ b/meta-multimedia/recipes-multimedia/gstreamer-1.0/gstd/0001-gstd-yocto-compatibility.patch @@ -0,0 +1,63 @@ +From eaf51d6420c63713f62025583681007c3502d387 Mon Sep 17 00:00:00 2001 +From: Carlos +Date: Fri, 15 Dec 2017 10:14:05 -0600 +Subject: [PATCH] gstd:yocto compatibility + +--- + autogen.sh | 8 +++- + docs/reference/gstd/Makefile.am | 2 +- + gstd/Makefile.am| 2 +- + 3 files changed, 9 insertions(+), 3 deletions(-) + +diff --git a/autogen.sh b/autogen.sh +index 66dbd42..793ee2f 100755 +--- a/autogen.sh b/autogen.sh +@@ -21,7 +21,11 @@ + # ACLOCAL, AUTOPOINT and/or LIBTOOLIZE to the right versions, or leave them + # unset and get the defaults + +-gtkdocize || exit 1 ++test -n "$srcdir" || srcdir=`dirname "$0"` ++test -n "$srcdir" || srcdir=. ++ ++olddir=`pwd` ++cd "$srcdir" + + autoreconf --verbose --force --install || { + echo 'autogen.sh failed'; +@@ -31,3 +35,5 @@ autoreconf --verbose --force --install || { + echo + echo "Now run './configure' with your system settings followed by 'make' to compile this module." + echo ++ ++cd "$olddir" +diff --git a/docs/reference/gstd/Makefile.am b/docs/reference/gstd/Makefile.am +index f860fa1..153a13b 100644 +--- a/docs/reference/gstd/Makefile.am b/docs/reference/gstd/Makefile.am +@@ -66,7 +66,7 @@ GTKDOC_LIBS=$(top_builddir)/gstd/libgstd-core.la + + + # This includes the standard gtk-doc make rules, copied by gtkdocize. +-include $(top_srcdir)/docs/gtk-doc.make ++# include $(top_srcdir)/docs/gtk-doc.make + + # Comment this out if you want 'make check' to test you doc status + # and run some sanity checks +diff --git a/gstd/Makefile.am b/gstd/Makefile.am +index 13c551d..11fe202 100644 +--- a/gstd/Makefile.am b/gstd/Makefile.am +@@ -49,7 +49,7 @@ bin_PROGRAMS = gstd + + gstd_SOURCES = gstd.c + gstd_CFLAGS = $(GST_CFLAGS) $(GIO_CFLAGS) $(GJSON_CFLAGS) +-gstd_LDFLAGS = $(GST_LIBS) $(GIO_LIBS) $(GJSON_LIBS) -Wl,-rpath -Wl,$(libdir) ++gstd_LDFLAGS = $(GST_LIBS) $(GIO_LIBS) $(GJSON_LIBS) + gstd_LDADD = libgstd-core.la + + gstdincludedir = $(includedir)/gstd +-- +1.9.1 + diff --git a/meta-multimedia/recipes-multimedia/gstreamer-1.0/gstd_1.0.bb b/meta-multimedia/recipes-multimedia/gstreamer-1.0/gstd_1.0.bb new file mode 100644 index 000..94f6b57 --- /dev/null +++ b/meta-multimedia/recipes-multimedia/gstreamer-1.0/gstd_1.0.bb @@ -0,0 +1,3 @@ +require gstd.inc + +LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263" -- 1.9.1 -- ___ Openembedded-core mailing list
[OE-core] [meta-oe][PATCH v2] gst-shark: Add Gst-Shark recipe
Gst-Shark is a set of tracers used as Benchmarks and profiling tools for GStreamer. It includes tracers for generating debug information plus some tools to analyze the debug information. GstShark provides easy to use and useful tracers, paired with analysis tools to enable straightforward optimizations. Signed-off-by: Carlos Rodriguez--- .../recipes-multimedia/gstreamer-1.0/gst-shark.inc | 36 ++ .../gstreamer-1.0/gst-shark_0.2.1.bb | 3 ++ 2 files changed, 39 insertions(+) create mode 100644 meta-multimedia/recipes-multimedia/gstreamer-1.0/gst-shark.inc create mode 100644 meta-multimedia/recipes-multimedia/gstreamer-1.0/gst-shark_0.2.1.bb diff --git a/meta-multimedia/recipes-multimedia/gstreamer-1.0/gst-shark.inc b/meta-multimedia/recipes-multimedia/gstreamer-1.0/gst-shark.inc new file mode 100644 index 000..1841d30 --- /dev/null +++ b/meta-multimedia/recipes-multimedia/gstreamer-1.0/gst-shark.inc @@ -0,0 +1,36 @@ +DESCRIPTION = "RidgeRun Gst-Shark Tracers" +SUMMARY = "Benchmarks and profiling tools for GStreamer" +HOMEPAGE = "https://developer.ridgerun.com/wiki/index.php?title=GstShark; +SECTION = "multimedia" +LICENSE = "GPLv2+" + +DEPENDS = "gstreamer1.0 gstreamer1.0-plugins-base gstreamer1.0-plugins-bad " + +SRCBRANCH ?= "master" + +SRCREV_base = "a60b3996fe3376d42334fc89014e9d6f6af62899" +SRCREV_common = "b64f03f6090245624608beb5d2fff335e23a01c0" + +SRC_URI = " \ + git://g...@github.com/RidgeRun/gst-shark.git;protocol=https;branch=${SRCBRANCH};name=base \ + git://anongit.freedesktop.org/git/gstreamer/common.git;protocol=https;destsuffix=git/common;name=common; \ +" + +S = "${WORKDIR}/git" + +PACKAGECONFIG_CONFARGS = " \ + --disable-graphviz \ + --enable-gtk-doc=no \ +" + +FILES_${PN} += "\ + ${libdir}/gstreamer-1.0/libgstsharktracers.so \ + ${libdir}/gstreamer-1.0/libgstsharktracers.la \ +" + +inherit autotools gettext + +do_configure() { +${S}/autogen.sh --noconfigure +oe_runconf +} diff --git a/meta-multimedia/recipes-multimedia/gstreamer-1.0/gst-shark_0.2.1.bb b/meta-multimedia/recipes-multimedia/gstreamer-1.0/gst-shark_0.2.1.bb new file mode 100644 index 000..637bd0e --- /dev/null +++ b/meta-multimedia/recipes-multimedia/gstreamer-1.0/gst-shark_0.2.1.bb @@ -0,0 +1,3 @@ +require gst-shark.inc + +LIC_FILES_CHKSUM = "file://COPYING;md5=e1caa368743492879002ad032445fa97" \ No newline at end of file -- 1.9.1 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] gcc: backport patch to fix ICE in MIPS64 target in G++
On Fri, Feb 9, 2018 at 11:34 AM, Mark Hatlewrote: > Backport a patch to fix an ICE when compiling for MIPS64. > > Signed-off-by: Mark Hatle > --- > meta/recipes-devtools/gcc/gcc-7.3.inc | 1 + > .../gcc-7.3/0001-PR-rtl-optimization-83030.patch | 272 > + > 2 files changed, 273 insertions(+) > create mode 100644 > meta/recipes-devtools/gcc/gcc-7.3/0001-PR-rtl-optimization-83030.patch > > diff --git a/meta/recipes-devtools/gcc/gcc-7.3.inc > b/meta/recipes-devtools/gcc/gcc-7.3.inc > index 724f9c32a0..9872d81203 100644 > --- a/meta/recipes-devtools/gcc/gcc-7.3.inc > +++ b/meta/recipes-devtools/gcc/gcc-7.3.inc > @@ -77,6 +77,7 @@ SRC_URI = "\ > ${BACKPORTS} \ > " > BACKPORTS = "\ > + file://0001-PR-rtl-optimization-83030.patch \ > " > > SRC_URI[md5sum] = "be2da21680f27624f3a87055c4ba5af2" > diff --git > a/meta/recipes-devtools/gcc/gcc-7.3/0001-PR-rtl-optimization-83030.patch > b/meta/recipes-devtools/gcc/gcc-7.3/0001-PR-rtl-optimization-83030.patch > new file mode 100644 > index 00..71f7988eaa > --- /dev/null > +++ b/meta/recipes-devtools/gcc/gcc-7.3/0001-PR-rtl-optimization-83030.patch > @@ -0,0 +1,272 @@ > +From f5c4a9440f15ccf6775659910a2014a5494ee86e Mon Sep 17 00:00:00 2001 > +From: ebotcazou > +Date: Wed, 22 Nov 2017 21:43:22 + > +Subject: [PATCH] PR rtl-optimization/83030 * doc/rtl.texi (Flags > + in an RTL Expression): Alphabetize, add entry for CROSSING_JUMP_P > and > + mention usage of 'jump' for JUMP_INSNs. (Insns): Delete entry for > + REG_CROSSING_JUMP in register notes. * bb-reorder.c > + (update_crossing_jump_flags): Do not test whether the > CROSSING_JUMP_P flag > + is already set before setting it. * cfgrtl.c (fixup_partition_crossing): > + Likewise. * reorg.c (relax_delay_slots): Do not consider a > + CROSSING_JUMP_P insn as useless. > + > +git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@255083 > 138bc75d-0d04-0410-961f-82ee72b054a4 > + > +Upstream-Status: Backport > + > +This patch removes changes to Changelog from the original upstream patch. > +This will help us avoid conflicts. > + > +Original backport to GCC 7.x by Amruta Pawar > + > +Signed-off-by: Mark Hatle > + LGTM -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [rocko] Re: [PATCH] gcc: backport patch to fix ICE in MIPS64 target in G++
On 2/9/18 1:34 PM, Mark Hatle wrote: > Backport a patch to fix an ICE when compiling for MIPS64. This is also applicable to Rocko. --Mark > Signed-off-by: Mark Hatle> --- > meta/recipes-devtools/gcc/gcc-7.3.inc | 1 + > .../gcc-7.3/0001-PR-rtl-optimization-83030.patch | 272 > + > 2 files changed, 273 insertions(+) > create mode 100644 > meta/recipes-devtools/gcc/gcc-7.3/0001-PR-rtl-optimization-83030.patch > > diff --git a/meta/recipes-devtools/gcc/gcc-7.3.inc > b/meta/recipes-devtools/gcc/gcc-7.3.inc > index 724f9c32a0..9872d81203 100644 > --- a/meta/recipes-devtools/gcc/gcc-7.3.inc > +++ b/meta/recipes-devtools/gcc/gcc-7.3.inc > @@ -77,6 +77,7 @@ SRC_URI = "\ > ${BACKPORTS} \ > " > BACKPORTS = "\ > + file://0001-PR-rtl-optimization-83030.patch \ > " > > SRC_URI[md5sum] = "be2da21680f27624f3a87055c4ba5af2" > diff --git > a/meta/recipes-devtools/gcc/gcc-7.3/0001-PR-rtl-optimization-83030.patch > b/meta/recipes-devtools/gcc/gcc-7.3/0001-PR-rtl-optimization-83030.patch > new file mode 100644 > index 00..71f7988eaa > --- /dev/null > +++ b/meta/recipes-devtools/gcc/gcc-7.3/0001-PR-rtl-optimization-83030.patch > @@ -0,0 +1,272 @@ > +From f5c4a9440f15ccf6775659910a2014a5494ee86e Mon Sep 17 00:00:00 2001 > +From: ebotcazou > +Date: Wed, 22 Nov 2017 21:43:22 + > +Subject: [PATCH] PR rtl-optimization/83030 * doc/rtl.texi (Flags > + in an RTL Expression): Alphabetize, add entry for CROSSING_JUMP_P and > + mention usage of 'jump' for JUMP_INSNs. (Insns): Delete entry for > + REG_CROSSING_JUMP in register notes.* bb-reorder.c > + (update_crossing_jump_flags): Do not test whether the CROSSING_JUMP_P > flag > + is already set before setting it. * cfgrtl.c (fixup_partition_crossing): > + Likewise. * reorg.c (relax_delay_slots): Do not consider a > + CROSSING_JUMP_P insnas useless. > + > +git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@255083 > 138bc75d-0d04-0410-961f-82ee72b054a4 > + > +Upstream-Status: Backport > + > +This patch removes changes to Changelog from the original upstream patch. > +This will help us avoid conflicts. > + > +Original backport to GCC 7.x by Amruta Pawar > + > +Signed-off-by: Mark Hatle > + > +--- > + gcc/bb-reorder.c | 5 +-- > + gcc/cfgrtl.c | 3 +- > + gcc/doc/rtl.texi | 129 > --- > + gcc/reorg.c | 7 +-- > + 5 files changed, 84 insertions(+), 72 deletions(-) > + > +diff --git a/gcc/bb-reorder.c b/gcc/bb-reorder.c > +index 55e6dc6..794283c 100644 > +--- a/gcc/bb-reorder.c > b/gcc/bb-reorder.c > +@@ -2236,10 +2236,7 @@ update_crossing_jump_flags (void) > + FOR_EACH_EDGE (e, ei, bb->succs) > + if (e->flags & EDGE_CROSSING) > + { > +- if (JUMP_P (BB_END (bb)) > +- /* Some flags were added during fix_up_fall_thru_edges, via > +- force_nonfallthru_and_redirect. */ > +- && !CROSSING_JUMP_P (BB_END (bb))) > ++ if (JUMP_P (BB_END (bb))) > + CROSSING_JUMP_P (BB_END (bb)) = 1; > + break; > + } > +diff --git a/gcc/cfgrtl.c b/gcc/cfgrtl.c > +index d6e5ac0..a2ad075 100644 > +--- a/gcc/cfgrtl.c > b/gcc/cfgrtl.c > +@@ -1334,8 +1334,7 @@ fixup_partition_crossing (edge e) > + if (BB_PARTITION (e->src) != BB_PARTITION (e->dest)) > + { > + e->flags |= EDGE_CROSSING; > +- if (JUMP_P (BB_END (e->src)) > +- && !CROSSING_JUMP_P (BB_END (e->src))) > ++ if (JUMP_P (BB_END (e->src))) > + CROSSING_JUMP_P (BB_END (e->src)) = 1; > + } > + else if (BB_PARTITION (e->src) == BB_PARTITION (e->dest)) > +diff --git a/gcc/doc/rtl.texi b/gcc/doc/rtl.texi > +index 21524f5..a58eedc 100644 > +--- a/gcc/doc/rtl.texi > b/gcc/doc/rtl.texi > +@@ -565,6 +565,16 @@ that are used in certain types of expression. Most > often they > + are accessed with the following macros, which expand into lvalues. > + > + @table @code > ++@findex CROSSING_JUMP_P > ++@cindex @code{jump_insn} and @samp{/j} > ++@item CROSSING_JUMP_P (@var{x}) > ++Nonzero in a @code{jump_insn} if it crosses between hot and cold sections, > ++which could potentially be very far apart in the executable. The presence > ++of this flag indicates to other optimizations that this branching > instruction > ++should not be ``collapsed'' into a simpler branching construct. It is used > ++when the optimization to partition basic blocks into hot and cold sections > ++is turned on. > ++ > + @findex CONSTANT_POOL_ADDRESS_P > + @cindex @code{symbol_ref} and @samp{/u} > + @cindex @code{unchanging}, in @code{symbol_ref} > +@@ -577,37 +587,6 @@ In either case GCC assumes these addresses can be > addressed directly, > + perhaps with the help of base registers. > + Stored in the @code{unchanging} field and printed as @samp{/u}. > + >
[OE-core] [PATCH] gcc: backport patch to fix ICE in MIPS64 target in G++
Backport a patch to fix an ICE when compiling for MIPS64. Signed-off-by: Mark Hatle--- meta/recipes-devtools/gcc/gcc-7.3.inc | 1 + .../gcc-7.3/0001-PR-rtl-optimization-83030.patch | 272 + 2 files changed, 273 insertions(+) create mode 100644 meta/recipes-devtools/gcc/gcc-7.3/0001-PR-rtl-optimization-83030.patch diff --git a/meta/recipes-devtools/gcc/gcc-7.3.inc b/meta/recipes-devtools/gcc/gcc-7.3.inc index 724f9c32a0..9872d81203 100644 --- a/meta/recipes-devtools/gcc/gcc-7.3.inc +++ b/meta/recipes-devtools/gcc/gcc-7.3.inc @@ -77,6 +77,7 @@ SRC_URI = "\ ${BACKPORTS} \ " BACKPORTS = "\ + file://0001-PR-rtl-optimization-83030.patch \ " SRC_URI[md5sum] = "be2da21680f27624f3a87055c4ba5af2" diff --git a/meta/recipes-devtools/gcc/gcc-7.3/0001-PR-rtl-optimization-83030.patch b/meta/recipes-devtools/gcc/gcc-7.3/0001-PR-rtl-optimization-83030.patch new file mode 100644 index 00..71f7988eaa --- /dev/null +++ b/meta/recipes-devtools/gcc/gcc-7.3/0001-PR-rtl-optimization-83030.patch @@ -0,0 +1,272 @@ +From f5c4a9440f15ccf6775659910a2014a5494ee86e Mon Sep 17 00:00:00 2001 +From: ebotcazou +Date: Wed, 22 Nov 2017 21:43:22 + +Subject: [PATCH] PR rtl-optimization/83030 * doc/rtl.texi (Flags + in an RTL Expression): Alphabetize, add entry for CROSSING_JUMP_P and + mention usage of 'jump' for JUMP_INSNs. (Insns): Delete entry for + REG_CROSSING_JUMP in register notes. * bb-reorder.c + (update_crossing_jump_flags): Do not test whether the CROSSING_JUMP_P flag + is already set before setting it. * cfgrtl.c (fixup_partition_crossing): + Likewise. * reorg.c (relax_delay_slots): Do not consider a + CROSSING_JUMP_P insn as useless. + +git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@255083 138bc75d-0d04-0410-961f-82ee72b054a4 + +Upstream-Status: Backport + +This patch removes changes to Changelog from the original upstream patch. +This will help us avoid conflicts. + +Original backport to GCC 7.x by Amruta Pawar + +Signed-off-by: Mark Hatle + +--- + gcc/bb-reorder.c | 5 +-- + gcc/cfgrtl.c | 3 +- + gcc/doc/rtl.texi | 129 --- + gcc/reorg.c | 7 +-- + 5 files changed, 84 insertions(+), 72 deletions(-) + +diff --git a/gcc/bb-reorder.c b/gcc/bb-reorder.c +index 55e6dc6..794283c 100644 +--- a/gcc/bb-reorder.c b/gcc/bb-reorder.c +@@ -2236,10 +2236,7 @@ update_crossing_jump_flags (void) + FOR_EACH_EDGE (e, ei, bb->succs) + if (e->flags & EDGE_CROSSING) + { +-if (JUMP_P (BB_END (bb)) +-/* Some flags were added during fix_up_fall_thru_edges, via +- force_nonfallthru_and_redirect. */ +-&& !CROSSING_JUMP_P (BB_END (bb))) ++if (JUMP_P (BB_END (bb))) + CROSSING_JUMP_P (BB_END (bb)) = 1; + break; + } +diff --git a/gcc/cfgrtl.c b/gcc/cfgrtl.c +index d6e5ac0..a2ad075 100644 +--- a/gcc/cfgrtl.c b/gcc/cfgrtl.c +@@ -1334,8 +1334,7 @@ fixup_partition_crossing (edge e) + if (BB_PARTITION (e->src) != BB_PARTITION (e->dest)) + { + e->flags |= EDGE_CROSSING; +- if (JUMP_P (BB_END (e->src)) +-&& !CROSSING_JUMP_P (BB_END (e->src))) ++ if (JUMP_P (BB_END (e->src))) + CROSSING_JUMP_P (BB_END (e->src)) = 1; + } + else if (BB_PARTITION (e->src) == BB_PARTITION (e->dest)) +diff --git a/gcc/doc/rtl.texi b/gcc/doc/rtl.texi +index 21524f5..a58eedc 100644 +--- a/gcc/doc/rtl.texi b/gcc/doc/rtl.texi +@@ -565,6 +565,16 @@ that are used in certain types of expression. Most often they + are accessed with the following macros, which expand into lvalues. + + @table @code ++@findex CROSSING_JUMP_P ++@cindex @code{jump_insn} and @samp{/j} ++@item CROSSING_JUMP_P (@var{x}) ++Nonzero in a @code{jump_insn} if it crosses between hot and cold sections, ++which could potentially be very far apart in the executable. The presence ++of this flag indicates to other optimizations that this branching instruction ++should not be ``collapsed'' into a simpler branching construct. It is used ++when the optimization to partition basic blocks into hot and cold sections ++is turned on. ++ + @findex CONSTANT_POOL_ADDRESS_P + @cindex @code{symbol_ref} and @samp{/u} + @cindex @code{unchanging}, in @code{symbol_ref} +@@ -577,37 +587,6 @@ In either case GCC assumes these addresses can be addressed directly, + perhaps with the help of base registers. + Stored in the @code{unchanging} field and printed as @samp{/u}. + +-@findex RTL_CONST_CALL_P +-@cindex @code{call_insn} and @samp{/u} +-@cindex @code{unchanging}, in @code{call_insn} +-@item RTL_CONST_CALL_P (@var{x}) +-In a @code{call_insn} indicates that the insn represents a call to a +-const function. Stored in the @code{unchanging} field and printed as +-@samp{/u}. +-
Re: [OE-core] [PATCH 1/2] gtk-doc: update to 1.27
On Friday, February 9, 2018 2:03:01 AM EST Alexander Kanavin wrote: > On 02/09/2018 12:13 AM, Mark Asselstine wrote: > > The use of libunique is non-consequential here. The issue is that the > > gtk-doc package has imports which are not going to be present via direct > > runtime dependencies. Any sw which attempts to run the python scripts > > found in gtk-doc will fail in the same way unless the python3-six is > > installed via an indirect dependency. I didn't have a chance to dig in to > > this deeper today so I don't have more to add than this but the "import > > six" is pretty explicit and will fail unless this script is not meant to > > actually be run anytime, anywhere. > gtk-doc recipe does have a direct dependency on python3-six, subject to > 'api-documentation' in DISTRO_FEATURES. The reason it's conditional is > that we don't want to build a ton of gtk-doc dependencies in the default > case that used by almost everyone. Yes, this produces gtk-doc scripts > that are not working, but they will not be run anyway, if gtk-doc > capable recipes inherit the gtk-doc class, which will disable the > gtk-doc feature. libunique was missing that inherit, the patch to fix > that is now on oe-devl list. Take it and the issue will go away. Thanks for sending out the updates, I am giving them a go. I wasn't clear about the intention based on your initial change so glad I reached out to you and that this will move on. Thanks again, Mark > > Alex -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] Cherry-pick postinstallation script refactoring to rocko
Recently, the mechanism for defining post installation scripts that have to run on the first boot (on the target) was refactored in the following commits: ff4835470bc4 rootfs.py: change the notice about deferring scripts to first boot from warning to a note a2b7260f791e package_rpm.bbclass: run pre/post installation scriptlets using sh -e 7bc55b296097 meta/lib/oe/package_manager.py: deprecate 'exit 1' as a way to defer to first boot 6ca669105ff7 package.bbclass: add support for pkg_postinst_ontarget() 32c500b8ea2c meta/lib/oe/rootfs.py: do not execute defer_to_first_boot when processing postinst_intercept hooks 4c808e31ea35 meta/lib/oe/rootfs.py: separate first boot deferral logic into a separate function This makes it easier and clearer to define post installation scripts that have to run on the target, and it also clears the warnings that you currently get in rocko when trying to define post installation scripts that have to run on the target: > [log_check] warning: %post(u-boot-fw-utils-1:2017.09-r0.0.ccimx6sbc) > scriptlet failed, exit status 1 I think these warnings are quite confusing, as they seem to indicate that some scriptlet failed, when that is not the case at all. The exit status 1 is the result of the idiom (or hacky method) that you have to use in order to define post installation scripts that run on the target, as documented in rocko [1]. Note that this patchset would not break anything, it would just change confusing warnings (like shown above) to a specific warning telling users about using this new method. Would it be possible to cherry-pick this patchset to rocko, in order to fix this? Thanks. [1] http://www.yoctoproject.org/docs/2.4/mega-manual/mega-manual.html#new-recipe-post-installation-scripts -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] ltp: fix knob to control numa support
There's now two patches which do this on the list, can you decide which one should be merged? Cheers, Ross On 8 February 2018 at 17:34, Anders Roxellwrote: > Reported-by: Yi Zhao > Signed-off-by: Anders Roxell > --- > ...ix-default-value-of-without-numa-switch-i.patch | 31 ++ > ...onfigure-add-knob-to-control-numa-support.patch | 50 > ++ > ...-control-whether-numa-support-should-be-c.patch | 45 > --- > meta/recipes-extended/ltp/ltp_20180118.bb | 3 +- > 4 files changed, 83 insertions(+), 46 deletions(-) > create mode 100644 meta/recipes-extended/ltp/ltp/ > 0001-configure-Fix-default-value-of-without-numa-switch-i.patch > create mode 100644 meta/recipes-extended/ltp/ltp/ > 0001-configure-add-knob-to-control-numa-support.patch > delete mode 100644 meta/recipes-extended/ltp/ltp/ > 0002-Add-knob-to-control-whether-numa-support-should-be-c.patch > > diff --git a/meta/recipes-extended/ltp/ltp/0001-configure-Fix- > default-value-of-without-numa-switch-i.patch b/meta/recipes-extended/ltp/ > ltp/0001-configure-Fix-default-value-of-without-numa-switch-i.patch > new file mode 100644 > index 000..da62687 > --- /dev/null > +++ b/meta/recipes-extended/ltp/ltp/0001-configure-Fix- > default-value-of-without-numa-switch-i.patch > @@ -0,0 +1,31 @@ > +From 4ace68a6ba501907a0741dba5f5f155e06a74c35 Mon Sep 17 00:00:00 2001 > +From: Petr Vorel > +Date: Wed, 7 Feb 2018 11:09:49 +0100 > +Subject: [PATCH] configure: Fix default value of --without-numa switch in > help > + > +The default value is no. > + > +Fixes: 39a85a1f1 ("configure: add knob to control numa support") > + > +Signed-off-by: Petr Vorel > +Upstream-Status: Accepted > +--- > + configure.ac | 2 +- > + 1 file changed, 1 insertion(+), 1 deletion(-) > + > +diff --git a/configure.ac b/configure.ac > +index b39a31d..d66ea00 100644 > +--- a/configure.ac > b/configure.ac > +@@ -86,7 +86,7 @@ fi > + # Numa > + AC_ARG_WITH([numa], > + AC_HELP_STRING([--without-numa], > +-[without numa support (default=yes)]), > ++[without numa support (default=no)]), > + [with_numa=no], > + [with_numa=yes] > + ) > +-- > +2.7.4 > + > diff --git > a/meta/recipes-extended/ltp/ltp/0001-configure-add-knob-to-control-numa-support.patch > b/meta/recipes-extended/ltp/ltp/0001-configure-add-knob- > to-control-numa-support.patch > new file mode 100644 > index 000..8aaa287 > --- /dev/null > +++ b/meta/recipes-extended/ltp/ltp/0001-configure-add-knob- > to-control-numa-support.patch > @@ -0,0 +1,50 @@ > +From 39a85a1f1e6624f554215ba4b6843d3689a8415e Mon Sep 17 00:00:00 2001 > +From: Anders Roxell > +Date: Mon, 5 Feb 2018 11:56:04 +0100 > +Subject: [PATCH] configure: add knob to control numa support > + > +Allow to disable numa from the top level. > + > +Based on patch: > +http://cgit.openembedded.org/openembedded-core/commit/meta/ > recipes-extended/ltp?id=4c7873552e13dfdba96afca7562c398d2966ca71 > + > +Reported-by: Roy Li > +Signed-off-by: Anders Roxell > +Signed-off-by: Petr Vorel > +Upstream-Status: Accepted > +--- > + configure.ac | 10 ++ > + 1 file changed, 10 insertions(+) > + > +diff --git a/configure.ac b/configure.ac > +index 5c8d4ea..b39a31d 100644 > +--- a/configure.ac > b/configure.ac > +@@ -83,6 +83,14 @@ else > + AC_SUBST([WITH_EXPECT],["no"]) > + fi > + > ++# Numa > ++AC_ARG_WITH([numa], > ++ AC_HELP_STRING([--without-numa], > ++[without numa support (default=yes)]), > ++ [with_numa=no], > ++ [with_numa=yes] > ++) > ++ > + # Perl > + AC_ARG_WITH([perl], > + [AC_HELP_STRING([--with-perl], > +@@ -157,7 +165,9 @@ LTP_CHECK_SELINUX > + LTP_CHECK_SIGNAL > + LTP_CHECK_SYSCALL_EVENTFD > + LTP_CHECK_SYSCALL_MODIFY_LDT > ++if test "x$with_numa" = xyes; then > + LTP_CHECK_SYSCALL_NUMA > ++fi > + LTP_CHECK_SYSCALL_QUOTACTL > + LTP_CHECK_SYSCALL_SIGNALFD > + LTP_CHECK_SYSCALL_UNSHARE > +-- > +2.7.4 > + > diff --git a/meta/recipes-extended/ltp/ltp/0002-Add-knob-to-control- > whether-numa-support-should-be-c.patch b/meta/recipes-extended/ltp/ > ltp/0002-Add-knob-to-control-whether-numa-support-should-be-c.patch > deleted file mode 100644 > index 31460b9..000 > --- a/meta/recipes-extended/ltp/ltp/0002-Add-knob-to-control- > whether-numa-support-should-be-c.patch > +++ /dev/null > @@ -1,45 +0,0 @@ > -From 867ad5d5d64b9b27ee32148027532db0a00f6433 Mon Sep 17 00:00:00 2001 > -From: "Roy.Li" > -Date: Thu, 7 Jan 2016 17:33:26 + > -Subject: [PATCH 02/32] Add knob to control whether numa support should be > - checked > - > -otherwise undeterministic dependency will be generated > -during build depending upong numa being staged or not > - > -Signed-off-by: Roy.Li > -Signed-off-by: Khem Raj >
[OE-core] [PATCH] utility-tasks: Drop fetchall and checkuriall tasks
The same thing can now be done with "bitbake --runall=fetch" or "bitbake --runall=checkuri". Dropping the tasks takes "bitbake core-image-sato -g" from 22s to 8s since it no longer has to resolve the recursive dependencies (it doesn't know if any given target will touch them or not until it computes them). That is a significant enough win that its worth any impact this may have on the small number of users using the tasks. Signed-off-by: Richard Purdie--- meta/classes/utility-tasks.bbclass | 13 - 1 file changed, 13 deletions(-) diff --git a/meta/classes/utility-tasks.bbclass b/meta/classes/utility-tasks.bbclass index 587bfd4..b1f27d3 100644 --- a/meta/classes/utility-tasks.bbclass +++ b/meta/classes/utility-tasks.bbclass @@ -50,17 +50,4 @@ python do_checkuri() { bb.fatal(str(e)) } -addtask checkuriall after do_checkuri -do_checkuriall[recrdeptask] = "do_checkuriall do_checkuri" -do_checkuriall[recideptask] = "do_${BB_DEFAULT_TASK}" -do_checkuriall[nostamp] = "1" -do_checkuriall() { - : -} -addtask fetchall after do_fetch -do_fetchall[recrdeptask] = "do_fetchall do_fetch" -do_fetchall[recideptask] = "do_${BB_DEFAULT_TASK}" -do_fetchall() { - : -} -- 2.7.4 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCHv3] bmap-tools: change SRC_URI to use tarball instead
From: Chang Rebecca Swee FunTarball sources can be checksummed and are faster to download. Added UPSTREAM_CHECK_URI to improve recipe maintenance and to verify upstream version check is still work. Signed-off-by: Chang Rebecca Swee Fun --- meta/recipes-support/bmap-tools/bmap-tools_3.4.bb | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/meta/recipes-support/bmap-tools/bmap-tools_3.4.bb b/meta/recipes-support/bmap-tools/bmap-tools_3.4.bb index 70b6e91..9d8191f 100644 --- a/meta/recipes-support/bmap-tools/bmap-tools_3.4.bb +++ b/meta/recipes-support/bmap-tools/bmap-tools_3.4.bb @@ -9,10 +9,12 @@ SECTION = "console/utils" LICENSE = "GPLv2" LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263" -SRC_URI = "git://github.com/intel/bmap-tools.git" -SRCREV = "9dad724104df265442226972a1e310813f9ffcba" +SRC_URI = "https://github.com/intel/${BPN}/releases/download/v${PV}/${BP}.tgz; -S = "${WORKDIR}/git" +SRC_URI[md5sum] = "883420183611aa137cbaf68a91ef0d7e" +SRC_URI[sha256sum] = "0064891270c180c190f41925b0f6fb9cecac3056f1168d2592dbe90e5f226c0a" + +UPSTREAM_CHECK_URI = "https://github.com/intel/${BPN}/releases; RDEPENDS_${PN} = "python3-core python3-compression python3-mmap python3-setuptools" -- 2.7.4 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core