Re: [master/morty][PATCH] binutils-crosssdk: match OE-Core, use SDK_SYS suffix instead of SDK/TARGET_ARCH
Done! > Op 23 dec. 2016, om 15:06 heeft Denys Dmytriyenko <de...@denix.org> het > volgende geschreven: > > Sounds good. > Can you merge this patch to morty too, now that binutils 2.27 was > cherry-picked. Thanks! > > Denys > > PS. Phone-replying, sorry. > > > On Dec 23, 2016 03:24, Koen Kooi <koen.k...@linaro.org> wrote: > > > Op 22 dec. 2016, om 18:49 heeft Denys Dmytriyenko <de...@denix.org> het > > volgende geschreven: > > > > Thanks. > > Didn't know you now have a separate openembedded list - do you want patches > > to > > be sent there? > > Preferably yes, but we check both lists. > > -- > Koen Kooi > Builds and Baselines | Release Manager > Linaro.org | Open source software for ARM SoCs > > > > > -- > > Denys > > > > > > On Thu, Dec 22, 2016 at 02:38:47PM +0100, Koen Kooi wrote: > >> Added into gerrit: https://review.linaro.org/16545 > >> > >> > >>> Op 21 dec. 2016, om 23:10 heeft Denys Dmytriyenko <de...@denix.org> het > >>> volgende geschreven: > >>> > >>> From: Denys Dmytriyenko <de...@ti.com> > >>> > >>> OE-Core has switched to using SDK_SYS suffix for crosssdk packages, > >>> instead of > >>> SDK/TARGET_ARCH in d2eb70e809d482c493922f23aef4409cfd82 [1], update > >>> Linaro > >>> versions accordingly. > >>> > >>> [1] > >>> http://cgit.openembedded.org/openembedded-core/commit/?id=d2eb70e809d482c493922f23aef4409cfd82 > >>> > >>> > >>> Signed-off-by: Denys Dmytriyenko <de...@ti.com> > >>> --- > >>> .../recipes-devtools/binutils/binutils-crosssdk_linaro-2.25.bb | > >>> 2 +- > >>> .../recipes-devtools/binutils/binutils-crosssdk_linaro-2.27.bb | > >>> 2 +- > >>> 2 files changed, 2 insertions(+), 2 deletions(-) > >>> > >>> diff --git > >>> a/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.25.bb > >>> > >>> b/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.25.bb > >>> > >>> index 1c62ed4..6304613 100644 > >>> --- > >>> a/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.25.bb > >>> > >>> +++ > >>> b/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.25.bb > >>> > >>> @@ -2,7 +2,7 @@ require recipes-devtools/binutils/binutils-cross_${PV}.bb > >>> > >>> inherit crosssdk > >>> > >>> -PN = "binutils-crosssdk-${TARGET_ARCH}" > >>> +PN = "binutils-crosssdk-${SDK_SYS}" > >>> > >>> PROVIDES = "virtual/${TARGET_PREFIX}binutils-crosssdk" > >>> > >>> diff --git > >>> a/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.27.bb > >>> > >>> b/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.27.bb > >>> > >>> index 1c62ed4..6304613 100644 > >>> --- > >>> a/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.27.bb > >>> > >>> +++ > >>> b/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.27.bb > >>> > >>> @@ -2,7 +2,7 @@ require recipes-devtools/binutils/binutils-cross_${PV}.bb > >>> > >>> inherit crosssdk > >>> > >>> -PN = "binutils-crosssdk-${TARGET_ARCH}" > >>> +PN = "binutils-crosssdk-${SDK_SYS}" > >>> > >>> PROVIDES = "virtual/${TARGET_PREFIX}binutils-crosssdk" > >>> > >>> -- > >>> 2.7.4 > >>> > >>> ___ > >>> linaro-dev mailing list > >>> linaro-dev@lists.linaro.org > >>> https://lists.linaro.org/mailman/listinfo/linaro-dev > >> > > ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [master/morty][PATCH] binutils-crosssdk: match OE-Core, use SDK_SYS suffix instead of SDK/TARGET_ARCH
> Op 22 dec. 2016, om 18:49 heeft Denys Dmytriyenko <de...@denix.org> het > volgende geschreven: > > Thanks. > Didn't know you now have a separate openembedded list - do you want patches > to > be sent there? Preferably yes, but we check both lists. -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs > > -- > Denys > > > On Thu, Dec 22, 2016 at 02:38:47PM +0100, Koen Kooi wrote: >> Added into gerrit: https://review.linaro.org/16545 >> >> >>> Op 21 dec. 2016, om 23:10 heeft Denys Dmytriyenko <de...@denix.org> het >>> volgende geschreven: >>> >>> From: Denys Dmytriyenko <de...@ti.com> >>> >>> OE-Core has switched to using SDK_SYS suffix for crosssdk packages, instead >>> of >>> SDK/TARGET_ARCH in d2eb70e809d482c493922f23aef4409cfd82 [1], update >>> Linaro >>> versions accordingly. >>> >>> [1] >>> http://cgit.openembedded.org/openembedded-core/commit/?id=d2eb70e809d482c493922f23aef4409cfd82 >>> >>> Signed-off-by: Denys Dmytriyenko <de...@ti.com> >>> --- >>> .../recipes-devtools/binutils/binutils-crosssdk_linaro-2.25.bb | 2 >>> +- >>> .../recipes-devtools/binutils/binutils-crosssdk_linaro-2.27.bb | 2 >>> +- >>> 2 files changed, 2 insertions(+), 2 deletions(-) >>> >>> diff --git >>> a/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.25.bb >>> >>> b/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.25.bb >>> index 1c62ed4..6304613 100644 >>> --- >>> a/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.25.bb >>> +++ >>> b/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.25.bb >>> @@ -2,7 +2,7 @@ require recipes-devtools/binutils/binutils-cross_${PV}.bb >>> >>> inherit crosssdk >>> >>> -PN = "binutils-crosssdk-${TARGET_ARCH}" >>> +PN = "binutils-crosssdk-${SDK_SYS}" >>> >>> PROVIDES = "virtual/${TARGET_PREFIX}binutils-crosssdk" >>> >>> diff --git >>> a/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.27.bb >>> >>> b/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.27.bb >>> index 1c62ed4..6304613 100644 >>> --- >>> a/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.27.bb >>> +++ >>> b/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.27.bb >>> @@ -2,7 +2,7 @@ require recipes-devtools/binutils/binutils-cross_${PV}.bb >>> >>> inherit crosssdk >>> >>> -PN = "binutils-crosssdk-${TARGET_ARCH}" >>> +PN = "binutils-crosssdk-${SDK_SYS}" >>> >>> PROVIDES = "virtual/${TARGET_PREFIX}binutils-crosssdk" >>> >>> -- >>> 2.7.4 >>> >>> ___ >>> linaro-dev mailing list >>> linaro-dev@lists.linaro.org >>> https://lists.linaro.org/mailman/listinfo/linaro-dev >> ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [master/morty][PATCH] binutils-crosssdk: match OE-Core, use SDK_SYS suffix instead of SDK/TARGET_ARCH
Added into gerrit: https://review.linaro.org/16545 > Op 21 dec. 2016, om 23:10 heeft Denys Dmytriyenkohet > volgende geschreven: > > From: Denys Dmytriyenko > > OE-Core has switched to using SDK_SYS suffix for crosssdk packages, instead of > SDK/TARGET_ARCH in d2eb70e809d482c493922f23aef4409cfd82 [1], update Linaro > versions accordingly. > > [1] > http://cgit.openembedded.org/openembedded-core/commit/?id=d2eb70e809d482c493922f23aef4409cfd82 > > Signed-off-by: Denys Dmytriyenko > --- > .../recipes-devtools/binutils/binutils-crosssdk_linaro-2.25.bb | 2 +- > .../recipes-devtools/binutils/binutils-crosssdk_linaro-2.27.bb | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git > a/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.25.bb > > b/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.25.bb > index 1c62ed4..6304613 100644 > --- > a/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.25.bb > +++ > b/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.25.bb > @@ -2,7 +2,7 @@ require recipes-devtools/binutils/binutils-cross_${PV}.bb > > inherit crosssdk > > -PN = "binutils-crosssdk-${TARGET_ARCH}" > +PN = "binutils-crosssdk-${SDK_SYS}" > > PROVIDES = "virtual/${TARGET_PREFIX}binutils-crosssdk" > > diff --git > a/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.27.bb > > b/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.27.bb > index 1c62ed4..6304613 100644 > --- > a/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.27.bb > +++ > b/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.27.bb > @@ -2,7 +2,7 @@ require recipes-devtools/binutils/binutils-cross_${PV}.bb > > inherit crosssdk > > -PN = "binutils-crosssdk-${TARGET_ARCH}" > +PN = "binutils-crosssdk-${SDK_SYS}" > > PROVIDES = "virtual/${TARGET_PREFIX}binutils-crosssdk" > > -- > 2.7.4 > > ___ > linaro-dev mailing list > linaro-dev@lists.linaro.org > https://lists.linaro.org/mailman/listinfo/linaro-dev ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [master/morty/krogoth][PATCH] binutils: add lost relocatable_sdk.patch used by crosssdk 2.27 recipe
Added into gerrit: https://review.linaro.org/16537 > Op 21 dec. 2016, om 19:13 heeft Denys Dmytriyenkohet > volgende geschreven: > > From: Denys Dmytriyenko > > Signed-off-by: Denys Dmytriyenko > --- > .../binutils-linaro-2.27/relocatable_sdk.patch | 49 ++ > 1 file changed, 49 insertions(+) > create mode 100644 > meta-linaro-toolchain/recipes-devtools/binutils/binutils-linaro-2.27/relocatable_sdk.patch > > diff --git > a/meta-linaro-toolchain/recipes-devtools/binutils/binutils-linaro-2.27/relocatable_sdk.patch > > b/meta-linaro-toolchain/recipes-devtools/binutils/binutils-linaro-2.27/relocatable_sdk.patch > new file mode 100644 > index 000..7408c31 > --- /dev/null > +++ > b/meta-linaro-toolchain/recipes-devtools/binutils/binutils-linaro-2.27/relocatable_sdk.patch > @@ -0,0 +1,49 @@ > +Upstream-Status: Inappropriate [SDK specific] > + > +This patch will modify the ELF linker scripts so that the crosssdk linker > will > +generate binaries with a 4096 bytes PT_INTERP section. When the binaries will > +be relocated, at SDK install time, the interpreter path can be easily changed > +by the relocating script. > + > +Signed-off-by: Laurentiu Palcu > + > +Index: binutils_git/ld/genscripts.sh > +=== > +--- binutils_git.orig/ld/genscripts.sh 2012-11-21 11:58:23.325441925 > +0200 > binutils_git/ld/genscripts.sh2012-11-21 12:03:42.106815400 +0200 > +@@ -290,6 +290,7 @@ > + LD_FLAG=r > + DATA_ALIGNMENT=${DATA_ALIGNMENT_r} > + DEFAULT_DATA_ALIGNMENT="ALIGN(${SEGMENT_SIZE})" > ++PARTIAL_LINKING=" " > + ( echo "/* Script for ld -r: link without relocation */" > + . ${CUSTOMIZER_SCRIPT} > + . ${srcdir}/scripttempl/${SCRIPT_NAME}.sc > +@@ -298,10 +299,12 @@ > + LD_FLAG=u > + DATA_ALIGNMENT=${DATA_ALIGNMENT_u} > + CONSTRUCTING=" " > ++PARTIAL_LINKING=" " > + ( echo "/* Script for ld -Ur: link w/out relocation, do create constructors > */" > + . ${CUSTOMIZER_SCRIPT} > + . ${srcdir}/scripttempl/${SCRIPT_NAME}.sc > + ) | sed -e '/^ *$/d;s/[ ]*$//' > ldscripts/${EMULATION_NAME}.xu > ++unset PARTIAL_LINKING > + > + LD_FLAG= > + DATA_ALIGNMENT=${DATA_ALIGNMENT_} > +Index: binutils_git/ld/scripttempl/elf.sc > +=== > +--- binutils_git.orig/ld/scripttempl/elf.sc 2012-11-21 12:02:26.800377384 > +0200 > binutils_git/ld/scripttempl/elf.sc 2012-11-21 12:04:16.166109621 > +0200 > +@@ -124,8 +124,8 @@ > + DATA_SEGMENT_END=". = DATA_SEGMENT_END (.);" > + DATA_SEGMENT_RELRO_END=". = DATA_SEGMENT_RELRO_END (${SEPARATE_GOTPLT-0}, > .);" > + fi > +-if test -z "${INITIAL_READONLY_SECTIONS}${CREATE_SHLIB}"; then > +- INITIAL_READONLY_SECTIONS=".interp ${RELOCATING-0} : { *(.interp) }" > ++if test -z "${INITIAL_READONLY_SECTIONS}${CREATE_SHLIB}${PARTIAL_LINKING}"; > then > ++ INITIAL_READONLY_SECTIONS=".interp ${RELOCATING-0} : { *(.interp); > . = 0x1000; }" > + fi > + if test -z "$PLT"; then > + IPLT=".iplt ${RELOCATING-0} : { *(.iplt) }" > -- > 2.7.4 > > ___ > linaro-dev mailing list > linaro-dev@lists.linaro.org > https://lists.linaro.org/mailman/listinfo/linaro-dev ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [master/morty/krogoth][PATCH] recipes: fix SRC_URI, as releases.linaro.org moved YY.MM dirs into archive
Added into gerrit for master: https://review.linaro.org/16506 On 20 December 2016 at 02:16, Denys Dmytriyenko <de...@denix.org> wrote: > From: Denys Dmytriyenko <de...@ti.com> > > Signed-off-by: Denys Dmytriyenko <de...@ti.com> > --- > meta-linaro-toolchain/recipes-core/glibc/glibc_linaro-2.20.bb | 2 +- > meta-linaro-toolchain/recipes-devtools/gcc/gcc-linaro-4.9.inc | 2 +- > meta-linaro-toolchain/recipes-devtools/gdb/gdb-linaro-7.8.inc | 2 +- > meta-linaro/recipes-extra/powerdebug/powerdebug_0.7.3.bb | 2 +- > 4 files changed, 4 insertions(+), 4 deletions(-) > > diff --git a/meta-linaro-toolchain/recipes-core/glibc/glibc_linaro-2.20.bb > b/meta-linaro-toolchain/recipes-core/glibc/glibc_linaro-2.20.bb > index e52e734..058222e 100644 > --- a/meta-linaro-toolchain/recipes-core/glibc/glibc_linaro-2.20.bb > +++ b/meta-linaro-toolchain/recipes-core/glibc/glibc_linaro-2.20.bb > @@ -6,7 +6,7 @@ MMYY = "14.11" > RELEASE = "20${MMYY}" > PR = "r${RELEASE}" > > -SRC_URI = > "http://releases.linaro.org/${MMYY}/components/toolchain/glibc-linaro/glibc-${PV}-${RELEASE}.tar.xz > \ > +SRC_URI = > "http://releases.linaro.org/archive/${MMYY}/components/toolchain/glibc-linaro/glibc-${PV}-${RELEASE}.tar.xz > \ > file://etc/ld.so.conf \ > file://generate-supported.mk \ > file://IO-acquire-lock-fix.patch \ > diff --git a/meta-linaro-toolchain/recipes-devtools/gcc/gcc-linaro-4.9.inc > b/meta-linaro-toolchain/recipes-devtools/gcc/gcc-linaro-4.9.inc > index 1b95cd8..56fb6ca 100644 > --- a/meta-linaro-toolchain/recipes-devtools/gcc/gcc-linaro-4.9.inc > +++ b/meta-linaro-toolchain/recipes-devtools/gcc/gcc-linaro-4.9.inc > @@ -8,7 +8,7 @@ BINV = "4.9.4" > > FILESPATH = "${@base_set_filespath([ '${FILE_DIRNAME}/gcc-${PV}' ], d)}" > > -SRC_URI = > "https://releases.linaro.org/${MMYY}/components/toolchain/gcc-linaro/${BASEPV}/gcc-${PV}-${RELEASE}.tar.xz > \ > +SRC_URI = > "https://releases.linaro.org/archive/${MMYY}/components/toolchain/gcc-linaro/${BASEPV}/gcc-${PV}-${RELEASE}.tar.xz > \ > file://0001-gcc-4.3.1-ARCH_FLAGS_FOR_TARGET.patch \ > file://0002-uclibc-conf.patch \ > file://0003-gcc-uclibc-locale-ctype_touplow_t.patch \ > diff --git a/meta-linaro-toolchain/recipes-devtools/gdb/gdb-linaro-7.8.inc > b/meta-linaro-toolchain/recipes-devtools/gdb/gdb-linaro-7.8.inc > index 773fcea..4dae37d 100644 > --- a/meta-linaro-toolchain/recipes-devtools/gdb/gdb-linaro-7.8.inc > +++ b/meta-linaro-toolchain/recipes-devtools/gdb/gdb-linaro-7.8.inc > @@ -14,7 +14,7 @@ S = "${WORKDIR}/${BPN}-${PV}-${RELEASE}" > > FILESPATH = "${@base_set_filespath([ '${FILE_DIRNAME}/gdb-${BINV}' ], d)}" > > -SRC_URI = > "https://releases.linaro.org/${MMYY}/components/toolchain/gdb-linaro/gdb-${PV}-${RELEASE}.tar.xz; > +SRC_URI = > "https://releases.linaro.org/archive/${MMYY}/components/toolchain/gdb-linaro/gdb-${PV}-${RELEASE}.tar.xz; > > SRC_URI[md5sum] = "954e47e397de0b635ecdb5bb5d0f145f" > SRC_URI[sha256sum] = > "fbbe96b8d0debf7c2d8c9a4a6c7ca0ba87d536e43289f81c4af56f95e5f7b5ea" > diff --git a/meta-linaro/recipes-extra/powerdebug/powerdebug_0.7.3.bb > b/meta-linaro/recipes-extra/powerdebug/powerdebug_0.7.3.bb > index 9b6f3a0..37fdfc0 100644 > --- a/meta-linaro/recipes-extra/powerdebug/powerdebug_0.7.3.bb > +++ b/meta-linaro/recipes-extra/powerdebug/powerdebug_0.7.3.bb > @@ -9,7 +9,7 @@ DEPENDS = "ncurses" > MMYY = "14.06" > RELEASE = "20${MMYY}" > > -SRC_URI = > "http://releases.linaro.org/${MMYY}/components/power-management/powerdebug/linaro-powerdebug-${PV}-${RELEASE}.tar.bz2; > +SRC_URI = > "http://releases.linaro.org/archive/${MMYY}/components/power-management/powerdebug/linaro-powerdebug-${PV}-${RELEASE}.tar.bz2; > > SRC_URI[md5sum] = "f381946c5ca2f8075ed1bedc5f2a2876" > SRC_URI[sha256sum] = > "bfc4c92d8a8a1c8ee208a12310d3c763f111cf76d283facedb7ef56cafd074a1" > -- > 2.7.4 > > ___ > linaro-dev mailing list > linaro-dev@lists.linaro.org > https://lists.linaro.org/mailman/listinfo/linaro-dev -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro 16.12 available for download!
"I retain the right to change my mind, as always. Le Linus e mobile." ~ Linus Torvalds The Linaro 16.12 release is now available for download! This is probably the last installment of this monthly largely autogenerated email. Fewer and fewer components in Linaro have monthly cycles and with other changes scheduled for 2017 this email has become less than useful. The releases and snapshot they are based on will continue, but no email about them anymore. Also: shortest cycle ever! If you have snow where you live, I’m very jealous. If you live on the southern hemisphere with hot, sunny weather, I’m also very jealous. If you like rain, wind and gloom, come visit me! Enjoy the holidays! Using the Android-based images === The Android-based images come in three parts: system, userdata and boot. These need to be combined to form a complete Android install. For an explanation of how to do this please see: http://wiki.linaro.org/Platform/Android/ImageInstallation If you are interested in getting the source and building these images yourself please see the following pages: http://wiki.linaro.org/Platform/Android/GetSource http://wiki.linaro.org/Platform/Android/BuildSource Using the OpenEmbedded-based images === With the Linaro provided downloads and with ARM’s Fast Models virtual platform, you can boot a virtual ARMv8 system and run 64-bit binaries. For more information please see: http://www.linaro.org/engineering/armv8 Using the Debian-based images === The Debian-based images consist of two parts. The first part is a hardware pack, which can be found under the hwpacks directory and contains hardware specific packages (such as the kernel and bootloader). The second part is the rootfs, which is combined with the hardware pack to create a complete image. For more information on how to create an image please see: http://wiki.linaro.org/Platform/DevPlatform/Ubuntu/ImageInstallation Getting involved More information on Linaro can be found on our websites: * Homepage: http://www.linaro.org * Wiki: http://wiki.linaro.org Also subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro developments: * Announcements: http://lists.linaro.org/mailman/listinfo/linaro-announce * Development: http://lists.linaro.org/mailman/listinfo/linaro-dev * IRC: #linaro on irc.linaro.org or irc.freenode.net #linaro-android irc.linaro.org or irc.freenode.net Known issues with this release = Bug reports for this release should be filed in Bugzilla (http://bugs.linaro.org) against the individual packages or projects that are affected. On behalf of the release team, Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro 16.10 is available for download, now without spurious paste buffers
Apparently the terminal session from the tab next to the script generating these notes ended up in the other mail, and of course I didn't check the top of the mail, only the bottom, so here's the announcement without build logs and fetches: -- The first rule of all intelligent tinkering is to keep all the parts. -- Aldo Leopold, quoted in Donald Wurster's "Nature's Economy" The Linaro 16.10 release is now available for download! Using the Android-based images === The Android-based images come in three parts: system, userdata and boot. These need to be combined to form a complete Android install. For an explanation of how to do this please see: http://wiki.linaro.org/Platform/Android/ImageInstallation If you are interested in getting the source and building these images yourself please see the following pages: http://wiki.linaro.org/Platform/Android/GetSource http://wiki.linaro.org/Platform/Android/BuildSource Using the OpenEmbedded-based images === With the Linaro provided downloads and with ARM’s Fast Models virtual platform, you can boot a virtual ARMv8 system and run 64-bit binaries. For more information please see: http://www.linaro.org/engineering/armv8 Using the Debian-based images === The Debian-based images consist of two parts. The first part is a hardware pack, which can be found under the hwpacks directory and contains hardware specific packages (such as the kernel and bootloader). The second part is the rootfs, which is combined with the hardware pack to create a complete image. For more information on how to create an image please see: http://wiki.linaro.org/Platform/DevPlatform/Ubuntu/ImageInstallation Getting involved More information on Linaro can be found on our websites: * Homepage: http://www.linaro.org * Wiki: http://wiki.linaro.org Also subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro developments: * Announcements: http://lists.linaro.org/mailman/listinfo/linaro-announce * Development: http://lists.linaro.org/mailman/listinfo/linaro-dev * IRC: #linaro on irc.linaro.org or irc.freenode.net #linaro-android irc.linaro.org or irc.freenode.net Known issues with this release = Bug reports for this release should be filed in Bugzilla (http://bugs.linaro.org) against the individual packages or projects that are affected. On behalf of the release team, Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro 16.10 available for download!
rts for this release should be filed in Bugzilla (http://bugs.linaro.org) against the individual packages or projects that are affected. On behalf of the release team, Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro 16.09 available for download!
"Teamwork is essential -- it allows you to blame someone else." ~ Anonymous The Linaro 16.09 release is now available for download! And it's a week early! In preparation for Linaro Connect LAS16 in Las Vegas we're releasing a bit earlier than usual. Next cycle will be back on schedule. Using the Android-based images === The Android-based images come in three parts: system, userdata and boot. These need to be combined to form a complete Android install. For an explanation of how to do this please see: http://wiki.linaro.org/Platform/Android/ImageInstallation If you are interested in getting the source and building these images yourself please see the following pages: http://wiki.linaro.org/Platform/Android/GetSource http://wiki.linaro.org/Platform/Android/BuildSource Using the OpenEmbedded-based images === With the Linaro provided downloads and with ARM’s Fast Models virtual platform, you can boot a virtual ARMv8 system and run 64-bit binaries. For more information please see: http://www.linaro.org/engineering/armv8 Using the Debian-based images === The Debian-based images consist of two parts. The first part is a hardware pack, which can be found under the hwpacks directory and contains hardware specific packages (such as the kernel and bootloader). The second part is the rootfs, which is combined with the hardware pack to create a complete image. For more information on how to create an image please see: http://wiki.linaro.org/Platform/DevPlatform/Ubuntu/ImageInstallation Getting involved More information on Linaro can be found on our websites: * Homepage: http://www.linaro.org * Wiki: http://wiki.linaro.org Also subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro developments: * Announcements: http://lists.linaro.org/mailman/listinfo/linaro-announce * Development: http://lists.linaro.org/mailman/listinfo/linaro-dev * IRC: #linaro on irc.linaro.org or irc.freenode.net #linaro-android irc.linaro.org or irc.freenode.net Known issues with this release = Bug reports for this release should be filed in Bugzilla (http://bugs.linaro.org) against the individual packages or projects that are affected. On behalf of the release team, Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: meta-optee/optee-os: ARM64 hardcoding
> Op 6 sep. 2016, om 20:42 heeft Denys Dmytriyenko <de...@denix.org> het > volgende geschreven: > > Koen, Fathi, et al, > > Any chance to get EXTRA_OEMAKE to not hardcode ARM64 flags? > > https://git.linaro.org/openembedded/meta-linaro.git/blob/HEAD:/meta-optee/recipes-security/optee/optee-os_git.bb#l23 It’s not planned, but we wouldn’t say no to patches :) -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro 16.07 Release Available for Download
As soon as we started programming, we found to our surprise that it wasn't as easy to get programs right as we had thought. Debugging had to be discovered. I can remember the exact instant when I realized that a large part of my life from then on was going to be spent in finding mistakes in my own programs. -- Maurice Wilkes, designer of EDSAC, on programming, 1949 The Linaro 16.07 release is now available for download! Using the Android-based images === The Android-based images come in three parts: system, userdata and boot. These need to be combined to form a complete Android install. For an explanation of how to do this please see: http://wiki.linaro.org/Platform/Android/ImageInstallation If you are interested in getting the source and building these images yourself please see the following pages: http://wiki.linaro.org/Platform/Android/GetSource http://wiki.linaro.org/Platform/Android/BuildSource Using the OpenEmbedded-based images === With the Linaro provided downloads and with ARM’s Fast Models virtual platform, you can boot a virtual ARMv8 system and run 64-bit binaries. For more information please see: http://www.linaro.org/engineering/armv8 Using the Debian-based images === The Debian-based images consist of two parts. The first part is a hardware pack, which can be found under the hwpacks directory and contains hardware specific packages (such as the kernel and bootloader). The second part is the rootfs, which is combined with the hardware pack to create a complete image. For more information on how to create an image please see: http://wiki.linaro.org/Platform/DevPlatform/Ubuntu/ImageInstallation Getting involved More information on Linaro can be found on our websites: * Homepage: http://www.linaro.org * Wiki: http://wiki.linaro.org Also subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro developments: * Announcements: http://lists.linaro.org/mailman/listinfo/linaro-announce * Development: http://lists.linaro.org/mailman/listinfo/linaro-dev * IRC: #linaro on irc.linaro.org or irc.freenode.net #linaro-android irc.linaro.org or irc.freenode.net Known issues with this release = Bug reports for this release should be filed in Bugzilla (http://bugs.linaro.org) against the individual packages or projects that are affected. On behalf of the release team, Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro 16.06 Release Available for Download
The aim of science is to seek the simplest explanations of complex facts. Seek simplicity and distrust it. -- Whitehead. The Linaro 16.06 release is now available for download! Using the Android-based images === The Android-based images come in three parts: system, userdata and boot. These need to be combined to form a complete Android install. For an explanation of how to do this please see: http://wiki.linaro.org/Platform/Android/ImageInstallation If you are interested in getting the source and building these images yourself please see the following pages: http://wiki.linaro.org/Platform/Android/GetSource http://wiki.linaro.org/Platform/Android/BuildSource Using the OpenEmbedded-based images === With the Linaro provided downloads and with ARM’s Fast Models virtual platform, you can boot a virtual ARMv8 system and run 64-bit binaries. For more information please see: http://www.linaro.org/engineering/armv8 Using the Debian-based images === The Debian-based images consist of two parts. The first part is a hardware pack, which can be found under the hwpacks directory and contains hardware specific packages (such as the kernel and bootloader). The second part is the rootfs, which is combined with the hardware pack to create a complete image. For more information on how to create an image please see: http://wiki.linaro.org/Platform/DevPlatform/Ubuntu/ImageInstallation Getting involved More information on Linaro can be found on our websites: * Homepage: http://www.linaro.org * Wiki: http://wiki.linaro.org Also subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro developments: * Announcements: http://lists.linaro.org/mailman/listinfo/linaro-announce * Development: http://lists.linaro.org/mailman/listinfo/linaro-dev * IRC: #linaro on irc.linaro.org or irc.freenode.net #linaro-android irc.linaro.org or irc.freenode.net Known issues with this release = Bug reports for this release should be filed in Bugzilla (http://bugs.linaro.org) against the individual packages or projects that are affected. On behalf of the release team, Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
The Linaro 16.05 release is now available for download!
"No amount of careful planning will ever replace dumb luck." ~ Anonymous The Linaro 16.05 release is now available for download! Using the Android-based images === The Android-based images come in three parts: system, userdata and boot. These need to be combined to form a complete Android install. For an explanation of how to do this please see: http://wiki.linaro.org/Platform/Android/ImageInstallation If you are interested in getting the source and building these images yourself please see the following pages: http://wiki.linaro.org/Platform/Android/GetSource http://wiki.linaro.org/Platform/Android/BuildSource Using the OpenEmbedded-based images === With the Linaro provided downloads and with ARM’s Fast Models virtual platform, you can boot a virtual ARMv8 system and run 64-bit binaries. For more information please see: http://www.linaro.org/engineering/armv8 Using the Debian-based images === The Debian-based images consist of two parts. The first part is a hardware pack, which can be found under the hwpacks directory and contains hardware specific packages (such as the kernel and bootloader). The second part is the rootfs, which is combined with the hardware pack to create a complete image. For more information on how to create an image please see: http://wiki.linaro.org/Platform/DevPlatform/Ubuntu/ImageInstallation Getting involved More information on Linaro can be found on our websites: * Homepage: http://www.linaro.org * Wiki: http://wiki.linaro.org Also subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro developments: * Announcements: http://lists.linaro.org/mailman/listinfo/linaro-announce * Development: http://lists.linaro.org/mailman/listinfo/linaro-dev * IRC: #linaro on irc.linaro.org or irc.freenode.net #linaro-android irc.linaro.org or irc.freenode.net Known issues with this release = Bug reports for this release should be filed in Bugzilla (http://bugs.linaro.org) against the individual packages or projects that are affected. On behalf of the release team, Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
The Linaro 16.04 release is now available for download!
Digital circuits are made from analog parts. -- Don Vonada The Linaro 16.04 release is now available for download! Both LSK and LNG tarball releases have been discontinued this cycle and the preferred way of procuring a release is through git.linaro.org. Using the Android-based images === The Android-based images come in three parts: system, userdata and boot. These need to be combined to form a complete Android install. For an explanation of how to do this please see: http://wiki.linaro.org/Platform/Android/ImageInstallation If you are interested in getting the source and building these images yourself please see the following pages: http://wiki.linaro.org/Platform/Android/GetSource http://wiki.linaro.org/Platform/Android/BuildSource Using the OpenEmbedded-based images === With the Linaro provided downloads and with ARM’s Fast Models virtual platform, you can boot a virtual ARMv8 system and run 64-bit binaries. For more information please see: http://www.linaro.org/engineering/armv8 Using the Debian-based images === The Debian-based images consist of two parts. The first part is a hardware pack, which can be found under the hwpacks directory and contains hardware specific packages (such as the kernel and bootloader). The second part is the rootfs, which is combined with the hardware pack to create a complete image. For more information on how to create an image please see: http://wiki.linaro.org/Platform/DevPlatform/Ubuntu/ImageInstallation Getting involved More information on Linaro can be found on our websites: * Homepage: http://www.linaro.org * Wiki: http://wiki.linaro.org Also subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro developments: * Announcements: http://lists.linaro.org/mailman/listinfo/linaro-announce * Development: http://lists.linaro.org/mailman/listinfo/linaro-dev * IRC: #linaro on irc.linaro.org or irc.freenode.net #linaro-android irc.linaro.org or irc.freenode.net Known issues with this release = Bug reports for this release should be filed in Bugzilla (http://bugs.linaro.org) against the individual packages or projects that are affected. On behalf of the release team, Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [meta-linaro-toolchain][jethro][PATCH] gcc-runtime: Fix QA Issues
Fixed commit message and added into gerrit: https://review.linaro.org/11606 On 26 April 2016 at 12:20, <zongchun...@nxp.com> wrote: > From: Zongchun Yu <zongchun...@nxp.com> > > Fix following QA Issue: > ERROR: QA Issue: gcc-runtime: Files/directories were installed but not > shipped in any package: > /usr/lib/libstdc++fs.la > /usr/lib/libstdc++fs.a > Please set FILES such that these items are packaged. Alternatively if > they are unneeded, avoid installing them or delete them within > do_install. > gcc-runtime: 2 installed and not shipped files. [installed-vs-shipped] > > Signed-off-by: Zongchun Yu <zongchun...@nxp.com> > --- > .../recipes-devtools/gcc/gcc-runtime_linaro-5.2.bb| 8 > > 1 file changed, 8 insertions(+) > > diff --git > a/meta-linaro-toolchain/recipes-devtools/gcc/gcc-runtime_linaro-5.2.bb > b/meta-linaro-toolchain/recipes-devtools/gcc/gcc-runtime_linaro-5.2.bb > index a147ebd..0ae3085 100644 > --- a/meta-linaro-toolchain/recipes-devtools/gcc/gcc-runtime_linaro-5.2.bb > +++ b/meta-linaro-toolchain/recipes-devtools/gcc/gcc-runtime_linaro-5.2.bb > @@ -5,3 +5,11 @@ require recipes-devtools/gcc/gcc-runtime.inc > FILES_libgomp-dev += "\ > ${libdir}/gcc/${TARGET_SYS}/${BINV}/include/openacc.h \ > " > + > +FILES_libstdc++-dev += "\ > +${libdir}/libstdc++fs.la \ > +" > + > +FILES_libstdc++-staticdev += "\ > +${libdir}/libstdc++fs.a \ > +" > -- > 1.8.3.2 > -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [fido/jethro][PATCH] external-linaro-toolchain: correct path for libgcov.a to package properly
Added into gerrit: https://review.linaro.org/11498 https://review.linaro.org/11499 On 20 April 2016 at 19:53, Denys Dmytriyenko <de...@denix.org> wrote: > From: Denys Dmytriyenko <de...@ti.com> > > With migration from crosstool-NG to ABE, libgcov.a changed path and is now > available in ${libdir}. So, instead of being packaged into own libgcov-dev > package, it gets picked up by "catchall" libc6-staticdev package. This mostly > works, as long as nothing directly depends on libgcov-dev. Unfortunately, > packagegroup-core-standalone-sdk-target does and is the one being used when > building SDKs with -c populate_sdk. Correct path to generate libgcov-dev pkg. > > Signed-off-by: Denys Dmytriyenko <de...@ti.com> > --- > This is required for fido/jethro, but krogoth/master introduces single -dev > package rule, so separate libgcov-dev package can be dropped entirely. > > .../external-linaro-toolchain/external-linaro-toolchain.bb | 2 > +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git > a/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb > > b/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb > index ea41179..531caf7 100644 > --- > a/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb > +++ > b/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb > @@ -301,7 +301,7 @@ PKGV_gdbserver = "${ELT_VER_GDBSERVER}" > ALLOW_EMPTY_${PN}-mtrace = "1" > FILES_${PN}-mtrace = "${bindir}/mtrace" > > -FILES_libgcov-dev = "${libdir}/${TARGET_SYS}/${BINV}/libgcov.a" > +FILES_libgcov-dev = "${libdir}/libgcov.a" > > FILES_libsegfault = "${base_libdir}/libSegFault*" > > -- > 2.2.0 > > ___ > linaro-dev mailing list > linaro-dev@lists.linaro.org > https://lists.linaro.org/mailman/listinfo/linaro-dev -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: OE recipes for 5.3-2016.02 toolchain?
On 19 April 2016 at 07:30, Koen Kooi <koen.k...@linaro.org> wrote: > On 18 April 2016 at 23:03, Denys Dmytriyenko <de...@denix.org> wrote: >> On Fri, Apr 15, 2016 at 08:01:48AM +0200, Koen Kooi wrote: >>> On 14 April 2016 at 18:27, Denys Dmytriyenko <de...@denix.org> wrote: >>> > On Thu, Apr 14, 2016 at 10:04:18AM +0200, Koen Kooi wrote: >>> >> On 14 April 2016 at 07:09, Fathi Boudra <fathi.bou...@linaro.org> wrote: >>> >> > On 14 April 2016 at 00:05, Denys Dmytriyenko <de...@denix.org> wrote: >>> >> >> Koen, et al, >>> >> >> >>> >> >> With the release of 5.3-2016.02 Linaro toolchain it is now possible >>> >> >> to use the >>> >> >> binary version with the external-linaro-toolchain recipe. Are there >>> >> >> any >>> >> >> immediate plans to provide corresponding recipes to build the same >>> >> >> version of >>> >> >> the toolchain from sources? Thanks. >>> >> > >>> >> > Yes, the recipes for 5.3-2016.02 will be added. It's targeted for next >>> >> > cycle. >>> >> >>> >> The test build is still running, but here's the gerrit: >>> >> >>> >> https://review.linaro.org/11376 >>> > >>> > Thanks! >>> >>> It breaks grub, I'll sort that out with the toolchain folks later today. >>> >>> > What about glibc-2.21? >>> >>> Haven't looked at that one yet. >> >> Any updates on the above 2 items? It's not exactly blocking me currently, as >> I >> have workarounds in place, but it would be nice to get these resolved in >> krogoth/2.1... Thanks! > > For grub we need both a newer toolchain and a newer binutils. Still > haven't looked at glibc 2.21 yet, sorry. An update to the gcc situation: we've decided to move it to the next cycle (2016.06) so we can use a newer gcc release with the fix included. I've retracted https://review.linaro.org/#/c/11376/ to reflect this. -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: OE recipes for 5.3-2016.02 toolchain?
On 18 April 2016 at 23:03, Denys Dmytriyenko <de...@denix.org> wrote: > On Fri, Apr 15, 2016 at 08:01:48AM +0200, Koen Kooi wrote: >> On 14 April 2016 at 18:27, Denys Dmytriyenko <de...@denix.org> wrote: >> > On Thu, Apr 14, 2016 at 10:04:18AM +0200, Koen Kooi wrote: >> >> On 14 April 2016 at 07:09, Fathi Boudra <fathi.bou...@linaro.org> wrote: >> >> > On 14 April 2016 at 00:05, Denys Dmytriyenko <de...@denix.org> wrote: >> >> >> Koen, et al, >> >> >> >> >> >> With the release of 5.3-2016.02 Linaro toolchain it is now possible to >> >> >> use the >> >> >> binary version with the external-linaro-toolchain recipe. Are there any >> >> >> immediate plans to provide corresponding recipes to build the same >> >> >> version of >> >> >> the toolchain from sources? Thanks. >> >> > >> >> > Yes, the recipes for 5.3-2016.02 will be added. It's targeted for next >> >> > cycle. >> >> >> >> The test build is still running, but here's the gerrit: >> >> >> >> https://review.linaro.org/11376 >> > >> > Thanks! >> >> It breaks grub, I'll sort that out with the toolchain folks later today. >> >> > What about glibc-2.21? >> >> Haven't looked at that one yet. > > Any updates on the above 2 items? It's not exactly blocking me currently, as I > have workarounds in place, but it would be nice to get these resolved in > krogoth/2.1... Thanks! For grub we need both a newer toolchain and a newer binutils. Still haven't looked at glibc 2.21 yet, sorry. -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [meta-linaro-toolchain][PATCH][jethro] gcc: remove '-2' from PR
On 15 April 2016 at 11:27, <zongchun...@nxp.com> wrote: > From: Zongchun Yu <zongchun...@nxp.com> > > Fix following Error: > | error: line 4: invalid tag value("^[A-Za-z0-9+._]+$") Release: > Release: r2015.11-2 > | error: Package has no %description: libgcc-linaro+5.2.aarch64 NACK, this winds back the release, which is bad and breaks upgrade paths, which is worse > > Signed-off-by: Zongchun Yu <zongchun...@nxp.com> > --- > meta-linaro-toolchain/recipes-devtools/gcc/gcc-linaro-5.2.inc | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/meta-linaro-toolchain/recipes-devtools/gcc/gcc-linaro-5.2.inc > b/meta-linaro-toolchain/recipes-devtools/gcc/gcc-linaro-5.2.inc > index ca44d66..65c665b 100644 > --- a/meta-linaro-toolchain/recipes-devtools/gcc/gcc-linaro-5.2.inc > +++ b/meta-linaro-toolchain/recipes-devtools/gcc/gcc-linaro-5.2.inc > @@ -58,9 +58,9 @@ EXTRA_OECONF_PATHS = "\ > > PV = "linaro-${BASEPV}" > > -MMYY = "15.11-2" > -RELEASE = "20${MMYY}" > -PR = "r${RELEASE}" > +MMYY = "15.11" > +RELEASE = "20${MMYY}-2" > +PR = "r20${MMYY}" > BINV = "5.2.1" > > FILESPATH = "${@base_set_filespath([ '${FILE_DIRNAME}/gcc-${PV}' ], d)}" > -- > 1.8.3.2 > -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: OE recipes for 5.3-2016.02 toolchain?
On 14 April 2016 at 18:27, Denys Dmytriyenko <de...@denix.org> wrote: > On Thu, Apr 14, 2016 at 10:04:18AM +0200, Koen Kooi wrote: >> On 14 April 2016 at 07:09, Fathi Boudra <fathi.bou...@linaro.org> wrote: >> > On 14 April 2016 at 00:05, Denys Dmytriyenko <de...@denix.org> wrote: >> >> Koen, et al, >> >> >> >> With the release of 5.3-2016.02 Linaro toolchain it is now possible to >> >> use the >> >> binary version with the external-linaro-toolchain recipe. Are there any >> >> immediate plans to provide corresponding recipes to build the same >> >> version of >> >> the toolchain from sources? Thanks. >> > >> > Yes, the recipes for 5.3-2016.02 will be added. It's targeted for next >> > cycle. >> >> The test build is still running, but here's the gerrit: >> >> https://review.linaro.org/11376 > > Thanks! It breaks grub, I'll sort that out with the toolchain folks later today. > What about glibc-2.21? Haven't looked at that one yet. -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: OE recipes for 5.3-2016.02 toolchain?
On 14 April 2016 at 07:09, Fathi Boudra <fathi.bou...@linaro.org> wrote: > On 14 April 2016 at 00:05, Denys Dmytriyenko <de...@denix.org> wrote: >> Koen, et al, >> >> With the release of 5.3-2016.02 Linaro toolchain it is now possible to use >> the >> binary version with the external-linaro-toolchain recipe. Are there any >> immediate plans to provide corresponding recipes to build the same version of >> the toolchain from sources? Thanks. > > Yes, the recipes for 5.3-2016.02 will be added. It's targeted for next cycle. The test build is still running, but here's the gerrit: https://review.linaro.org/11376 -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [PATCH] external-linaro-toolchain-versions: make parse debugging use bb.debug
Added into gerrit: https://review.linaro.org/11273 On 7 April 2016 at 13:35, Denys Dmytriyenko <de...@denix.org> wrote: > From: Denys Dmytriyenko <de...@ti.com> > > Signed-off-by: Denys Dmytriyenko <de...@ti.com> > --- > .../conf/distro/include/external-linaro-toolchain-versions.inc | 2 > +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git > a/meta-linaro-toolchain/conf/distro/include/external-linaro-toolchain-versions.inc > > b/meta-linaro-toolchain/conf/distro/include/external-linaro-toolchain-versions.inc > index 564a408..71fe69b 100644 > --- > a/meta-linaro-toolchain/conf/distro/include/external-linaro-toolchain-versions.inc > +++ > b/meta-linaro-toolchain/conf/distro/include/external-linaro-toolchain-versions.inc > @@ -26,7 +26,7 @@ def elt_get_version(d): > # Extract the .MM version > def elt_get_main_version(d): > version = elt_get_version(d) > - bb.note('Trying for parse version info from: %s' % version) > + bb.debug(2, 'Trying for parse version info from: %s' % version) > if version != 'UNKNOWN': > if version.split()[4] == '(Linaro': > # gcc version 5.1.1 20150608 (Linaro GCC 5.1-2015.08) > -- > 2.2.0 > > ___ > linaro-dev mailing list > linaro-dev@lists.linaro.org > https://lists.linaro.org/mailman/listinfo/linaro-dev -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [PATCH] external-linaro-toolchain: update to work with Linaro GCC 5.3-2016.02
Added into gerrit: https://review.linaro.org/11146 On 1 April 2016 at 03:04, Denys Dmytriyenko <de...@denix.org> wrote: > From: Denys Dmytriyenko <de...@ti.com> > > * libasan and libgfortran changed major version number, handle both > * only remove dups of lib*-${ELT_VER_LIBC}.so when they are regular and > identical files > preserve them if one is a symlink to another or files are different > > Signed-off-by: Denys Dmytriyenko <de...@ti.com> > --- > .../external-linaro-toolchain.bb | 33 > ++ > 1 file changed, 28 insertions(+), 5 deletions(-) > > diff --git > a/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb > > b/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb > index 676b7ba..7b29ce5 100644 > --- > a/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb > +++ > b/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb > @@ -89,7 +89,6 @@ do_install() { > cp -a ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/usr/include/* > ${D}${includedir} > if [ -d > ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/usr/include/${ELT_TARGET_SYS} ]; > then > cp -a > ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/usr/include/${ELT_TARGET_SYS}/* > ${D}${includedir} > - > rm -r ${D}${includedir}/${ELT_TARGET_SYS} > fi > > @@ -115,14 +114,22 @@ do_install() { > ln -sf ../../lib/libnss_nisplus.so.2 ${D}${libdir}/libnss_nisplus.so > ln -sf ../../lib/libnss_db.so.2 ${D}${libdir}/libnss_db.so > ln -sf ../../lib/libm.so.6 ${D}${libdir}/libm.so > - ln -sf ../../lib/libasan.so.1 ${D}${libdir}/libasan.so > ln -sf ../../lib/libatomic.so.1 ${D}${libdir}/libatomic.so > ln -sf ../../lib/libgomp.so.1 ${D}${libdir}/libgomp.so > ln -sf ../../lib/libitm.so.1 ${D}${libdir}/libitm.so > ln -sf ../../lib/libssp.so.0 ${D}${libdir}/libssp.so > ln -sf ../../lib/libstdc++.so.6 ${D}${libdir}/libstdc++.so > - ln -sf ../../lib/libgfortran.so.6 ${D}${libdir}/libgfortran.so > ln -sf ../../lib/libubsan.so.0 ${D}${libdir}/libubsan.so > + if [ -f ${D}${base_libdir}/libasan.so.2 ]; then > + ln -sf ../../lib/libasan.so.2 ${D}${libdir}/libasan.so > + else > + ln -sf ../../lib/libasan.so.1 ${D}${libdir}/libasan.so > + fi > + if [ -f ${D}${base_libdir}/libgfortran.so.6 ]; then > + ln -sf ../../lib/libgfortran.so.6 ${D}${libdir}/libgfortran.so > + else > + ln -sf ../../lib/libgfortran.so.3 ${D}${libdir}/libgfortran.so > + fi > > # remove potential .so duplicates from base_libdir > # for all symlinks created above in libdir > @@ -139,7 +146,6 @@ do_install() { > rm -f ${D}${base_libdir}/libcidn.so > rm -f ${D}${base_libdir}/libBrokenLocale.so > rm -f ${D}${base_libdir}/libthread_db.so > - rm -f ${D}${base_libdir}/libthread_db-1.0.so > rm -f ${D}${base_libdir}/libanl.so > rm -f ${D}${base_libdir}/libdl.so > rm -f ${D}${base_libdir}/libnss_nisplus.so > @@ -155,7 +161,24 @@ do_install() { > rm -f ${D}${base_libdir}/libubsan.so > > # Besides ld-${ELT_VER_LIBC}.so, other libs can have duplicates like > lib*-${ELT_VER_LIBC}.so > - rm -rf ${D}${base_libdir}/lib*-${ELT_VER_LIBC}.so > + # Only remove them if both are regular files and are identical > + for i in ${D}${base_libdir}/lib*-${ELT_VER_LIBC}.so; do > + f=$(echo $i | sed 's/-${ELT_VER_LIBC}//') > + l=$(ls $f.*) > + if [ $(readlink -f $i ) = $l ]; then > + echo "$i is a symlink of $l, keep it" > + elif [ $(readlink -f $l ) = $i ]; then > + echo "$l is a symlink of $i, keep it" > + else > + cmp -s $i $l > + if [ $? -eq 0 ]; then > + echo "$i is a duplicate of $l, remove it" > + rm $i > + else > + echo "$i and $l are different files, keep > them both" > + fi > + fi > + done > > if [ -d ${D}${base_libdir}/arm-linux-gnueabi ]; then >rm -rf ${D}${base_libdir}/arm-linux-gnueabi > -- > 2.2.0 > > ___ > linaro-dev mailing list > linaro-dev@lists.linaro.org > https://lists.linaro.org/mailman/listinfo/linaro-dev -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
The Linaro 16.03 release is now available for download!
But it does move! -- Galileo Galilei The Linaro 16.03 release is now available for download! A relatively short cycle thanks to BKK16. This is likely the last time LNG kernel tarballs will be published, since it's become a virtual copy of LSK. In the long run I'd like to completely phase out kernel tarballs, so speak up if you are actually using the LSK tarballs. Using the Android-based images === The Android-based images come in three parts: system, userdata and boot. These need to be combined to form a complete Android install. For an explanation of how to do this please see: http://wiki.linaro.org/Platform/Android/ImageInstallation If you are interested in getting the source and building these images yourself please see the following pages: http://wiki.linaro.org/Platform/Android/GetSource http://wiki.linaro.org/Platform/Android/BuildSource Using the OpenEmbedded-based images === With the Linaro provided downloads and with ARM’s Fast Models virtual platform, you can boot a virtual ARMv8 system and run 64-bit binaries. For more information please see: http://www.linaro.org/engineering/armv8 Using the Debian-based images === The Debian-based images consist of two parts. The first part is a hardware pack, which can be found under the hwpacks directory and contains hardware specific packages (such as the kernel and bootloader). The second part is the rootfs, which is combined with the hardware pack to create a complete image. For more information on how to create an image please see: http://wiki.linaro.org/Platform/DevPlatform/Ubuntu/ImageInstallation Getting involved More information on Linaro can be found on our websites: * Homepage: http://www.linaro.org * Wiki: http://wiki.linaro.org Also subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro developments: * Announcements: http://lists.linaro.org/mailman/listinfo/linaro-announce * Development: http://lists.linaro.org/mailman/listinfo/linaro-dev * IRC: #linaro on irc.linaro.org or irc.freenode.net #linaro-android irc.linaro.org or irc.freenode.net Known issues with this release = Bug reports for this release should be filed in Bugzilla (http://bugs.linaro.org) against the individual packages or projects that are affected. On behalf of the release team, Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
The Linaro 16.02 release is now available for download!
Sir, it's very possible this asteroid is not stable. -- C3P0 The Linaro 16.02 release is now available for download! This cycle contains a big, but hopefully invisible change: all artefacts for 16.02 are now hosted using Amazon S3. Personally, it meant that both upload and downloads speeds increased six-fold, making my release week coffee breaks a lot shorter. In the future Andy & Ben will turn on geo-clouding for even more bandwidth improvements for people outside of North America. As I said 'hopefully' above, don't hesitate to email me if you suspect something is not as it should be with this release. As with the previous two cycles, the OE release comes with a lot of qualifiers and caveats. Something has gone wrong in the CI loop which broke fetching the hwpacks for the prebuilt images, which means the prebuilts have been recycled from last cycle. Using the Android-based images === The Android-based images come in three parts: system, userdata and boot. These need to be combined to form a complete Android install. For an explanation of how to do this please see: http://wiki.linaro.org/Platform/Android/ImageInstallation If you are interested in getting the source and building these images yourself please see the following pages: http://wiki.linaro.org/Platform/Android/GetSource http://wiki.linaro.org/Platform/Android/BuildSource Using the OpenEmbedded-based images === With the Linaro provided downloads and with ARM’s Fast Models virtual platform, you can boot a virtual ARMv8 system and run 64-bit binaries. For more information please see: http://www.linaro.org/engineering/armv8 Using the Debian-based images === The Debian-based images consist of two parts. The first part is a hardware pack, which can be found under the hwpacks directory and contains hardware specific packages (such as the kernel and bootloader). The second part is the rootfs, which is combined with the hardware pack to create a complete image. For more information on how to create an image please see: http://wiki.linaro.org/Platform/DevPlatform/Ubuntu/ImageInstallation (Yes, that points to Ubuntu, I know, the instructions are still valid) Getting involved More information on Linaro can be found on our websites: * Homepage: http://www.linaro.org * Wiki: http://wiki.linaro.org Also subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro developments: * Announcements: http://lists.linaro.org/mailman/listinfo/linaro-announce * Development: http://lists.linaro.org/mailman/listinfo/linaro-dev * IRC: #linaro on irc.linaro.org or irc.freenode.net #linaro-android irc.linaro.org or irc.freenode.net Known issues with this release = Bug reports for this release should be filed in Bugzilla (http://bugs.linaro.org) against the individual packages or projects that are affected. On behalf of the release team, Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
The Linaro 16.01 release is now available for download!
Digital circuits are made from analog parts. -- Don Vonada The Linaro 16.01 release is now available for download! Using the Android-based images === The Android-based images come in three parts: system, userdata and boot. These need to be combined to form a complete Android install. For an explanation of how to do this please see: http://wiki.linaro.org/Platform/Android/ImageInstallation If you are interested in getting the source and building these images yourself please see the following pages: http://wiki.linaro.org/Platform/Android/GetSource http://wiki.linaro.org/Platform/Android/BuildSource Using the OpenEmbedded-based images === With the Linaro provided downloads and with ARM’s Fast Models virtual platform, you can boot a virtual ARMv8 system and run 64-bit binaries. For more information please see: http://www.linaro.org/engineering/armv8 Using the Ubuntu-based images === The Ubuntu-based images consist of two parts. The first part is a hardware pack, which can be found under the hwpacks directory and contains hardware specific packages (such as the kernel and bootloader). The second part is the rootfs, which is combined with the hardware pack to create a complete image. For more information on how to create an image please see: http://wiki.linaro.org/Platform/DevPlatform/Ubuntu/ImageInstallation Getting involved More information on Linaro can be found on our websites: * Homepage: http://www.linaro.org * Wiki: http://wiki.linaro.org Also subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro developments: * Announcements: http://lists.linaro.org/mailman/listinfo/linaro-announce * Development: http://lists.linaro.org/mailman/listinfo/linaro-dev * IRC: #linaro on irc.linaro.org or irc.freenode.net #linaro-android irc.linaro.org or irc.freenode.net Known issues with this release = Bug reports for this release should be filed in Bugzilla (http://bugs.linaro.org) against the individual packages or projects that are affected. On behalf of the release team, Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Old releases have been archived
On 30 October 2015 at 15:33, Arnd Bergmann <a...@arndb.de> wrote: > On Monday 26 October 2015 10:24:54 Koen Kooi wrote: >> The first reports of things breaking are tricking in, OpenWRT >> apparently uses binutils-linaro 13.05 and Fathi mentioned that various >> LAVA health checks are failing now. If you encounter such an issue, >> add the 'archive/' bit to the URL, e.g. >> > > Is this old OpenWRT or current trunk? The current code should > obviously be updated, but it might be better to not break the > latest official release. I have no idea, someone showed up on IRC and said openWRT needed it. That's all the info I have. -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Old releases have been archived
Hi, As part of BB-149 old releases have been moved to http://releases.linaro.org/archive/. 'Old' meaning 2011, 2012 and 2013. The first reports of things breaking are tricking in, OpenWRT apparently uses binutils-linaro 13.05 and Fathi mentioned that various LAVA health checks are failing now. If you encounter such an issue, add the 'archive/' bit to the URL, e.g. sed -i -e s:org/13:org/archive/13:g -e s:org/12:org/archive/12:g -e s:org/11:org/archive/11:g We of course recommend trying out more recent releases for current projects, but if you can't upgrade the archive is there to stay. -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 40
== Progress == * Connect wrap up in jira (20%) * ELC-E preparation (40%) * Release fixes (5%) * meta-96boards maintenance (5%) * OE builds (30%) == Plans == * ELC-E -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 37
== Progress == * meta-luv work (30%) * OE CI loops (10%) * Connect preparations (10%) * ELC-E preparation (10%) * Release preparations (30%) * meta-96boards maintenance (10%) == Plans == * vacation -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [meta-linaro-toolchain][PATCH 1/2] external-linaro-toolchain: work around 2015.05 release that moved libs
Pushed to fido, sorry for the delay. On 28 August 2015 at 18:35, Denys Dmytriyenko <de...@denix.org> wrote: > Ping. Can I get these backported to fido, please? Corresponding patches were > already submitted 2 weeks ago. Thanks. > > -- > Denys > > > On Fri, Aug 14, 2015 at 02:55:06PM -0400, Denys Dmytriyenko wrote: >> Thanks! I also submitted fido backports of the patches, for when these get >> into the master... >> >> -- >> Denys >> >> >> On Fri, Aug 14, 2015 at 08:27:07PM +0200, Koen Kooi wrote: >> > Added both patches into gerrit: >> > >> > https://review.linaro.org/7446 >> > https://review.linaro.org/7447 >> > >> > >> > >> > > Op 14 aug. 2015, om 20:12 heeft Denys Dmytriyenko <de...@denix.org> het >> > > volgende geschreven: >> > > >> > > From: Denys Dmytriyenko <de...@ti.com> >> > > >> > > Starting with 2015.05 binary release, all the libraries have been moved >> > > from >> > > /libc/lib/ to /libc/usr/lib/ that causes various toolchain issues in OE, >> > > ranging from QA errors to build failures of other components. This patch >> > > takes care of installing, updating and packaging libraries to match other >> > > versions and satisfy OE toolchain requirements. >> > > >> > > Previous attempt at fixing it in 78df3a9646e35790ef8b429c84a912d336fd128b >> > > wasn't complete and its conditional logic would never work: >> > > https://bugs.linaro.org/show_bug.cgi?id=1717 >> > > >> > > * Update check to look where ld-*.so is installed, instead of simply >> > > checking for /libc/lib/ presence, which exists in 2015.05 >> > > * Only copy real *.so* libs from /libc/usr/lib to base_libdir, let the >> > > rest (*.a, *.o, etc) go to libdir, as usual >> > > * If we copy *.so* to base_libdir, remove them from libdir >> > > * Update lib*.so -> lib*.so.* symlinking list with new libraries >> > > * For all the lib*.so symlinks created in libdir, remove potential dups >> > > from base_libdir >> > > * Remove lib*-${ELT_VER_LIBC}.so duplicates >> > > * When updating libc.so in base_libdir, no need to change path to >> > > ld-linux >> > > that is also in base_libdir >> > > * If both libc.so and libc.so.6 are in base_libdir, make sure the path to >> > > libc.so.6 in libc.so is correct >> > > * Same for libpthread.so >> > > * Suppress ldflags/GNU_HASH QA warning for more lib packages >> > > * Remove duplicate FILES_libstdc++ lines >> > > >> > > Signed-off-by: Denys Dmytriyenko <de...@ti.com> >> > > --- >> > > .../external-linaro-toolchain.bb | 81 >> > > ++ >> > > 1 file changed, 66 insertions(+), 15 deletions(-) >> > > >> > > diff --git >> > > a/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb >> > > >> > > b/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb >> > > index 857e280..ea41179 100644 >> > > --- >> > > a/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb >> > > +++ >> > > b/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb >> > > @@ -65,16 +65,19 @@ do_install() { >> > > if [ -d >> > > ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/lib/${ELT_TARGET_SYS} ]; >> > > then >> > > cp -a >> > > ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/lib/${ELT_TARGET_SYS}/* >> > > ${D}${base_libdir} >> > > else >> > > -if [ -d ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/lib ]; then >> > > - cp -a ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/lib/* >> > > ${D}${base_libdir} >> > > -else >> > > - cp -a >> > > ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/usr/lib/* >> > > ${D}${base_libdir} >> > > -fi >> > > + if [ -f >> > > ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/lib/ld-${ELT_VER_LIBC}.so >> > > ]; then >> > > + cp -a >> > > ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/lib/* ${D}${base_libdir} >> > > + e
Re: [meta-linaro-toolchain][PATCH 1/2] external-linaro-toolchain: work around 2015.05 release that moved libs
Added both patches into gerrit: https://review.linaro.org/7446 https://review.linaro.org/7447 Op 14 aug. 2015, om 20:12 heeft Denys Dmytriyenko de...@denix.org het volgende geschreven: From: Denys Dmytriyenko de...@ti.com Starting with 2015.05 binary release, all the libraries have been moved from /libc/lib/ to /libc/usr/lib/ that causes various toolchain issues in OE, ranging from QA errors to build failures of other components. This patch takes care of installing, updating and packaging libraries to match other versions and satisfy OE toolchain requirements. Previous attempt at fixing it in 78df3a9646e35790ef8b429c84a912d336fd128b wasn't complete and its conditional logic would never work: https://bugs.linaro.org/show_bug.cgi?id=1717 * Update check to look where ld-*.so is installed, instead of simply checking for /libc/lib/ presence, which exists in 2015.05 * Only copy real *.so* libs from /libc/usr/lib to base_libdir, let the rest (*.a, *.o, etc) go to libdir, as usual * If we copy *.so* to base_libdir, remove them from libdir * Update lib*.so - lib*.so.* symlinking list with new libraries * For all the lib*.so symlinks created in libdir, remove potential dups from base_libdir * Remove lib*-${ELT_VER_LIBC}.so duplicates * When updating libc.so in base_libdir, no need to change path to ld-linux that is also in base_libdir * If both libc.so and libc.so.6 are in base_libdir, make sure the path to libc.so.6 in libc.so is correct * Same for libpthread.so * Suppress ldflags/GNU_HASH QA warning for more lib packages * Remove duplicate FILES_libstdc++ lines Signed-off-by: Denys Dmytriyenko de...@ti.com --- .../external-linaro-toolchain.bb | 81 ++ 1 file changed, 66 insertions(+), 15 deletions(-) diff --git a/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb b/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb index 857e280..ea41179 100644 --- a/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb +++ b/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb @@ -65,16 +65,19 @@ do_install() { if [ -d ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/lib/${ELT_TARGET_SYS} ]; then cp -a ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/lib/${ELT_TARGET_SYS}/* ${D}${base_libdir} else -if [ -d ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/lib ]; then - cp -a ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/lib/* ${D}${base_libdir} -else - cp -a ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/usr/lib/* ${D}${base_libdir} -fi + if [ -f ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/lib/ld-${ELT_VER_LIBC}.so ]; then + cp -a ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/lib/* ${D}${base_libdir} + else + cp -a ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/usr/lib/*.so* ${D}${base_libdir} + fi fi if [ -d ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/usr/lib/${ELT_TARGET_SYS} ]; then cp -a ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/usr/lib/${ELT_TARGET_SYS}/* ${D}${libdir} else cp -a ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/usr/lib/* ${D}${libdir} + if [ ! -f ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/lib/ld-${ELT_VER_LIBC}.so ]; then + rm -rf ${D}${libdir}/*.so* + fi fi cp -a ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/usr/share/* ${D}${datadir} cp -a ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/usr/include/* ${D}${includedir} @@ -100,10 +103,53 @@ do_install() { ln -sf ../../lib/libcidn.so.1 ${D}${libdir}/libcidn.so ln -sf ../../lib/libBrokenLocale.so.1 ${D}${libdir}/libBrokenLocale.so ln -sf ../../lib/libthread_db.so.1 ${D}${libdir}/libthread_db.so + ln -sf ../../lib/libthread_db.so.1 ${D}${libdir}/libthread_db-1.0.so ln -sf ../../lib/libanl.so.1 ${D}${libdir}/libanl.so ln -sf ../../lib/libdl.so.2 ${D}${libdir}/libdl.so ln -sf ../../lib/libnss_nisplus.so.2 ${D}${libdir}/libnss_nisplus.so + ln -sf ../../lib/libnss_db.so.2 ${D}${libdir}/libnss_db.so ln -sf ../../lib/libm.so.6 ${D}${libdir}/libm.so + ln -sf ../../lib/libasan.so.1 ${D}${libdir}/libasan.so + ln -sf ../../lib/libatomic.so.1 ${D}${libdir}/libatomic.so + ln -sf ../../lib/libgomp.so.1 ${D}${libdir}/libgomp.so + ln -sf ../../lib/libitm.so.1 ${D}${libdir}/libitm.so + ln -sf ../../lib/libssp.so.0 ${D}${libdir}/libssp.so + ln -sf ../../lib/libstdc++.so.6 ${D}${libdir}/libstdc++.so + ln -sf ../../lib/libgfortran.so.6 ${D}${libdir}/libgfortran.so + ln -sf
[ACTIVITY] Week 30
== Progress == * Address issues caused by the new layout for r.l.o (50%) * Reinstate gcc-linaro 4.9-2015.06 (5%) * Fix binutils-linaro issues in OE (5%) * Fix gdb-linaro issues in OE (5%) * Prepare for 15.08 release (15%) * Looked at OE CI jobs (20%) == Plans == * Document the new release scripts since I'll be away most of release week * Modernize OE CI jobs * Create LAVA tarballs for 15.08 -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [meta-linaro-toolchain] gcc, SRC_URI points to not existing tarball
On 5 August 2015 at 12:26, Max Krummenacher max.oss...@gmail.com wrote: Hi I tried to build with meta-linaro, branch master HEAD at eeeccee. The do_fetch of gcc fails with: WARNING: Failed to fetch URL https://releases.linaro.org/15.06/components/toolchain/gcc-linaro/4.9/gcc-linaro-4.9-2015.06.tar.xz, attempting MIRRORS if available ERROR: Fetcher failure: Fetch command failed with exit code 8, output: https://releases.linaro.org/15.06/components/toolchain/gcc-linaro/4.9/gcc-linaro-4.9-2015.06.tar.xz: 2015-08-05 11:15:55 ERROR 404: NOT FOUND. I checked with a browser, gcc 4.9 is really not there. What happend was that 4.9-2015.06 was mistakingly promoted to 'release' instead of snapshot and removed when we realized what happened. In that process I forgot that meta-linaro had been updated to use it. The CI loop and my laptop didn't empty their source cache and hence didn't notice it was gone. It's now back on releases since that was the simplest way to fix this mess. My apologies for this and I hope this fixes the issues you have been seeing. regards, Koen The following fixed this, however I don't know if that is the right course of action here. diff --git a/meta-linaro-toolchain/recipes-devtools/gcc/gcc-linaro-4.9.inc b/meta-linaro-toolchain/recipes-devtools/gcc/gcc-linaro-4.9.inc index 852a316..1109b44 100644 --- a/meta-linaro-toolchain/recipes-devtools/gcc/gcc-linaro-4.9.inc +++ b/meta-linaro-toolchain/recipes-devtools/gcc/gcc-linaro-4.9.inc @@ -1,10 +1,10 @@ require recipes-devtools/gcc/gcc-4.9.inc PV = linaro-${BASEPV} -MMYY = 15.06 +MMYY = 15.05 RELEASE = 20${MMYY} PR = r${RELEASE} -BINV = 4.9.4 +BINV = 4.9.3 FILESPATH = ${@base_set_filespath([ '${FILE_DIRNAME}/gcc-${PV}' ], d)} @@ -65,8 +65,8 @@ SRC_URI = https://releases.linaro.org/${MMYY}/components/toolchain/gcc-linaro/$ file://use-lib-for-aarch64.patch \ -SRC_URI[md5sum] = e978776eb7b1b0101015c5ffb00d8292 -SRC_URI[sha256sum] = 9a149d46b933d66b85141c0a8341321551f6b56f264adbf59c312eb52c0f52ad +SRC_URI[md5sum] = 7303374d7877e20aedc9e442cd1d0b2d +SRC_URI[sha256sum] = 27fcdab3706574a4206c1a756f14d42fc5000156a730ad827e8e70a1043a42ce S = ${TMPDIR}/work-shared/gcc-${PV}-${PR}/gcc-${PV}-${RELEASE} B = ${WORKDIR}/gcc-${PV}-${RELEASE}/build.${HOST_SYS}.${TARGET_SYS} Regards Max -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [meta-linaro-toolchain] gdb: patch does not apply, cherry-pick request
On 5 August 2015 at 13:20, Max Krummenacher max.oss...@gmail.com wrote: Hi Can we cherry-pick 723442fbdfaa9da91ea113b381c4d49a2a17ae66 (from dizzy) into the fido and master branch. Certainly! I didn't notice the build breakage because the linaro setup is picking up the oe-core gdb for reasons unknown. Anyway, patch cherry-picked into fido and master, thanks! Regards Max commit 723442fbdfaa9da91ea113b381c4d49a2a17ae66 Author: Max Krummenacher max.oss...@gmail.com Date: Tue Dec 30 16:20:08 2014 +0100 gdb-cross_linaro-7.8: remove elf_prstatus-size.patch elf_prstatus-size.patch no longer applies as the patched file no longer exists. The patched code now resides in gdb-linaro-7.8-2014.09/bfd/elfxx-aarch64.c with the patch already applied. ERROR: Command Error: exit status: 1 Output: Applying patch elf_prstatus-size.patch can't find file to patch at input line 5 ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [meta-linaro][PATCH] perf: move to 4.0.2
Done On 28 July 2015 at 07:24, Yu Zongchun zongchun...@freescale.com wrote: Ping Best Regards Zongchun -Original Message- From: Yu Zongchun-B40527 Sent: Friday, July 24, 2015 11:05 AM To: 'Koen Kooi' Cc: Linaro Dev Mailman List; Luo Zhenhua-B19537 Subject: RE: [meta-linaro][PATCH] perf: move to 4.0.2 Hello Koen. Can you help to port this patch to fido branch? Thanks Best Regards Zongchun -Original Message- From: Koen Kooi [mailto:koen.k...@linaro.org] Sent: Thursday, July 23, 2015 4:43 PM To: Yu Zongchun-B40527 Cc: Linaro Dev Mailman List; Yu Zongchun-B40527; Luo Zhenhua-B19537 Subject: Re: [meta-linaro][PATCH] perf: move to 4.0.2 Added to gerrit: https://review.linaro.org/7140 On 23 July 2015 at 09:59, b40...@freescale.com wrote: From: Zongchun Yu zongchun...@freescale.com The 3.18.5 tarball has been removed in the mirror. So Update the SRC_URI to point to a avaliable tarball. Signed-off-by: Zongchun Yu zongchun...@freescale.com --- meta-linaro/recipes-kernel/perf/perf.bbappend | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/meta-linaro/recipes-kernel/perf/perf.bbappend b/meta-linaro/recipes-kernel/perf/perf.bbappend index 7bf446a..cf7cb93 100644 --- a/meta-linaro/recipes-kernel/perf/perf.bbappend +++ b/meta-linaro/recipes-kernel/perf/perf.bbappend @@ -1,13 +1,13 @@ LICENSE = GPL-2 LIC_FILES_CHKSUM = file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7 -PV = 3.18.5 +PV = 4.0.2 FILESEXTRAPATHS_prepend := ${THISDIR}/files: -SRC_URI = ${DEBIAN_MIRROR}/main/l/linux-tools/linux-tools_3.18.5.orig.tar.xz +SRC_URI = ${DEBIAN_MIRROR}/main/l/linux-tools/linux-tools_4.0.2.orig.tar.xz -SRC_URI[md5sum] = c9ee8f5c1f88e562f1c1d6997c442c7f -SRC_URI[sha256sum] = bf79397874cc211e81eed47e2c2591632ba7b03d3de73aea867f2a78917b9720 +SRC_URI[md5sum] = 2bf7891f174843b40603395e94bde29d +SRC_URI[sha256sum] = 9c149a18e2d0ec3aba9200fdf49b124849a74130574e15abcb526f7481c2147e S = ${WORKDIR}/linux-tools-${PV} B = ${WORKDIR}/linux-tools-${PV}-build -- 1.8.3.2 ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [meta-linaro][PATCH] perf: move to 4.0.2
Added to gerrit: https://review.linaro.org/7140 On 23 July 2015 at 09:59, b40...@freescale.com wrote: From: Zongchun Yu zongchun...@freescale.com The 3.18.5 tarball has been removed in the mirror. So Update the SRC_URI to point to a avaliable tarball. Signed-off-by: Zongchun Yu zongchun...@freescale.com --- meta-linaro/recipes-kernel/perf/perf.bbappend | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/meta-linaro/recipes-kernel/perf/perf.bbappend b/meta-linaro/recipes-kernel/perf/perf.bbappend index 7bf446a..cf7cb93 100644 --- a/meta-linaro/recipes-kernel/perf/perf.bbappend +++ b/meta-linaro/recipes-kernel/perf/perf.bbappend @@ -1,13 +1,13 @@ LICENSE = GPL-2 LIC_FILES_CHKSUM = file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7 -PV = 3.18.5 +PV = 4.0.2 FILESEXTRAPATHS_prepend := ${THISDIR}/files: -SRC_URI = ${DEBIAN_MIRROR}/main/l/linux-tools/linux-tools_3.18.5.orig.tar.xz +SRC_URI = ${DEBIAN_MIRROR}/main/l/linux-tools/linux-tools_4.0.2.orig.tar.xz -SRC_URI[md5sum] = c9ee8f5c1f88e562f1c1d6997c442c7f -SRC_URI[sha256sum] = bf79397874cc211e81eed47e2c2591632ba7b03d3de73aea867f2a78917b9720 +SRC_URI[md5sum] = 2bf7891f174843b40603395e94bde29d +SRC_URI[sha256sum] = 9c149a18e2d0ec3aba9200fdf49b124849a74130574e15abcb526f7481c2147e S = ${WORKDIR}/linux-tools-${PV} B = ${WORKDIR}/linux-tools-${PV}-build -- 1.8.3.2 ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [meta-linaro-toolchain][PATCH] binutils: remove '-2' from PR
Added to gerrit: https://review.linaro.org/7137 On 23 July 2015 at 05:23, b40...@freescale.com wrote: From: Zongchun Yu zongchun...@freescale.com Fix following Error: | DEBUG: Executing shell function BUILDSPEC | error: line 4: invalid tag value(^[A-Za-z0-9+._]+$) Release: Release: r2015.01-2 | error: Package has no %description: binutils-linaro+2.25.aarch64 | Building target platforms: aarch64-fsl-linux Signed-off-by: Zongchun Yu zongchun...@freescale.com --- .../recipes-devtools/binutils/binutils-linaro-2.25.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-linaro-toolchain/recipes-devtools/binutils/binutils-linaro-2.25.inc b/meta-linaro-toolchain/recipes-devtools/binutils/binutils-linaro-2.25.inc index 912d59a..96452e2 100644 --- a/meta-linaro-toolchain/recipes-devtools/binutils/binutils-linaro-2.25.inc +++ b/meta-linaro-toolchain/recipes-devtools/binutils/binutils-linaro-2.25.inc @@ -1,7 +1,7 @@ BPV = 2.25.0 MMYY = 15.01 RELEASE = 20${MMYY}-2 -PR = r${RELEASE} +PR = r20${MMYY} LIC_FILES_CHKSUM=\ file://COPYING;md5=59530bdf33659b29e73d4adb9f9f6552\ -- 1.8.3.2 ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 29
== Progress == * Deploy new layout for releases.l.o (10%) * Start meta-luv (60%) * Dragonboard support for meta-96boards (20%) * OE maintenance (10%) == Plans == * Find mind bleach to erase any recollection luv-yocto contents and quality. -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 28
== Progress == * Deploy new layout for releases.l.o * Integrated new linaro gcc into OE * Fixed OE build issues == Plans == * Start meta-luv -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 23
== Progress == * luvOS (60%) * boost breackage (30%) * new releases layout (10%) == Plans == -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 22
== Progress == 4 day week, so the amounts should add up to 80% instead of 100%. * 15.05 release (70%) * New layout for releases.linaro.org (DEVPLAT-366) (5%) * planned for 15.06 * OE (CARD-787) (5%) * empty gerrit queue * 96borads (1.25%) * Rebase to 4.1rc4 * Update atf/edk2 recipe == Plans == * release * meta-luv layer -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 21
== Progress == * New layout for releases.linaro.org (DEVPLAT-366) (60%) * received feedback from Fathi Vishal * moved to 15.06 * OE (CARD-787) (35%) * fix gator license breakage * partially merge ODP patches * Fix binutils in 'dora' branch * 96borads (5%) * Rebase to 4.1rc3 * Update atf/edk2 recipe == Plans == * release * meta-luv layer -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 19
== Progress == * New layout for releases.linaro.org (DEVPLAT-366) (65%) * OE (CARD-787) (20%) * verify merge window patches * DEVPLAT-270 (toolchain) (10%) * Added URLtrigger to CI job * Unsuccesfully tried to get recent binary toolchains working * 96borads (5%) * Rebase to 4.1rc2 * Merge pullrequests for meta-96boards layer * Update atf/edk2 recipe == Plans == * really deploy buildhistory to CI loop * Share layout proposal gdoc for feedback -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
Linaro 15.04 Available for download!
When I was a boy and I would see scary things in the news, my mother would say to me, ‘Look for the helpers. You will always find people who are helping. ~ Fred Rogers The Linaro 15.04 release is now available for download! See the detailed highlights of this release to get an overview of what has been accomplished by the Working Groups, Landing Teams and Platform Teams: * Linux Linaro 4.0-2015.04 is released: * based on v4.0 release * updated linaro-android topic: aosp/android-3.18 branch has been merged * GATOR topic: version 5.20.1 * updated integration-linaro-vexpress64 topic by ARM LT (FVP Base and Foundation models, and Juno support) * updated topic from Qualcomm LT (IFC6410 and DB410c boards support): * Resource Power Manager (RPM) - MSM Shared Memory Driver (SMD) driver * quite some changes under drivers/gpu/drm/ related to adv7511 and adv7533 support * ASoC support for QCOM platforms * external Connector Class (extcon) support (used for USB VBUS and ID detection) * Linaro builds of AOSP 15.04 is released: * baseline updated to android-5.1.1_r1 * updated Nexus 10 CI for LAVA testing * added Optimus A80 Android Kitkat build * Linaro OpenEmbedded 2015.04 is released: * removed stress recipe in favor of oe-core recipe * updated linux-linaro to ll_20150422.0 (based on 4.0) * libevent-fb: OE-core updated to 2.0.22, fix require statement * APM mustang boot failure (https://bugs.linaro.org/show_bug.cgi?id=1501) was tracked down to using 'arm64' as U-Boot arch for the initramfs header while the vendor U-Boot 2013.04 expects 'arm'. * upstreaming: * strace: fix build for aarch64 * libgpg-error 1.18: simplify tuple handling and add armv8b support * Linaro Ubuntu 15.04 is released: * updated packages: LSK 3.10.74/3.14.39 and linux-linaro 4.0 kernels * U-Boot: upstream fastboot support: * Add HiSilicon D01 platform support to Debian installer: * Updated android-build job to work with docker slaves * Cleaned up ILP32 build job * LSK: enable debug options on regular builds * linux-linaro: ll-fold.sh script fixed to work correctly with newer git versions * CI bring up: tshark board Android member build * Added Ubuntu arm64 gnome rootfs * Added D01 platform to Coresight CI loop The release details are linked from the “Details” column for each released artifact on the release information: http://wiki.linaro.org/Cycles/1504/Release#Release_Information Using the Android-based images === The Android-based images come in three parts: system, userdata and boot. These need to be combined to form a complete Android install. For an explanation of how to do this please see: http://wiki.linaro.org/Platform/Android/ImageInstallation If you are interested in getting the source and building these images yourself please see the following pages: http://wiki.linaro.org/Platform/Android/GetSource http://wiki.linaro.org/Platform/Android/BuildSource Using the OpenEmbedded-based images === With the Linaro provided downloads and with ARM’s Fast Models virtual platform, you can boot a virtual ARMv8 system and run 64-bit binaries. For more information please see: http://www.linaro.org/engineering/armv8 Using the Ubuntu-based images === The Ubuntu-based images consist of two parts. The first part is a hardware pack, which can be found under the hwpacks directory and contains hardware specific packages (such as the kernel and bootloader). The second part is the rootfs, which is combined with the hardware pack to create a complete image. For more information on how to create an image please see: http://wiki.linaro.org/Platform/DevPlatform/Ubuntu/ImageInstallation Getting involved More information on Linaro can be found on our websites: * Homepage: http://www.linaro.org * Wiki: http://wiki.linaro.org Also subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro developments: * Announcements: http://lists.linaro.org/mailman/listinfo/linaro-announce * Development: http://lists.linaro.org/mailman/listinfo/linaro-dev * IRC: #linaro on irc.linaro.org or irc.freenode.net #linaro-android irc.linaro.org or irc.freenode.net Known issues with this release = For any errata issues, please see: http://wiki.linaro.org/Cycles/1504/Release#Known_Issues Bug reports for this release should be filed in Bugzilla (http://bugs.linaro.org) against the individual packages or projects that are affected. On behalf of the release team, Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 16
== Progress == * OE (CARD-787) (20%) * fix strace build * DEVPLAT-319 (buildhistory) (25%) * DEVPLAT-270 (toolchain) (45%) * Added URLtrigger to CI job * Unsuccesfully tried to get recent binary toolchains working * 96borads (10%) * Rebase to post 4.0 * Update meta-96boards layer == Plans == * deploy buildhistory to CI loop -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 12
== Progress == * OE (CARD-787) (60%) * debug grub gcc ICE with TCWG - FIXED (https://bugs.linaro.org/show_bug.cgi?id=1254) * DEVPLAT-332 (uefi) (5%) * Address gcc 4.9 issues * Deploy all the .bin files, not just fip.bin * DEVPLAT-270 (toolchain) (30%) * Get bitten by layout change, again * Add URLTrigger to CI job. * 96borads (5%) * Rebase to 4.0rc4 * Update meta-96boards layer * Add l-loader recipe == Plans == * release * vacation -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 11
== Progress == * OE (CARD-787) (10%) * debug grub gcc ICE with TCWG ( https://bugs.linaro.org/show_bug.cgi?id=1254) * Add full wget to LAMP image (https://bugs.linaro.org/show_bug.cgi?id=1288 ) * DEVPLAT-265 (meta-aarch64) (60%) * Delete obsolete bbappends * Try to upstream changes (again) * Split out meta-ilp32 * DEVPLAT-337 (meta-bigendian) (20%) * Delete obsolete bbappends * Try to upstream changes (again) * DEVPLAT-332 (uefi) (5%) * Recipe for hikey created and working * 96borads (5%) * Rebase to 4.0rc3 * Update meta-96boards layer * Discuss kernel tree * Triage bugs == Plans == * DEVPLAT-332 (uefi) * Expand recipe to build for all uefi-linaro targets * DEVPLAT-337 (meta-bigendian) * Delete obsolete bbappends * Try to upstream changes * 96borads * integrate wilink MAC address fix from Fathi into meta-96boards * Wait for 4.0 targeted patches from hisilicon ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 10
== Progress == * Release 15.02 (DEVPLAT-312) (1%) * OE (CARD-787) (93%) * Fix mozjs build for aarch64 * debug grub gcc ICE with TCWG * 96borads (5%) * Rebase to 4.0rc2 * Update meta-96boards layer * Discuss kernel tree == Plans == ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 9
== Progress == * Release 15.02 (DEVPLAT-312) (90%) * OE (CARD-787) (30%) * Fix RC builds * 96borads (10%) * Boot 4.0rc * Update meta-96boards layer == Plans == Fix issues before the weekend starts. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 8
== Progress == * OE (CARD-787) * work around linux-dummy problems * fix perf build * work around openvswitch issues * drop snort from lng build * Triggered ILP32 build * 96borads * Fixed MMC bus-width on hikey * integrated UIM patches into BSP == Plans == * Convert more CI jobs to yaml * Add blueprints ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 5
== Progress == * Release (80%) * TC2 boot failure caused some pain * Sorting out 32 * 3 kernel branches (20%) == Plans == * FOSDEM -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 4
== Progress == * OpenEmbedded (90%) * Build failures (CARD-787 https://cards.linaro.org/browse/CARD-787) * OE Training * Despairing at vendor kernels (10%) == Plans == * Release * BB sprint * FOSDEM -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [meta-linaro v2 2/2] genericarmv8: build the ext3 image by default
On 21 January 2015 at 09:09, Kevin Hao kexin@windriver.com wrote: This is needed when we want to boot from qeumu. Signed-off-by: Kevin Hao kexin@windriver.com --- v2: Don't build qemu-native by default. v1: http://lists.linaro.org/pipermail/linaro-dev/2015-January/017738.html meta-aarch64/conf/machine/genericarmv8.conf | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta-aarch64/conf/machine/genericarmv8.conf b/meta-aarch64/conf/machine/genericarmv8.conf index 1d05238d8c04..a1b63fb681cf 100644 --- a/meta-aarch64/conf/machine/genericarmv8.conf +++ b/meta-aarch64/conf/machine/genericarmv8.conf @@ -35,3 +35,5 @@ FEATURE_PACKAGES_autoserial = auto-serial-console # we do not want to have getty running on tty1 as we run # auto-serial-console there USE_VT = 0 + +IMAGE_FSTYPES += ext3 I'm still not convinced this needs to be by default, it's easy enough to do in local.conf. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [meta-linaro 1/2] qemu: drop it to use the one in oe-core
Added to gerrit: https://review.linaro.org/4339 On 19 January 2015 at 12:29, Kevin Hao kexin@windriver.com wrote: The qemu in oe-core has updated to the latest version and also has the system mode support for aarch64. Signed-off-by: Kevin Hao kexin@windriver.com --- .../3f08ffb4a4741d147634761dc053ed386243a0de.patch | 42 --- .../qemu/files/enable-i386-linux-user.patch| 55 -- .../recipes-devtools/qemu/files/fdt_header.patch | 39 -- .../fix-libcap-header-issue-on-some-distro.patch | 84 - .../recipes-devtools/qemu/files/init-info.patch| 18 - .../qemu/files/larger_default_ram_size.patch | 22 -- .../recipes-devtools/qemu/files/no-strip.patch | 15 .../recipes-devtools/qemu/files/powerpc_rom.bin| Bin 4096 - 0 bytes .../qemu/files/relocatable_sdk.patch | 34 - ...-Fix-aflag-logic-for-CODE64-and-the-0x67-.patch | 79 --- .../qemu/files/target-ppc_fix_bit_extraction.patch | 70 - meta-linaro/recipes-devtools/qemu/qemu_git.bb | 25 -- 12 files changed, 483 deletions(-) delete mode 100644 meta-linaro/recipes-devtools/qemu/files/3f08ffb4a4741d147634761dc053ed386243a0de.patch delete mode 100644 meta-linaro/recipes-devtools/qemu/files/enable-i386-linux-user.patch delete mode 100644 meta-linaro/recipes-devtools/qemu/files/fdt_header.patch delete mode 100644 meta-linaro/recipes-devtools/qemu/files/fix-libcap-header-issue-on-some-distro.patch delete mode 100644 meta-linaro/recipes-devtools/qemu/files/init-info.patch delete mode 100644 meta-linaro/recipes-devtools/qemu/files/larger_default_ram_size.patch delete mode 100644 meta-linaro/recipes-devtools/qemu/files/no-strip.patch delete mode 100644 meta-linaro/recipes-devtools/qemu/files/powerpc_rom.bin delete mode 100644 meta-linaro/recipes-devtools/qemu/files/relocatable_sdk.patch delete mode 100644 meta-linaro/recipes-devtools/qemu/files/target-i386-Fix-aflag-logic-for-CODE64-and-the-0x67-.patch delete mode 100644 meta-linaro/recipes-devtools/qemu/files/target-ppc_fix_bit_extraction.patch delete mode 100644 meta-linaro/recipes-devtools/qemu/qemu_git.bb diff --git a/meta-linaro/recipes-devtools/qemu/files/3f08ffb4a4741d147634761dc053ed386243a0de.patch b/meta-linaro/recipes-devtools/qemu/files/3f08ffb4a4741d147634761dc053ed386243a0de.patch deleted file mode 100644 index 4390b943b97c.. --- a/meta-linaro/recipes-devtools/qemu/files/3f08ffb4a4741d147634761dc053ed386243a0de.patch +++ /dev/null @@ -1,42 +0,0 @@ -Upstream-Status: Backport - -[Appears to fix the random segfaults we were seeing in a variety of architectures: -https://bugzilla.yoctoproject.org/show_bug.cgi?id=4216 ] - - -From: Yeongkyoon Lee yeongkyoon@samsung.com -Date: Fri, 22 Mar 2013 12:50:17 + (+0900) -Subject: tcg: Fix occasional TCG broken problem when ldst optimization enabled -X-Git-Url: http://git.qemu.org/?p=qemu.git;a=commitdiff_plain;h=52ae646d4a3ebdcdcc973492c6a56f2c49b6578f;hp=3f08ffb4a4741d147634761dc053ed386243a0de - -tcg: Fix occasional TCG broken problem when ldst optimization enabled - -is_tcg_gen_code() checks the upper limit of TCG generated code range wrong, so -that TCG could get broken occasionally only when CONFIG_QEMU_LDST_OPTIMIZATION -enabled. The reason is code_gen_buffer_max_size does not cover the upper range -up to (TCG_MAX_OP_SIZE * OPC_BUF_SIZE), thus code_gen_buffer_max_size should be -modified to code_gen_buffer_size. - -CC: qemu-sta...@nongnu.org -Signed-off-by: Yeongkyoon Lee yeongkyoon@samsung.com -Reviewed-by: Peter Maydell peter.mayd...@linaro.org -Signed-off-by: Aurelien Jarno aurel...@aurel32.net - -Index: qemu-1.4.0/translate-all.c -=== qemu-1.4.0.orig/translate-all.c2013-04-09 10:58:19.0 + -+++ qemu-1.4.0/translate-all.c 2013-04-09 10:58:34.783203406 + -@@ -1310,10 +1310,10 @@ - /* check whether the given addr is in TCG generated code buffer or not */ - bool is_tcg_gen_code(uintptr_t tc_ptr) - { --/* This can be called during code generation, code_gen_buffer_max_size -+/* This can be called during code generation, code_gen_buffer_size -is used instead of code_gen_ptr for upper boundary checking */ - return (tc_ptr = (uintptr_t)code_gen_buffer --tc_ptr (uintptr_t)(code_gen_buffer + code_gen_buffer_max_size)); -+tc_ptr (uintptr_t)(code_gen_buffer + code_gen_buffer_size)); - } - #endif - diff --git a/meta-linaro/recipes-devtools/qemu/files/enable-i386-linux-user.patch b/meta-linaro/recipes-devtools/qemu/files/enable-i386-linux-user.patch deleted file mode 100644 index bb0d6a384845.. --- a/meta-linaro/recipes-devtools/qemu/files/enable-i386-linux-user.patch +++ /dev/null @@ -1,55 +0,0 @@ -Enable
[ACTIVITY] Week 3
== Progress == * OpenEmbedded (100%) * Build failures (CARD-787 https://cards.linaro.org/browse/CARD-787) * gcc in dizzy branch * OE Training == Plans == * Prebuilt toolchain testing (CARD-1728) * Prepare and give OE training * add latest gcc-linaro -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [meta-linaro] bootwrapper: fix the configure error
Added to gerrit: https://review.linaro.org/4295 On 15 January 2015 at 11:36, Kevin Hao kexin@windriver.com wrote: Since kernel commit ca5b34100c57 (dts, arm64: Move dts files to vendor subdirs), the default dtb directory in bootwrapper is not matched with the kernel and it would provoke the following error when checking the dtb in configure: checking for build/arch/arm64/boot/dts/rtsm_ve-aemv8a.dtb... no configure: error: No such file or directory: build/arch/arm64/boot/dts/rtsm_ve-aemv8a.dtb WARNING: temp/run.do_compile.5170:1 exit 1 from The latest bootwrapper adds a --with-dtb to override the default dtb in configure.ac. So update the bootwrapper to the latest version and use the --with-dtb option to workaround this build issue. Signed-off-by: Kevin Hao kexin@windriver.com --- meta-linaro/recipes-kernel/linux/bootwrapper.inc | 19 --- 1 file changed, 12 insertions(+), 7 deletions(-) diff --git a/meta-linaro/recipes-kernel/linux/bootwrapper.inc b/meta-linaro/recipes-kernel/linux/bootwrapper.inc index cbe5a068255d..627c320bbce6 100644 --- a/meta-linaro/recipes-kernel/linux/bootwrapper.inc +++ b/meta-linaro/recipes-kernel/linux/bootwrapper.inc @@ -1,7 +1,7 @@ SRC_URI_append= git:// git.kernel.org/pub/scm/linux/kernel/git/cmarinas/boot-wrapper-aarch64.git;protocol=http;branch=master;name=bootwrapper;destsuffix=bootwrapper \ -SRCREV_bootwrapper = 2ff0b45423226d3de898a52a81b8e90b20fecd60 +SRCREV_bootwrapper = 26a17ad59544f026878efdb0524ce66b7a314784 BW = ${WORKDIR}/bootwrapper DTBDIR=${B}/arch/arm64/boot/dts/ @@ -24,26 +24,31 @@ do_compile_append() { export LDFLAGS=${WRAPLDFLAGS} autoreconf -vfi +dtb=`find ${DTBDIR} -type f -name foundation-v8.dtb` ./configure --host=aarch64-linux-gnu \ --with-kernel-dir=${B} \ ---with-cmdline=${BOOTARGS_COMMON} root=/dev/vda +--with-cmdline=${BOOTARGS_COMMON} root=/dev/vda \ +--with-dtb=${dtb} make IMAGE=linux-system-foundation.axf clean make DTC=${B}/scripts/dtc/dtc \ - KERNEL_DTB=`find ${DTBDIR} -type f -name foundation-v8.dtb` \ + KERNEL_DTB=${dtb} \ IMAGE=linux-system-foundation.axf make IMAGE=img-foundation.axf clean ./configure --host=aarch64-linux-gnu \ --with-kernel-dir=${B} \ ---with-cmdline=${BOOTARGS_COMMON} root=/dev/vda2 +--with-cmdline=${BOOTARGS_COMMON} root=/dev/vda2 \ +--with-dtb=${dtb} make DTC=${B}/scripts/dtc/dtc \ - KERNEL_DTB=`find ${DTBDIR} -type f -name foundation-v8.dtb` \ + KERNEL_DTB=${dtb} \ IMAGE=img-foundation.axf make IMAGE=img.axf clean +dtb=`find ${DTBDIR} -type f -name rtsm_ve-aemv8a.dtb` ./configure --host=aarch64-linux-gnu \ --with-kernel-dir=${B} \ ---with-cmdline=${BOOTARGS_COMMON} root=/dev/mmcblk0p2 +--with-cmdline=${BOOTARGS_COMMON} root=/dev/mmcblk0p2 \ +--with-dtb=${dtb} make DTC=${B}/scripts/dtc/dtc \ - KERNEL_DTB=`find ${DTBDIR} -type f -name rtsm_ve-aemv8a.dtb` \ + KERNEL_DTB=${dtb} \ IMAGE=img.axf } -- 1.9.3 ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 2
== Progress == * OpenEmbedded (90%) * Build failures (CARD-787 https://cards.linaro.org/browse/CARD-787) * linux-linaro * libatomic-ops * gcc in dizzy branch * Toolchain * integrated binutils 2.25 * Release (10%) * Discuss 'latest' symlink issue == Plans == * Fix ALIP * Prebuilt toolchain testing (CARD-1728) * Prepare OE training -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [meta-linaro][PATCH 0/2] fix the build errors for aarch64 kernel
Thanks, added to gerrit: https://review.linaro.org/4183 https://review.linaro.org/4184 On 31 December 2014 at 06:58, Kevin Hao kexin@windriver.com wrote: Hi, I am not sure if this is the right list for these patches. If not, please point me to the right one. :-) I tried to build a linaro aarch64 kernel with the latest oe-core, but got several build errors. This patch series fix these errors. Kevin Hao (2): bootwrapper: use ${B} when building and referencing to dtbs linux-linaro-aarch64: change to source directory before merging config files meta-linaro/recipes-kernel/linux/bootwrapper.inc | 15 +++ meta-linaro/recipes-kernel/linux/linux-linaro-aarch64.bb | 2 ++ 2 files changed, 9 insertions(+), 8 deletions(-) -- 1.9.3 ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [meta-linaro-toolchain][dizzy][PATCH] gdb-cross_linaro-7.8: remove elf_prstatus-size.patch
Thanks, added to gerrit: https://review.linaro.org/4135 On 30 December 2014 at 16:20, Max Krummenacher max.oss...@gmail.com wrote: elf_prstatus-size.patch no longer applies as the patched file no longer exists. The patched code now resides in gdb-linaro-7.8-2014.09/bfd/elfxx-aarch64.c with the patch already applied. ERROR: Command Error: exit status: 1 Output: Applying patch elf_prstatus-size.patch can't find file to patch at input line 5 Signed-off-by: Max Krummenacher max.oss...@gmail.com --- .../recipes-devtools/gdb/gdb-7.8/elf_prstatus-size.patch| 13 - .../recipes-devtools/gdb/gdb-cross_linaro-7.8.bb| 1 - 2 files changed, 14 deletions(-) delete mode 100644 meta-linaro-toolchain/recipes-devtools/gdb/gdb-7.8/elf_prstatus-size.patch diff --git a/meta-linaro-toolchain/recipes-devtools/gdb/gdb-7.8/elf_prstatus-size.patch b/meta-linaro-toolchain/recipes-devtools/gdb/gdb-7.8/elf_prstatus-size.patch deleted file mode 100644 index 857e94d..000 --- a/meta-linaro-toolchain/recipes-devtools/gdb/gdb-7.8/elf_prstatus-size.patch +++ /dev/null @@ -1,13 +0,0 @@ -Index: gdb-linaro-7.6.1-2013.10/bfd/elf64-aarch64.c -=== gdb-linaro-7.6.1-2013.10.orig/bfd/elf64-aarch64.c -+++ gdb-linaro-7.6.1-2013.10/bfd/elf64-aarch64.c -@@ -1529,7 +1529,7 @@ elf64_aarch64_grok_prstatus (bfd *abfd, - default: - return FALSE; - -- case 408: /* sizeof(struct elf_prstatus) on Linux/arm64. */ -+ case 392: /* sizeof(struct elf_prstatus) on Linux/arm64. */ - /* pr_cursig */ - elf_tdata (abfd)-core-signal - = bfd_get_16 (abfd, note-descdata + 12); diff --git a/meta-linaro-toolchain/recipes-devtools/gdb/ gdb-cross_linaro-7.8.bb b/meta-linaro-toolchain/recipes-devtools/gdb/ gdb-cross_linaro-7.8.bb index 12ffe4c..b2003b4 100644 --- a/meta-linaro-toolchain/recipes-devtools/gdb/gdb-cross_linaro-7.8.bb +++ b/meta-linaro-toolchain/recipes-devtools/gdb/gdb-cross_linaro-7.8.bb @@ -2,4 +2,3 @@ require recipes-devtools/gdb/gdb-cross.inc require gdb-${PV}.inc SRC_URI += file://sim-install-6.6.patch -SRC_URI += file://elf_prstatus-size.patch -- 1.8.4.5 ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [meta-linaro-toolchain] gcc-source: import of gcc-source.inc fails
Op 6 dec. 2014, om 01:13 heeft Sven Ebenfeld sven.ebenf...@gmail.com het volgende geschreven: Am 05.12.2014 um 09:43 schrieb Koen Kooi: On 5 December 2014 at 09:37, Sven Ebenfeld sven.ebenf...@gmail.com wrote: Hi, I hope, this is the right mailing-list for my issue. If not, please tell me how to find the correct one. Unfortunately it is not mentioned in the README of meta-linaro. After the merge last night, I'm unable to use meta-linaro-toolchain layer as bitbake tries to find gcc-source.inc but this file is missing. Or do I need to import a different layer that is missing in Layer Dependency of layer.conf file? That file is in OE-core, are you using meta-linaro-toolchain against an older OE-core branch like 'daisy' or 'dizzy'? Yes, that is what I am doing. I use meta-linaro-toolchain with dizzy branch of OE-Core. There is no dizzy branch in meta-linaro. Yes there is: https://git.linaro.org/openembedded/meta-linaro.git/shortlog/refs/heads/dizzy -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [meta-linaro-toolchain] gcc-source: import of gcc-source.inc fails
On 5 December 2014 at 09:37, Sven Ebenfeld sven.ebenf...@gmail.com wrote: Hi, I hope, this is the right mailing-list for my issue. If not, please tell me how to find the correct one. Unfortunately it is not mentioned in the README of meta-linaro. After the merge last night, I'm unable to use meta-linaro-toolchain layer as bitbake tries to find gcc-source.inc but this file is missing. Or do I need to import a different layer that is missing in Layer Dependency of layer.conf file? That file is in OE-core, are you using meta-linaro-toolchain against an older OE-core branch like 'daisy' or 'dizzy'? regards, Koen ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 49
== Progress == * OpenEmbedded (90%) * Build failures (CARD-787 https://cards.linaro.org/browse/CARD-787) * Prebuilt toolchain testing (CARD-1728) * Branched meta-linaro for 'dizzy' * Release (10%) * Various fixups (broken links, wiki et cetera) == Plans == * OpenEmbedded * Prebuilt toolchain testing (CARD-1728) * ILP32 -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 46
== Progress == * OpenEmbedded (100%) * OpenJDK build failures (CARD-787 https://cards.linaro.org/browse/CARD-787) * Prebuilt toolchain testing (CARD-1728) == Plans == * Release * OpenEmbedded * eglibc - glibc move (CARD-787 https://cards.linaro.org/browse/CARD-787 ) * update gcc (CARD-787 https://cards.linaro.org/browse/CARD-787) * update binutils (CARD-787 https://cards.linaro.org/browse/CARD-787) * Prebuilt toolchain testing (CARD-1728) -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 46
== Progress == * OpenEmbedded (100%) * minimal + lamp images build again * Partially fix openjdk build. * Prebuilt toolchain CI loop working (CARD-1728) == Plans == * eglibc-linaro - glibc-linaro switch -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 45
== Progress == * OpenEmbedded (100%) * Fix issues with 'make clean' change * Fix issues with gcc sysroot poisoning * Prebuilt toolchain testing (CARD-1728) == Plans == Same as above -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 44
== Progress == * Release (80%) * The usual, lots of release note updates. * Day off (20%) == Plans == -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 42
== Progress == * OE (80%) * debug multi-git fetch issues * add gcc 4.9 2014.10 * prebuilt toolchain (REQ-583) * Release (10%) * Deploy gcc * fix permissions in older releases == Plans == * release -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 42
== Progress == * ELC-E (90%) * Release (10%) * Fix android directories and other issues == Plans == * Bugzilla backlog * OE build warnings * LEG CI -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 41
== Progress == * Release (20%) * add links for bare metal toolchain (Bug 719) * fix permission issue for 14.06 toolchain (Bug 745) * remove some more launchpad references * release note updates * OE baseline work (CARD-787: 80%) * All builds seem to be OK * Going through all the warnings and fix them == Plans == * ELC-E -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 39
== Progress == * Release (100%) == Plans == * Fix openjdk build -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 35
== Progress == * OE baseline work (CARD-787: 20%) * Release (80%) * CARD-1566 (5%) == Plans == Vacation! == Issues == ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [ACTIVITY] Week 34
Op 22 aug. 2014, om 11:56 heeft Bernhard Rosenkränzer bernhard.rosenkran...@linaro.org het volgende geschreven: == Progress == * Fixed build failures caused by 2014.08 based Android toolchains * Rewrote NDK build scripts to build everything from source instead of patching the upstream release (allowing us to build from master branch) * Created reduced test cases for compiler issues * Worked on cbuild2 toolchain releases With the switch to cbuild2 can we please get rid of the timestamp in the filename? It causing me a lot of pain when updating the links. No one cares on which day it was built and only leads to questions like why is the BE toolchain newer? when the build crossed midnight :/ Bad: gcc-linaro-arm-linux-gnueabihf-4.9-2014.07-20140723_win32.exe Good: gcc-linaro-arm-linux-gnueabihf-4.9-2014.07_win32.exe Thanks, -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 34
== Progress == * OE baseline work (CARD-787: 90%) * Release (5%) * CARD-1566 (5%) == Plans == * release == Issues == ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 32
== Progress == * OE baseline work (CARD-787: 50%) * Release (10%) * CARD-1566 (40%) == Plans == * CARD-1566 https://cards.linaro.org/browse/CARD-1566 == Issues == ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 31
== Progress == * OE baseline work (CARD-787: 10%) * Release (90%) == Plans == * CARD-1566 https://cards.linaro.org/browse/CARD-1566 * integrate 2014.08 toolchain == Issues == * People keep forgetting to put me in CC: for release issues causing premature escalation ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] Week 30
== Progress == * OE baseline work (CARD-787: 80%) * Release (10%) * Update release scripts * Downloads page discussion == Plans == * Release == Issues == ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [meta-linaro-toolchain][PATCH] external-linaro-toolchain: add more rprovides
This doesn't apply, which revision/branch is this against? On 16 July 2014 08:14, b40...@freescale.com wrote: From: Zongchun Yu zongchun...@freescale.com This avoids eglibc being rebuilt when trying to include packages like eglibc-utils. Signed-off-by: Zongchun Yu zongchun...@freescale.com --- .../external-linaro-toolchain/external-linaro-toolchain.bb| 8 1 file changed, 8 insertions(+) diff --git a/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/ external-linaro-toolchain.bb b/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/ external-linaro-toolchain.bb index bb4cfae..8ac929c 100644 --- a/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/ external-linaro-toolchain.bb +++ b/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/ external-linaro-toolchain.bb @@ -145,8 +145,11 @@ PACKAGES =+ \ libitm \ libitm-dev \ libitm-staticdev \ + eglibc-utils \ +ALLOW_EMPTY_eglibc-utils = 1 + INSANE_SKIP_${PN}-dbg = staticdev INSANE_SKIP_${PN}-utils += ldflags INSANE_SKIP_libstdc++ += ldflags @@ -166,7 +169,12 @@ PKG_${PN}-thread-db = eglibc-thread-db PKG_${PN}-pcprofile = eglibc-pcprofile PKG_${PN}-staticdev = eglibc-staticdev +RPROVIDES_${PN} += ${TCLIBC} RPROVIDES_${PN}-mtrace += ${TCLIBC}-mtrace +RPROVIDES_${PN}-staticdev += ${TCLIBC}-staticdev +RPROVIDES_${PN}-dev += ${TCLIBC}-dev +RPROVIDES_${PN}-dbg += ${TCLIBC}-dbg +RPROVIDES_${PN}-utils += ${TCLIBC}-utils PKGV_${PN} = ${ELT_VER_LIBC} PKGV_${PN}-dev = ${ELT_VER_LIBC} -- 1.8.3.2 ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[Activity] week 24
== Progress == * OE baseline work (CARD-787: 80%) * ODP work * Patch review * Juno CI loop (CARD-1441: 20%) -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[Activity] week 27
== Progress == * OE baseline work (CARD-787: 60%) * GCC 4.9 BE update * Juno (40%) == Plans == * OE toolchain updates == Issues == -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[Activity] week 25
== Progress == * OE baseline work (CARD-787: 100%) * OE-core binconfig fixes == Plans == * Release == Issues == -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[Activity] week 23
== Progress == * OE baseline work (CARD-787: 90%) * GCC 4.9 integration * Patch review * Juno CI loop (CARD-1441: 10%) == Plans == * Finish Juno CI loop == Issues == * CI maintenance -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[Activity] week 22
== Progress == * Release 14.05 166% (one holiday and one vacation day went *poof*) == Plans == * Bug triage == Issues == * Release slipped due to cbuildv2 and aarch64 problems ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[ACTIVITY] week 21
== Progress == * Fix OE merge window build breakages. (CARD-787: 50%) * Moved DISTRO type items into meta-linaro-integration. (CARD-1214: 40%) * On-target git fixes (5%) * Release scripts (5%) == Plans == * Close out CARD-1214 * Release Linaro 14.05 == Issues == * None -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [dora][PATCH] eglibc: accept GNU make version 4 or later (backport from 2.19)
Op 15 apr. 2014, om 05:37 heeft Denys Dmytriyenko de...@denix.org het volgende geschreven: From: Denys Dmytriyenko de...@ti.com Matches following commits from OE-Core: 9d59ceab6e58b422caf8ad7a306ed546316d8c3a bdc49826edf05233c6d506de404861a661043b1b Signed-off-by: Denys Dmytriyenko de...@ti.com Added into gerrit: https://review.linaro.org/1635 -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs --- This is only applicable to dora, since master already has eglibc-2.19 meta-linaro-toolchain/recipes-core/eglibc/eglibc_2.17.bbappend | 3 ++- meta-linaro-toolchain/recipes-core/eglibc/eglibc_2.18.bbappend | 1 + 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/meta-linaro-toolchain/recipes-core/eglibc/eglibc_2.17.bbappend b/meta-linaro-toolchain/recipes-core/eglibc/eglibc_2.17.bbappend index 9317ca1..14f28c8 100644 --- a/meta-linaro-toolchain/recipes-core/eglibc/eglibc_2.17.bbappend +++ b/meta-linaro-toolchain/recipes-core/eglibc/eglibc_2.17.bbappend @@ -1,6 +1,6 @@ MMYY = 13.07 RELEASE = 20${MMYY}-2 -PR = r5 +PR = r6 SRC_URI = http://releases.linaro.org/${MMYY}/components/toolchain/eglibc-linaro/eglibc-linaro-${PV}-${RELEASE}.tar.bz2 \ file://eglibc-svn-arm-lowlevellock-include-tls.patch \ @@ -26,6 +26,7 @@ SRC_URI = http://releases.linaro.org/${MMYY}/components/toolchain/eglibc-linaro file://tzselect-awk.patch \ file://0001-eglibc-run-libm-err-tab.pl-with-specific-dirs-in-S.patch \ file://fix-tibetian-locales.patch \ + file://make-4.patch \ SRC_URI[md5sum] = 6968b95121db1cffd147e07d6c55bffd diff --git a/meta-linaro-toolchain/recipes-core/eglibc/eglibc_2.18.bbappend b/meta-linaro-toolchain/recipes-core/eglibc/eglibc_2.18.bbappend index d4f7db4..e6c9fa5 100644 --- a/meta-linaro-toolchain/recipes-core/eglibc/eglibc_2.18.bbappend +++ b/meta-linaro-toolchain/recipes-core/eglibc/eglibc_2.18.bbappend @@ -27,6 +27,7 @@ SRC_URI = http://releases.linaro.org/${MMYY}/components/toolchain/eglibc-linaro file://0001-eglibc-run-libm-err-tab.pl-with-specific-dirs-in-S.patch \ file://fix-tibetian-locales.patch \ file://0001-ARM-Pass-dl_hwcap-to-IFUNC-resolver.patch \ + file://make-4.patch \ SRC_URI[md5sum] = 3effe2d563db9dcf6f789db647d1b03d -- 1.9.2 ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: auto-serial-console
Op 17 okt. 2013, om 10:03 heeft Nicolas Dechesne nicolas.deche...@linaro.org het volgende geschreven: koen, fathi, riku, i am having issues with auto-serial-console that was initially done by marcin. https://git.linaro.org/gitweb?p=openembedded/meta-linaro.git;a=tree;f=meta-linaro/recipes-linaro/auto-serial-console;hb=master the main issue is that it conflicts with BSP layer that uses SERIAL_CONSOLE variable. It is very much expected for a BSP layer to set SERIAL_CONSOLE variable. In which case OE will automatically start a serial console http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-core/sysvinit/sysvinit-inittab_2.88dsf.bb So when using auto-serial-console with a 'proper' BSP layer that set SERIAL_CONSOLE(S) we end up with starting the console twice, one added by OE, one by auto-serial-console. So far, all our OE builds are not using a proper BSP layer, so that's why you don't see the problem, but for our builds we use proper BSP layer... right now, auto-serial-console does 3 things: 1- figure out the serial console port from /proc/cmdline 2- start a console on #1 3- automatically login as root I believe that we should 'do something' to split them into several packages so that we get more granularity. At least #3 needs to be separated out, as #3 is a 'policy'. The recipe itself is already a policy thing, so we should look into a way to have different images for proper builds (using BSPs) and hwpack based deployments. This will also make non-linaro users of our layers happy. I would almost expect that 'being able to automatically login as root on the console' is a feature that could (should?) be added to oe-core somehow. What do you think koen? I agree I looked into that, but there isn't any obvious (and trivial) way to do that, but it's certainly doable inside an IMAGE_FEATURE for example. Right. But keep in mind that sysv is not the only init system supported in oe-core. FWIW, systemd already autospawns a getty on every entry listed in the console= kernel cmdline. regards, Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs this email is just to start the discussion and get some advices, e.g. i am not asking you to do it ;-) i can work on it, but want to make sure i do it right, with an 'upstream' path if possible. thx nico ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: auto-serial-console
Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs Op 17 okt. 2013, om 11:02 heeft Nicolas Dechesne nicolas.deche...@linaro.org het volgende geschreven: On Thu, Oct 17, 2013 at 10:20 AM, Koen Kooi koen.k...@linaro.org wrote: right now, auto-serial-console does 3 things: 1- figure out the serial console port from /proc/cmdline 2- start a console on #1 3- automatically login as root I believe that we should 'do something' to split them into several packages so that we get more granularity. At least #3 needs to be separated out, as #3 is a 'policy'. The recipe itself is already a policy thing, so we should look into a way to have different images for proper builds (using BSPs) and hwpack based deployments. This will also make non-linaro users of our layers happy. well, i am a non happy, linaro user ;-) I would almost expect that 'being able to automatically login as root on the console' is a feature that could (should?) be added to oe-core somehow. What do you think koen? I agree I looked into that, but there isn't any obvious (and trivial) way to do that, but it's certainly doable inside an IMAGE_FEATURE for example. Right. But keep in mind that sysv is not the only init system supported in oe-core. FWIW, systemd already autospawns a getty on every entry listed in the console= kernel cmdline. ok. so why then do we have this: http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-core/systemd/systemd-serialgetty.bb it's 'just in case' the kernel does not have console=xxx but SERIAL_CONSOLE is defined? what's the use case? It's as you say, to spawn a serial console regardless of console= parameters. It's analogous to having a getty in inittab. if systemd-getty-generator finds a console=xxx and if SERIAL_CONSOLE is defined, i assume we don't get 2 getty, but one. is systemd-getty-generator taking care of such situations? So far it seems to work, so I guess the clash of 2 rules trying to run a getty on the same port is somehow resolved internally in systemd. Since it just works for me I haven't looked into it :) regards, Koen ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Cross Compiling Linux genericarmv8 3.10.1.0-1-linaro-vexpress64
Op 9 okt. 2013, om 13:43 heeft Anil Singhar anil.sing...@linaro.org het volgende geschreven: Hi Fathi, Thanks for your response. I tried what you asked. Here is the output: anilss@anilss:~/linaro/openembedded$ cd jenkins-setup/ anilss@anilss:~/linaro/openembedded/jenkins-setup$ bash init-and-build.sh GCC version: 4.8 Target architecture: armv8 object e76efdd7b342577c40aa271fa5ded9d66a783a9b type commit tag v1.12.4 tagger Conley Owens c...@android.com 1380645867 -0700 repo 1.12.4 gpg: Signature made Tuesday 01 October 2013 10:14:27 PM IST using RSA key ID 692B382C gpg: Can't check signature: public key not found error: could not verify the tag 'v1.12.4' 'repo' is broken upstream, have a look at http://stackoverflow.com/questions/19126603/android-source-repo-gpg-public-key-not-found reagards, Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [RFC 1/3] pinctrl: add a driver for the OMAP pinmux
Op 22 nov. 2011, om 18:54 heeft Tony Lindgren het volgende geschreven: * Linus Walleij linus.wall...@linaro.org [22 03:30]: On Tue, Nov 22, 2011 at 12:09 PM, Thomas Abraham thomas.abra...@linaro.org wrote: On 17 November 2011 19:27, Linus Walleij linus.wall...@linaro.org wrote: Maybe I'm mistaken about the device tree ambitions, but I was sort of hoping that it would not contain too much custom magic numbers that need to be cross-referenced elsewhere ... or rather - the more understandable the device tree is, the more we win. Device tree is expected to describe the hardware. So to cross-reference the hardware manual to understand device tree should be fine I guess. For instance, GPIO numbers in dts would be written as a numeric number and not a enum or other format. And by looking up the manual, we understand the actual details of the GPIO pin. If dt-compiler had a option to support #define like in C, the numbers could have been made more easier to understand. Like, 3 to mean GPIO_PULL_UP in Exynos dts file. OK I think I get it now, so DT bindings shall really NOT be read by any of the pinctrl core, it is *supposed* to be all driver-specific. Then it makes perfect sense to have it as it is. Yes the driver nodes should describe in DT which pins to use: serial@1234 { compatible = 8250; reg = 0x1234 0x40; reg-shift = 2; interrupts = 10 ; pins = uart1_rx, uart1_tx; }; Note that we should use the actual signal names, not package specific pad names. This way they have a high likelyhood to work for new packages too by just mapping the signals to the new package. How would this handle the situation where you can mux a signal to multiple pins? IIRC omap3 and am335x can do funny stuff with the display pins like being able to map the blue bits to different pinblocks. regards, Koen signature.asc Description: Message signed with OpenPGP using GPGMail ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev