Re: [OE-core] Chaining compression support fixes for morty / pyro
RgfdfcD On 31-Jul-2017 7:27 PM, "Tom Rini" wrote: > Hi Armin, > > The following changes in master are relevant to both morty and pyro: > > commit 0a7ce0b971a208956cb895ba5a869ec8c5d94703 > Author: Tom Rini > Date: Fri Jul 21 18:06:33 2017 -0400 > > image.bbclass: Correct chaining compression support > > commit 98a2afeb3a53bec7a72a4a9846e1dba636cc6f3d > Author: Tom Rini > Date: Tue Jul 25 15:58:09 2017 -0400 > > image: Fix "metadata is not deterministic" when chaining 2+ > CONVERSION_CMDs > > And fix the problem where you cannot make arbitrary combinations of say > "ext4", "u-boot" and "xz" images. In the interest of full disclosure, > it is entirely possible that there are image types introduces in other > layers that have the same problem that the "u-boot" type had which lead > to 46bc438374de being done in the first place, which is to say a new > IMAGE_CMD that also cleaned up the intermediate files on its own. This > may make this too risky to pull into stable branches and that's fine. > Thanks for your consideration! > > -- > Tom > > -- > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core > > -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH V2] mesa, llvm: Use native version of llvm-config
On 1 August 2017 at 01:23, Khem Raj wrote: > We have a variable YOCTO_ALTERNATE_EXE_PATH to point to > target sysroot, utilize this in mesa to use native version > of llvm-config to report values from target sysroot. > > Its in a way similar to --sysroot option > > strip out rpath since its absolute path and incorrect thusly > I'd say that this needs to be three commits. One to llvm, one to mesa to use llvm-native, and one to mesa to chrpath. Ross -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [morty][PATCH 1/2] libpng: move SRC_URI back to SOURCEFORGE_MIRROR
Hi Armin,
On Mon, Jul 24, 2017 at 09:04:40PM -0700, akuster808 wrote:
>
>
> On 07/20/2017 04:51 AM, Maxin B. John wrote:
> >Since GENTOO_MIRROR removes older binaries, move back to
> >SOURCEFORGE_MIRROR
> your fix is cleaner than what I had stagged.
> thanks,
> Armin
> >[YOCTO #11554]
Please ignore this fix. I will send v2 which fixes the MIRRORS.
> >Signed-off-by: Maxin B. John
> >---
> > meta/recipes-multimedia/libpng/libpng_1.6.24.bb | 6 --
> > 1 file changed, 4 insertions(+), 2 deletions(-)
> >
> >diff --git a/meta/recipes-multimedia/libpng/libpng_1.6.24.bb
> >b/meta/recipes-multimedia/libpng/libpng_1.6.24.bb
> >index f91ab7f..4ee5983 100644
> >--- a/meta/recipes-multimedia/libpng/libpng_1.6.24.bb
> >+++ b/meta/recipes-multimedia/libpng/libpng_1.6.24.bb
> >@@ -6,8 +6,10 @@ LIC_FILES_CHKSUM =
> >"file://LICENSE;md5=5089214833586ba444048fd1dbbc76a4 \
> >
> > file://png.h;endline=149;md5=376d8ff7f69b7c4ad3a09f4672cec696"
> > DEPENDS = "zlib"
> >-SRC_URI = "${GENTOO_MIRROR}/libpng-${PV}.tar.xz \
> >- "
> >+LIBV = "16"
> >+
> >+SRC_URI =
> >"${SOURCEFORGE_MIRROR}/project/libpng/libpng${LIBV}/older-releases/${PV}/libpng-${PV}.tar.xz"
> >+
> > SRC_URI[md5sum] = "ffcdbd549814787fa8010c372e35ff25"
> > SRC_URI[sha256sum] =
> > "7932dc9e5e45d55ece9d204e90196bbb5f2c82741ccb0f7e10d07d364a6fd6dd"
Best Regards,
Maxin
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH][V2] re2c: fix build race
Signed-off-by: Ross Burton
---
meta/recipes-support/re2c/re2c/mkdir.patch | 36 ++
meta/recipes-support/re2c/re2c_0.16.bb | 2 +-
2 files changed, 37 insertions(+), 1 deletion(-)
create mode 100644 meta/recipes-support/re2c/re2c/mkdir.patch
diff --git a/meta/recipes-support/re2c/re2c/mkdir.patch
b/meta/recipes-support/re2c/re2c/mkdir.patch
new file mode 100644
index 000..d59f01b36c0
--- /dev/null
+++ b/meta/recipes-support/re2c/re2c/mkdir.patch
@@ -0,0 +1,36 @@
+Upstream-Status: Submitted (https://github.com/skvadrik/re2c/pull/191)
+Signed-off-by: Ross Burton
+
+From bccc10c60523f88c8f81413151cdcd612eb16198 Mon Sep 17 00:00:00 2001
+From: Ross Burton
+Date: Mon, 31 Jul 2017 15:43:41 +0100
+Subject: [PATCH] Makefile.am: create target directory before writing into it
+
+In some situations src/parse/ may not exist before a file is copied into the
+directory. Ensure that this doesn't happen by creating the directory first.
+---
+ re2c/Makefile.am | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/re2c/Makefile.am b/re2c/Makefile.am
+index 3b3b2c5e..0707fc5a 100644
+--- a/Makefile.am
b/Makefile.am
+@@ -187,6 +187,7 @@ CLEANFILES = \
+ $(DOC)
+
+ $(AUTOGEN_PARSER): $(CUSTOM_PARSER)
++ $(AM_V_at)$(MKDIR_P) $(dir $@)
+ $(AM_V_GEN) if test $(BISON) = "no"; \
+ then \
+ cp $(top_srcdir)/$(BOOTSTRAP_PARSER) $@ && \
+@@ -211,6 +212,7 @@ $(BOOTSTRAP_PARSER): $(CUSTOM_PARSER)
+ $(top_srcdir)/$(CUSTOM_PARSER);
+
+ .re.cc:
++ $(AM_V_at)$(MKDIR_P) $(dir $@)
+ $(AM_V_GEN) if test -x $(RE2C); \
+ then \
+ $(top_builddir)/$(RE2C) $(RE2CFLAGS) -o $@ $< && \
+--
+2.11.0
diff --git a/meta/recipes-support/re2c/re2c_0.16.bb
b/meta/recipes-support/re2c/re2c_0.16.bb
index e82502c5f2d..50dd7b7d261 100644
--- a/meta/recipes-support/re2c/re2c_0.16.bb
+++ b/meta/recipes-support/re2c/re2c_0.16.bb
@@ -6,7 +6,7 @@ LICENSE = "PD"
LIC_FILES_CHKSUM =
"file://README;beginline=146;md5=881056c9add17f8019ccd8c382ba963a"
SRC_URI = "${SOURCEFORGE_MIRROR}/${BPN}/${BPN}-${PV}.tar.gz \
-"
+ file://mkdir.patch"
SRC_URI[md5sum] = "3bf508fabd52ed7334647d0ccb956e8d"
SRC_URI[sha256sum] =
"48c12564297641cceb5ff05aead57f28118db6277f31e2262437feba89069e84"
--
2.11.0
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCHv2] (morty) Arch Linux build fixes
On 21/06/17 10:05, Anton Novikov wrote: [3 patch attachments] Any word on getting these patches applied to Morty? Is anything blocking them? Maybe they need resubmitted as individual patches? They do seem to apply cleanly on the current tip of morty (7d5822bf4c) and do fix various automake and gcc7 host build failures. Regards, Ian -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [morty][PATCH v2] libpng12: move SRC_URI back to SOURCEFORGE_MIRROR
Since GENTOO_MIRROR removes older binaries, move back to
SOURCEFORGE_MIRROR. Also provide a MIRROR to "older-releases"
directory.
[YOCTO #11556]
Signed-off-by: Maxin B. John
---
meta/recipes-lsb4/libpng/libpng12_1.2.56.bb | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-lsb4/libpng/libpng12_1.2.56.bb
b/meta/recipes-lsb4/libpng/libpng12_1.2.56.bb
index 10c350a..277d69f 100644
--- a/meta/recipes-lsb4/libpng/libpng12_1.2.56.bb
+++ b/meta/recipes-lsb4/libpng/libpng12_1.2.56.bb
@@ -9,7 +9,11 @@ DEPENDS = "zlib"
PN = "libpng12"
S = "${WORKDIR}/libpng-${PV}"
-SRC_URI = "${GENTOO_MIRROR}/libpng-${PV}.tar.xz"
+LIBV = "12"
+
+SRC_URI =
"${SOURCEFORGE_MIRROR}/project/libpng/libpng${LIBV}/${PV}/libpng-${PV}.tar.xz"
+
+MIRRORS += "${SOURCEFORGE_MIRROR}/project/libpng/libpng${LIBV}/${PV}/
${SOURCEFORGE_MIRROR}/project/libpng/libpng${LIBV}/older-releases/${PV}"
SRC_URI[md5sum] = "868562bd1c58b76ed8703f135a2e439a"
SRC_URI[sha256sum] =
"24ce54581468b937734a6ecc86f7e121bc46a90d76a0d948dca08f32ee000dbe"
--
2.4.0
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH v2] autoconf: fix mistakes in SUMMARY and DESCRIPTION
On Mon, 2017-07-31 at 13:48 -0400, Denys Dmytriyenko wrote: > On Fri, Jul 28, 2017 at 04:47:40PM -0700, Andre McCurdy wrote: > > On Fri, Jul 28, 2017 at 1:26 PM, Denys Dmytriyenko > > wrote: > > > @@ -1,5 +1,5 @@ > > > -SUMMARY = "A GNU tool that procude shell scripts to > > > automatically configure software" > > > -DESCRIPTION = "Autoconf is an extensible package of M4 macros > > > that produce shell scripts to automatically \ > > > +SUMMARY = "A GNU tool that produces shell scripts to > > > automatically configure software" > > > +DESCRIPTION = "Autoconf is an extensible package of M4 macros > > > that produces shell scripts to automatically \ > > The DESCRIPTION was correct originally (since it's the M4 macros > > which > > produce the shell scripts, not the extensible package). > > > > https://www.gnu.org/software/autoconf/autoconf.html > Good thing Richard picked up v1 of the patch then! :) That was in fact based on this mail thread! :) Cheers, Richard -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH V2] mesa, llvm: Use native version of llvm-config
ERROR: llvm-5.0-r0 do_compile: Function failed: do_compile (log file is located at /data/poky-tmp/master/build/work/corei7-64-poky-linux/llvm/5.0-r0/temp/log.do_compile.4542) ERROR: Logfile of failure stored in: /data/poky-tmp/master/build/work/corei7-64-poky-linux/llvm/5.0-r0/temp/log.do_compile.4542 Log data follows: | DEBUG: Executing shell function do_compile | ninja: error: '/data/poky-tmp/master/build/work/corei7-64-poky-linux/llvm/5.0-r0/recipe-sysroot-native/usr/bin/llvm-tblgen', needed by 'include/llvm/IR/Attributes.gen.tmp', missing and no known rule to make it | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_compile (log file is located at /data/poky-tmp/master/build/work/corei7-64-poky-linux/llvm/5.0-r0/temp/log.do_compile.4542) ERROR: Task (/home/ross/Yocto/poky/meta/recipes-devtools/llvm/llvm_git.bb:do_compile) failed with exit code '1' Ross -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH v2] openssh: Fix key generation with systemd
Sorry didn't notice the v2. In staging now.
Ross
On 25 July 2017 at 03:23, Joshua Watt wrote:
> On Mon, 2017-07-03 at 20:18 -0500, Joshua Watt wrote:
> > 106b59d9 broke SSH host key generation when systemd and a read-only
> > root file
> > system are in use because there isn't a way for systemd to get the
> > optional
> > weak assigment of SYSCONFDIR from /etc/default/sshd and still provide
> > a default
> > value if it is not specified. Instead, move the logic for determining
> > if keys
> > need to be created to a helper script that both the SysV init script
> > and the
> > systemd unit file can reference.
> >
> > This does mean that the systemd unit file can't check for file
> > existence to
> > know if it should start the service, but it wasn't able to do that
> > correctly
> > anyway anymore. This should be a problem since the serivce is only
> > run once per
> > power cycle by systemd, and should exit quickly if the keys already
> > exist
> >
> > Signed-off-by: Joshua Watt
> > ---
> > meta/recipes-connectivity/openssh/openssh/init | 69 +---
> > --
> > .../openssh/openssh/sshd_check_keys| 64
> >
> > .../openssh/openssh/sshdgenkeys.service| 16 +
> > meta/recipes-connectivity/openssh/openssh_7.5p1.bb | 8 +++
> > 4 files changed, 76 insertions(+), 81 deletions(-)
> > create mode 100644 meta/recipes-
> > connectivity/openssh/openssh/sshd_check_keys
> >
> > diff --git a/meta/recipes-connectivity/openssh/openssh/init
> > b/meta/recipes-connectivity/openssh/openssh/init
> > index 386628a..34ba0f8 100644
> > --- a/meta/recipes-connectivity/openssh/openssh/init
> > +++ b/meta/recipes-connectivity/openssh/openssh/init
> > @@ -19,25 +19,6 @@ fi
> > [ -z "$SYSCONFDIR" ] && SYSCONFDIR=/etc/ssh
> > mkdir -p $SYSCONFDIR
> >
> > -parse_sshd_opts() {
> > -set -- ${SSHD_OPTS} --
> > -sshd_config=/etc/ssh/sshd_config
> > -while true ; do
> > -case "$1" in
> > --f*) if [ "$1" = "-f" ] ; then
> > - sshd_config="$2"
> > - shift
> > - else
> > - sshd_config="${1#-f}"
> > - fi
> > - shift
> > - ;;
> > ---) shift; break;;
> > -*) shift;;
> > -esac
> > -done
> > -}
> > -
> > check_for_no_start() {
> > # forget it if we're trying to start, and
> > /etc/ssh/sshd_not_to_be_run exists
> > if [ -e $SYSCONFDIR/sshd_not_to_be_run ]; then
> > @@ -58,57 +39,13 @@ check_config() {
> > /usr/sbin/sshd -t $SSHD_OPTS || exit 1
> > }
> >
> > -check_keys() {
> > - # parse location of keys
> > - local HOST_KEY_RSA
> > - local HOST_KEY_DSA
> > - local HOST_KEY_ECDSA
> > - local HOST_KEY_ED25519
> > -
> > - parse_sshd_opts
> > - HOST_KEY_RSA=$(grep ^HostKey "${sshd_config}" | grep _rsa_ |
> > tail -1 | awk ' { print $2 } ')
> > - [ -z "${HOST_KEY_RSA}" ] && HOST_KEY_RSA=$(grep HostKey
> > "${sshd_config}" | grep _rsa_ | tail -1 | awk ' { print $2 } ')
> > - [ -z "${HOST_KEY_RSA}" ] &&
> > HOST_KEY_RSA=$SYSCONFDIR/ssh_host_rsa_key
> > - HOST_KEY_DSA=$(grep ^HostKey "${sshd_config}" | grep _dsa_ |
> > tail -1 | awk ' { print $2 } ')
> > - [ -z "${HOST_KEY_DSA}" ] && HOST_KEY_DSA=$(grep HostKey
> > "${sshd_config}" | grep _dsa_ | tail -1 | awk ' { print $2 } ')
> > - [ -z "${HOST_KEY_DSA}" ] &&
> > HOST_KEY_DSA=$SYSCONFDIR/ssh_host_dsa_key
> > - HOST_KEY_ECDSA=$(grep ^HostKey "${sshd_config}" | grep
> > _ecdsa_ | tail -1 | awk ' { print $2 } ')
> > - [ -z "${HOST_KEY_ECDSA}" ] && HOST_KEY_ECDSA=$(grep HostKey
> > "${sshd_config}" | grep _ecdsa_ | tail -1 | awk ' { print $2 } ')
> > - [ -z "${HOST_KEY_ECDSA}" ] &&
> > HOST_KEY_ECDSA=$SYSCONFDIR/ssh_host_ecdsa_key
> > - HOST_KEY_ED25519=$(grep ^HostKey "${sshd_config}" | grep
> > _ed25519_ | tail -1 | awk ' { print $2 } ')
> > - [ -z "${HOST_KEY_ED25519}" ] && HOST_KEY_ED25519=$(grep
> > HostKey "${sshd_config}" | grep _ed25519_ | tail -1 | awk ' { print
> > $2 } ')
> > - [ -z "${HOST_KEY_ED25519}" ] &&
> > HOST_KEY_ED25519=$SYSCONFDIR/ssh_host_ed25519_key
> > -
> > - # create keys if necessary
> > - if [ ! -f $HOST_KEY_RSA ]; then
> > - echo " generating ssh RSA key..."
> > - mkdir -p $(dirname $HOST_KEY_RSA)
> > - ssh-keygen -q -f $HOST_KEY_RSA -N '' -t rsa
> > - fi
> > - if [ ! -f $HOST_KEY_ECDSA ]; then
> > - echo " generating ssh ECDSA key..."
> > - mkdir -p $(dirname $HOST_KEY_ECDSA)
> > - ssh-keygen -q -f $HOST_KEY_ECDSA -N '' -t ecdsa
> > - fi
> > - if [ ! -f $HOST_KEY_DSA ]; then
> > - echo " generating ssh DSA key..."
> > - mkdir -p $(dirname $HOST_KEY_DSA)
> > - ssh-keygen -q -f $HOST_KEY_DSA -N '' -t dsa
> > - fi
> > - if [ ! -f $HOST_KEY_ED25519 ]; then
> > - echo " generating ssh ED25519 key..."
> > -
Re: [OE-core] [PATCHv4 3/4] recipetool: create: handle git URLs specifying only a tag
The eSDK tests are failing with this applied: oeqa.utils.subprocesstweak.OETestCalledProcessError: Command '. /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86-64/build/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/testsdkext/environment-setup-core2-64-poky-linux > /dev/null; devtool add myapp /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86-64/build/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/testsdkext/myapp; returned non-zero exit status 1 Standard Output: NOTE: Starting bitbake server... NOTE: Starting bitbake server... Traceback (most recent call last): File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86-64/build/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/testsdkext/layers/build/scripts/recipetool", line 121, in ret = main() File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86-64/build/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/testsdkext/layers/build/scripts/recipetool", line 110, in main ret = args.func(args) File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86-64/build/build/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/testsdkext/layers/build/scripts/lib/recipetool/create.py", line 662, in create_recipe if (branch and not append_branch) or storeTagName: UnboundLocalError: local variable 'storeTagName' referenced before assignment Ross -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] local.conf.sample.extended: remove references to image_types_uboot
> On Jul 31, 2017, at 5:23 PM, Tom Rini wrote: > > On Mon, Jul 31, 2017 at 04:16:24PM -0400, drew.mose...@northern.tech wrote: > >> From: Drew Moseley >> >> This class was removed with commit: >>OE-Core rev: 65f27122950a35a67ce39ae4cfe93d0dca6b0dab >> >> Signed-off-by: Drew Moseley > > Reviewed-by: Tom Rini > > -- > Tom Evidently my northern.tech subscription had not yet taken effect when I submitted the original patch so that email never made it to the list. I’ll resend a V2. Drew -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH V2] local.conf.sample.extended: remove references to image_types_uboot
From: Drew Moseley This class was removed with commit: OE-Core rev: 65f27122950a35a67ce39ae4cfe93d0dca6b0dab Signed-off-by: Drew Moseley --- meta-poky/conf/local.conf.sample.extended | 3 --- 1 file changed, 3 deletions(-) diff --git a/meta-poky/conf/local.conf.sample.extended b/meta-poky/conf/local.conf.sample.extended index 0560de8..331fdd1 100644 --- a/meta-poky/conf/local.conf.sample.extended +++ b/meta-poky/conf/local.conf.sample.extended @@ -168,9 +168,6 @@ # Additional image generation features # -# The following is a list of classes to import to use in the generation of images -# currently an example class is image_types_uboot -# IMAGE_CLASSES = " image_types_uboot" # The following options will build a companion 'debug filesystem' in addition # to the normal deployable filesystem. This companion system allows a -- 2.7.4 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] ✗ patchtest: failure for local.conf.sample.extended: remove references to image_types_uboot
== Series Details == Series: local.conf.sample.extended: remove references to image_types_uboot Revision: 1 URL : https://patchwork.openembedded.org/series/8052/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures: * Issue Series does not apply on top of target branch [test_series_merge_on_head] Suggested fixRebase your series on top of targeted branch Targeted branch master (currently at da29bc17e4) * Issue Series sent to the wrong mailing list or some patches from the series correspond to different mailing lists [test_target_mailing_list] Suggested fixSend the series again to the correct mailing list (ML) Suggested ML p...@yoctoproject.org [http://git.yoctoproject.org/cgit/cgit.cgi/poky/] Patch's path:meta-poky/conf/local.conf.sample.extended If you believe any of these test results are incorrect, please reply to the mailing list (openembedded-core@lists.openembedded.org) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...). --- Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] worth adding a "git"-versioned of i2c-tools to oe-core?
On 07/31/2017 09:57 PM, Khem Raj wrote: usually, sending it upstream at same time when its proposed here for OE is best. Then you can discuss it with upstream on sides, if upstream does not want a patch, that creates some maintenance debt for future upgrades but such is life. Also, if the patch is non-trivial, there is a risk it will be dropped from Yocto in the future, if rebasing it to a newer upstream release is difficult and requires specialist knowledge. It's best if upstream maintainers take it. Alex -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] go-dep: Add 0.2.0 release
Verifying this here.
Building for qemuarm puts the binary in /usr/bin/dep. Building for
intel-corei7-64 puts the binary in /usr/lib/x86_64-poky-linux/go/bin/dep.
Ross
On 31 July 2017 at 20:52, Otavio Salvador
wrote:
> On Mon, Jul 31, 2017 at 4:20 PM, Khem Raj wrote:
> >
> >
> > On 7/31/17 12:12 PM, Otavio Salvador wrote:
> >> Hello Ross,
> >> Hello Khem,
> >>
> >> On Sat, Jul 29, 2017 at 3:28 PM, Burton, Ross
> wrote:
> >>> Failed in the no-x11 builder at least so far:
> >>>
> >>> ERROR: go-dep-0.2.0-r0 do_package: QA Issue: go-dep: Files/directories
> were
> >>> installed but not shipped in any package:
> >>> /usr/lib/x86_64-poky-linux/go/bin/dep
> >>> Please set FILES such that these items are packaged. Alternatively if
> they
> >>> are unneeded, avoid installing them or delete them within do_install.
> >>>
> >>> https://autobuilder.yoctoproject.org/main/builders/nightly-no-x11/
> builds/537
> >>
> >> I did reproduce this; I could only reproduce it if I built it with a
> >> machine which matches the architecture of host, in my case x86-64.
> >> When building for other arch (e.g: ARM) it works as expected.
> >>
> >> The problem seems to be a generic problem and I am not experienced
> >> enough on the Golang toolchain to look at this. Khem could you take a
> >> look and see if you find the root cause?
> >
> > Delete this file, its building it on x86_64 because it can. We only need
> > cross version.
>
> I am not sure I follow you here.
>
> Using qemux86-64 as target it does NOT install on ${bindir} and
> surprisingly the installation path does also not match GOBIN_FINAL
> value.
>
> --
> Otavio Salvador O.S. Systems
> http://www.ossystems.com.brhttp://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
>
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH v2] python: don't include -tests with modules
Although 'test' is listed in the python module list
(https://docs.python.org/3/py-modindex.html) it is meant only to be
used 'internally' by folks developing python itself. Per the
documentation:
Note The test package is meant for internal use by Python only. It
is documented for the benefit of the core developers of Python. Any
use of this package outside of Python’s standard library is
discouraged as code mentioned here can change or be removed without
notice between releases of Python.
Per the above it is best not to include this module to discourage
folks who might not head the above warnings. Additionally this module
is one of the largest py modules going, by dropping this unneeded
module from the 'modules' package we can reduce overall image size,
something which is important for many embedded deployments.
The generator scripts as well as the manifests have thus been modified
accordingly, providing a generic mechanism to exclude modules from the
'all modules' package.
Signed-off-by: Mark Asselstine
---
*** v2
Updated the generator script missed in the v1 and pointed out
by RP.
meta/recipes-devtools/python/python-2.7-manifest.inc | 2 +-
meta/recipes-devtools/python/python-3.5-manifest.inc | 2 +-
scripts/contrib/python/generate-manifest-2.7.py | 9 ++---
scripts/contrib/python/generate-manifest-3.5.py | 9 ++---
4 files changed, 14 insertions(+), 8 deletions(-)
diff --git a/meta/recipes-devtools/python/python-2.7-manifest.inc
b/meta/recipes-devtools/python/python-2.7-manifest.inc
index 7ed254b..57d4834 100644
--- a/meta/recipes-devtools/python/python-2.7-manifest.inc
+++ b/meta/recipes-devtools/python/python-2.7-manifest.inc
@@ -281,7 +281,7 @@ RDEPENDS_${PN}-zlib="${PN}-core"
FILES_${PN}-zlib="${libdir}/python2.7/lib-dynload/zlib.so "
SUMMARY_${PN}-modules="All Python modules"
-RDEPENDS_${PN}-modules="${PN}-2to3 ${PN}-argparse ${PN}-audio ${PN}-bsddb
${PN}-codecs ${PN}-compile ${PN}-compiler ${PN}-compression ${PN}-contextlib
${PN}-core ${PN}-crypt ${PN}-ctypes ${PN}-curses ${PN}-datetime ${PN}-db
${PN}-debugger ${PN}-difflib ${PN}-distutils ${PN}-doctest ${PN}-email
${PN}-fcntl ${PN}-gdbm ${PN}-hotshot ${PN}-html ${PN}-idle ${PN}-image
${PN}-importlib ${PN}-io ${PN}-json ${PN}-lang ${PN}-logging ${PN}-mailbox
${PN}-math ${PN}-mime ${PN}-mmap ${PN}-multiprocessing ${PN}-netclient
${PN}-netserver ${PN}-numbers ${PN}-pickle ${PN}-pkgutil ${PN}-plistlib
${PN}-pprint ${PN}-profile ${PN}-pydoc ${PN}-re ${PN}-readline ${PN}-resource
${PN}-robotparser ${PN}-shell ${PN}-smtpd ${PN}-sqlite3 ${PN}-sqlite3-tests
${PN}-stringold ${PN}-subprocess ${PN}-syslog ${PN}-terminal ${PN}-tests
${PN}-textutils ${PN}-threading ${PN}-tkinter ${PN}-unittest ${PN}-unixadmin
${PN}-xml ${PN}-xmlrpc ${PN}-zlib "
+RDEPENDS_${PN}-modules="${PN}-2to3 ${PN}-argparse ${PN}-audio ${PN}-bsddb
${PN}-codecs ${PN}-compile ${PN}-compiler ${PN}-compression ${PN}-contextlib
${PN}-core ${PN}-crypt ${PN}-ctypes ${PN}-curses ${PN}-datetime ${PN}-db
${PN}-debugger ${PN}-difflib ${PN}-distutils ${PN}-doctest ${PN}-email
${PN}-fcntl ${PN}-gdbm ${PN}-hotshot ${PN}-html ${PN}-idle ${PN}-image
${PN}-importlib ${PN}-io ${PN}-json ${PN}-lang ${PN}-logging ${PN}-mailbox
${PN}-math ${PN}-mime ${PN}-mmap ${PN}-multiprocessing ${PN}-netclient
${PN}-netserver ${PN}-numbers ${PN}-pickle ${PN}-pkgutil ${PN}-plistlib
${PN}-pprint ${PN}-profile ${PN}-pydoc ${PN}-re ${PN}-readline ${PN}-resource
${PN}-robotparser ${PN}-shell ${PN}-smtpd ${PN}-sqlite3 ${PN}-sqlite3-tests
${PN}-stringold ${PN}-subprocess ${PN}-syslog ${PN}-terminal ${PN}-textutils
${PN}-threading ${PN}-tkinter ${PN}-unittest ${PN}-unixadmin ${PN}-xml
${PN}-xmlrpc ${PN}-zlib "
ALLOW_EMPTY_${PN}-modules = "1"
diff --git a/meta/recipes-devtools/python/python-3.5-manifest.inc
b/meta/recipes-devtools/python/python-3.5-manifest.inc
index 65db7e8..0260e87 100644
--- a/meta/recipes-devtools/python/python-3.5-manifest.inc
+++ b/meta/recipes-devtools/python/python-3.5-manifest.inc
@@ -277,7 +277,7 @@ RDEPENDS_${PN}-xmlrpc="${PN}-core ${PN}-xml ${PN}-netserver
${PN}-lang ${PN}-pyd
FILES_${PN}-xmlrpc="${libdir}/python3.5/xmlrpclib.*
${libdir}/python3.5/__pycache__/xmlrpclib.*
${libdir}/python3.5/SimpleXMLRPCServer.*
${libdir}/python3.5/__pycache__/SimpleXMLRPCServer.*
${libdir}/python3.5/DocXMLRPCServer.*
${libdir}/python3.5/__pycache__/DocXMLRPCServer.* ${libdir}/python3.5/xmlrpc
${libdir}/python3.5/xmlrpc/__pycache__ "
SUMMARY_${PN}-modules="All Python modules"
-RDEPENDS_${PN}-modules="${PN}-2to3 ${PN}-argparse ${PN}-asyncio ${PN}-audio
${PN}-codecs ${PN}-compile ${PN}-compression ${PN}-core ${PN}-crypt
${PN}-ctypes ${PN}-curses ${PN}-datetime ${PN}-db ${PN}-debugger ${PN}-difflib
${PN}-distutils ${PN}-doctest ${PN}-email ${PN}-enum ${PN}-fcntl ${PN}-gdbm
${PN}-html ${PN}-idle ${PN}-image ${PN}-importlib ${PN}-io ${PN}-json
${PN}-lang ${PN}-logging ${PN}-mailbox ${PN}-math ${PN}-mime ${PN}-mmap
${PN}-multiproces
[OE-core] [PATCH 1/4] musl: Drop the protected symbol optimization at configure time
lld and gold can not handle it and treat it wrong
Fixes
[YOCTO #11689]
Signed-off-by: Khem Raj
---
meta/recipes-core/musl/musl_git.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-core/musl/musl_git.bb
b/meta/recipes-core/musl/musl_git.bb
index 53a8ba196a..93e3535c8d 100644
--- a/meta/recipes-core/musl/musl_git.bb
+++ b/meta/recipes-core/musl/musl_git.bb
@@ -36,6 +36,7 @@ CONFIGUREOPTS = " \
--libdir=${libdir} \
--includedir=${includedir} \
--syslibdir=${base_libdir} \
+--disable-visibility \
"
do_configure() {
--
2.13.3
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 2/4] mesa: Use chrpath to delete rpaths
It adds native sysroot chrpath due to llvm-config in cross compiling
we can delete them via chrpath, since libs are in standard paths rpath
is really not needed
Signed-off-by: Khem Raj
---
meta/recipes-graphics/mesa/mesa.inc | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-graphics/mesa/mesa.inc
b/meta/recipes-graphics/mesa/mesa.inc
index c9b67d4966..da449fa70b 100644
--- a/meta/recipes-graphics/mesa/mesa.inc
+++ b/meta/recipes-graphics/mesa/mesa.inc
@@ -14,8 +14,8 @@ LIC_FILES_CHKSUM =
"file://docs/license.html;md5=725f991a1cc322aa7a0cd3a2016621c
PE = "2"
-DEPENDS = "expat makedepend-native flex-native bison-native libxml2-native
zlib"
-
+DEPENDS = "expat makedepend-native flex-native bison-native libxml2-native
zlib chrpath-replacement-native"
+EXTRANATIVEPATH += "chrpath-native"
PROVIDES = "virtual/libgl virtual/libgles1 virtual/libgles2 virtual/egl
virtual/mesa"
inherit autotools pkgconfig gettext distro_features_check
@@ -118,9 +118,10 @@ do_install_append () {
rm -f ${D}${libdir}/egl/*.la
rm -f ${D}${libdir}/gallium-pipe/*.la
rm -f ${D}${libdir}/gbm/*.la
-
+
# it was packaged in libdricore9.1.3-1 and preventing upgrades when
debian.bbclass was used
rm -f ${D}${sysconfdir}/drirc
+chrpath --delete ${D}${libdir}/dri/*_dri.so
}
# For the packages that make up the OpenGL interfaces, inject variables so that
--
2.13.3
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 3/4] mesa: Depend on llvm-native
We need to get llvm-config tool staged which is provided by llvm-native
Signed-off-by: Khem Raj
---
meta/recipes-graphics/mesa/mesa.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-graphics/mesa/mesa.inc
b/meta/recipes-graphics/mesa/mesa.inc
index da449fa70b..e14372775b 100644
--- a/meta/recipes-graphics/mesa/mesa.inc
+++ b/meta/recipes-graphics/mesa/mesa.inc
@@ -75,7 +75,7 @@ GALLIUMDRIVERS_append_x86-64 =
"${@bb.utils.contains('PACKAGECONFIG', 'gallium-l
# keep --with-gallium-drivers separate, because when only one of gallium
versions is enabled, other 2 were adding --without-gallium-drivers
PACKAGECONFIG[gallium] = "--enable-texture-float
--with-gallium-drivers=${GALLIUMDRIVERS}, --without-gallium-drivers"
MESA_LLVM_RELEASE ?= "5.0"
-PACKAGECONFIG[gallium-llvm] = "--enable-llvm --enable-llvm-shared-libs,
--disable-llvm, llvm${MESA_LLVM_RELEASE} \
+PACKAGECONFIG[gallium-llvm] = "--enable-llvm --enable-llvm-shared-libs,
--disable-llvm, llvm${MESA_LLVM_RELEASE} llvm-native \
${@'elfutils' if
${GALLIUMDRIVERS_LLVM33_ENABLED} else ''}"
export WANT_LLVM_RELEASE = "${MESA_LLVM_RELEASE}"
PACKAGECONFIG[xa] = "--enable-xa, --disable-xa"
--
2.13.3
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH V2 4/4] mesa, llvm: Use native version of llvm-config
We have a variable YOCTO_ALTERNATE_EXE_PATH to point to
target sysroot, utilize this in mesa to use native version
of llvm-config to report values from target sysroot.
Signed-off-by: Khem Raj
---
meta/recipes-devtools/llvm/llvm_git.bb | 16 +---
meta/recipes-graphics/mesa/mesa.inc| 4 ++--
2 files changed, 11 insertions(+), 9 deletions(-)
diff --git a/meta/recipes-devtools/llvm/llvm_git.bb
b/meta/recipes-devtools/llvm/llvm_git.bb
index 5dcb508c23..722bc53aa1 100644
--- a/meta/recipes-devtools/llvm/llvm_git.bb
+++ b/meta/recipes-devtools/llvm/llvm_git.bb
@@ -67,12 +67,12 @@ EXTRA_OECMAKE += "-DLLVM_ENABLE_ASSERTIONS=OFF \
EXTRA_OECMAKE_append_class-target = "\
-DCMAKE_CROSSCOMPILING:BOOL=ON \
- -DLLVM_TABLEGEN=${STAGING_BINDIR_NATIVE}/llvm-tblgen \
+ -DLLVM_TABLEGEN=${STAGING_BINDIR_NATIVE}/llvm-tblgen${PV} \
"
EXTRA_OECMAKE_append_class-nativesdk = "\
-DCMAKE_CROSSCOMPILING:BOOL=ON \
- -DLLVM_TABLEGEN=${STAGING_BINDIR_NATIVE}/llvm-tblgen \
+ -DLLVM_TABLEGEN=${STAGING_BINDIR_NATIVE}/llvm-tblgen${PV} \
"
do_configure_prepend() {
@@ -87,12 +87,12 @@ do_compile() {
}
do_compile_class-native() {
- NINJA_STATUS="[%p] " ninja -v ${PARALLEL_MAKE} llvm-tblgen
+ NINJA_STATUS="[%p] " ninja -v ${PARALLEL_MAKE} llvm-config llvm-tblgen
}
do_install() {
NINJA_STATUS="[%p] " DESTDIR=${LLVM_INSTALL_DIR} ninja -v install
- install -D -m 0755 ${B}/NATIVE/bin/llvm-config
${D}${libdir}/${LLVM_DIR}/llvm-config-host
+ install -D -m 0755 ${B}/bin/llvm-config
${D}${libdir}/${LLVM_DIR}/llvm-config
install -d ${D}${bindir}/${LLVM_DIR}
cp -r ${LLVM_INSTALL_DIR}${bindir}/* ${D}${bindir}/${LLVM_DIR}/
@@ -121,7 +121,9 @@ do_install() {
rm -rf ${D}${libdir}/${LLVM_DIR}/libLTO.so
}
do_install_class-native() {
- install -D -m 0755 ${B}/bin/llvm-tblgen ${D}${bindir}/llvm-tblgen
+ install -D -m 0755 ${B}/bin/llvm-tblgen ${D}${bindir}/llvm-tblgen${PV}
+ install -D -m 0755 ${B}/bin/llvm-config ${D}${bindir}/llvm-config${PV}
+ install -D -m 0755 ${B}/lib/libLLVM-${PV}.so
${D}${libdir}/libLLVM-${PV}.so
}
PACKAGES += "${PN}-bugpointpasses ${PN}-llvmhello"
@@ -134,14 +136,14 @@ FILES_${PN}-dbg = " \
${libdir}/${LLVM_DIR}/.debug/BugpointPasses.so \
${libdir}/${LLVM_DIR}/.debug/LLVMHello.so \
${libdir}/${LLVM_DIR}/.debug/libLTO.so* \
-${libdir}/${LLVM_DIR}/.debug/llvm-config-host \
+${libdir}/${LLVM_DIR}/.debug/llvm-config \
/usr/src/debug \
"
FILES_${PN}-dev = " \
${bindir}/${LLVM_DIR} \
${includedir}/${LLVM_DIR} \
-${libdir}/${LLVM_DIR}/llvm-config-host \
+${libdir}/${LLVM_DIR}/llvm-config \
"
RRECOMMENDS_${PN}-dev += "${PN}-bugpointpasses ${PN}-llvmhello"
diff --git a/meta/recipes-graphics/mesa/mesa.inc
b/meta/recipes-graphics/mesa/mesa.inc
index e14372775b..a26858df85 100644
--- a/meta/recipes-graphics/mesa/mesa.inc
+++ b/meta/recipes-graphics/mesa/mesa.inc
@@ -25,8 +25,8 @@ REQUIRED_DISTRO_FEATURES = "opengl"
PLATFORMS ??= "${@bb.utils.filter('PACKAGECONFIG', 'x11 wayland', d)} \
${@bb.utils.contains('PACKAGECONFIG', 'gbm', 'drm', '', d)}"
-export LLVM_CONFIG =
"${STAGING_LIBDIR}/llvm${MESA_LLVM_RELEASE}/llvm-config-host"
-
+export LLVM_CONFIG = "${STAGING_BINDIR_NATIVE}/llvm-config${MESA_LLVM_RELEASE}"
+export YOCTO_ALTERNATE_EXE_PATH =
"${STAGING_LIBDIR}/llvm${MESA_LLVM_RELEASE}/llvm-config"
EXTRA_OECONF = "--enable-shared-glapi \
--disable-opencl \
--with-llvm-prefix=${STAGING_LIBDIR}/llvm${MESA_LLVM_RELEASE} \
--
2.13.3
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH V2] mesa, llvm: Use native version of llvm-config
On Tue, Aug 1, 2017 at 3:44 AM, Burton, Ross wrote: > ERROR: llvm-5.0-r0 do_compile: Function failed: do_compile (log file is > located at > /data/poky-tmp/master/build/work/corei7-64-poky-linux/llvm/5.0-r0/temp/log.do_compile.4542) > ERROR: Logfile of failure stored in: > /data/poky-tmp/master/build/work/corei7-64-poky-linux/llvm/5.0-r0/temp/log.do_compile.4542 > Log data follows: > | DEBUG: Executing shell function do_compile > | ninja: error: > '/data/poky-tmp/master/build/work/corei7-64-poky-linux/llvm/5.0-r0/recipe-sysroot-native/usr/bin/llvm-tblgen', > needed by 'include/llvm/IR/Attributes.gen.tmp', missing and no known rule to > make it > | WARNING: exit code 1 from a shell command. > | ERROR: Function failed: do_compile (log file is located at > /data/poky-tmp/master/build/work/corei7-64-poky-linux/llvm/5.0-r0/temp/log.do_compile.4542) > ERROR: Task > (/home/ross/Yocto/poky/meta/recipes-devtools/llvm/llvm_git.bb:do_compile) > failed with exit code '1' yes, just realized that I was building it with a build where meta-clang is included and TOOLCHAIN = "clang" so it was getting llvm-tblgen from clang when llvm-native version got renamed so it kept on building for me. I have sent a next rev of the patches which addresses this issue as well as your comment. -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] go-dep: Add 0.2.0 release
On Tue, Aug 1, 2017 at 6:50 AM, Burton, Ross wrote:
> Verifying this here.
>
> Building for qemuarm puts the binary in /usr/bin/dep. Building for
> intel-corei7-64 puts the binary in /usr/lib/x86_64-poky-linux/go/bin/dep.
>
may be configure logs can tell why is it making this distinction.
Since we are not building
for multiarch, using /usr/bin/dep might be ok
> Ross
>
> On 31 July 2017 at 20:52, Otavio Salvador
> wrote:
>>
>> On Mon, Jul 31, 2017 at 4:20 PM, Khem Raj wrote:
>> >
>> >
>> > On 7/31/17 12:12 PM, Otavio Salvador wrote:
>> >> Hello Ross,
>> >> Hello Khem,
>> >>
>> >> On Sat, Jul 29, 2017 at 3:28 PM, Burton, Ross
>> >> wrote:
>> >>> Failed in the no-x11 builder at least so far:
>> >>>
>> >>> ERROR: go-dep-0.2.0-r0 do_package: QA Issue: go-dep: Files/directories
>> >>> were
>> >>> installed but not shipped in any package:
>> >>> /usr/lib/x86_64-poky-linux/go/bin/dep
>> >>> Please set FILES such that these items are packaged. Alternatively if
>> >>> they
>> >>> are unneeded, avoid installing them or delete them within do_install.
>> >>>
>> >>>
>> >>> https://autobuilder.yoctoproject.org/main/builders/nightly-no-x11/builds/537
>> >>
>> >> I did reproduce this; I could only reproduce it if I built it with a
>> >> machine which matches the architecture of host, in my case x86-64.
>> >> When building for other arch (e.g: ARM) it works as expected.
>> >>
>> >> The problem seems to be a generic problem and I am not experienced
>> >> enough on the Golang toolchain to look at this. Khem could you take a
>> >> look and see if you find the root cause?
>> >
>> > Delete this file, its building it on x86_64 because it can. We only need
>> > cross version.
>>
>> I am not sure I follow you here.
>>
>> Using qemux86-64 as target it does NOT install on ${bindir} and
>> surprisingly the installation path does also not match GOBIN_FINAL
>> value.
>>
>> --
>> Otavio Salvador O.S. Systems
>> http://www.ossystems.com.brhttp://code.ossystems.com.br
>> Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
>
>
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [morty][PATCH 1/2] libpng: move SRC_URI back to SOURCEFORGE_MIRROR
On 08/01/2017 01:43 AM, Maxin B. John wrote:
Hi Armin,
On Mon, Jul 24, 2017 at 09:04:40PM -0700, akuster808 wrote:
On 07/20/2017 04:51 AM, Maxin B. John wrote:
Since GENTOO_MIRROR removes older binaries, move back to
SOURCEFORGE_MIRROR
your fix is cleaner than what I had stagged.
thanks,
Armin
[YOCTO #11554]
Please ignore this fix. I will send v2 which fixes the MIRRORS.
this series already in morty-next. I pull them for your v2
- armin
Signed-off-by: Maxin B. John
---
meta/recipes-multimedia/libpng/libpng_1.6.24.bb | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-multimedia/libpng/libpng_1.6.24.bb
b/meta/recipes-multimedia/libpng/libpng_1.6.24.bb
index f91ab7f..4ee5983 100644
--- a/meta/recipes-multimedia/libpng/libpng_1.6.24.bb
+++ b/meta/recipes-multimedia/libpng/libpng_1.6.24.bb
@@ -6,8 +6,10 @@ LIC_FILES_CHKSUM =
"file://LICENSE;md5=5089214833586ba444048fd1dbbc76a4 \
file://png.h;endline=149;md5=376d8ff7f69b7c4ad3a09f4672cec696"
DEPENDS = "zlib"
-SRC_URI = "${GENTOO_MIRROR}/libpng-${PV}.tar.xz \
- "
+LIBV = "16"
+
+SRC_URI =
"${SOURCEFORGE_MIRROR}/project/libpng/libpng${LIBV}/older-releases/${PV}/libpng-${PV}.tar.xz"
+
SRC_URI[md5sum] = "ffcdbd549814787fa8010c372e35ff25"
SRC_URI[sha256sum] =
"7932dc9e5e45d55ece9d204e90196bbb5f2c82741ccb0f7e10d07d364a6fd6dd"
Best Regards,
Maxin
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/2] armv8: update to use armv8-a tune
On 07/31/2017 12:04 PM, Khem Raj wrote:
On 7/31/17 10:51 AM, Mark Hatle wrote:
On 7/31/17 12:40 PM, akuster808 wrote:
On 07/31/2017 10:31 AM, Mark Hatle wrote:
On 7/31/17 12:16 PM, Armin Kuster wrote:
Signed-off-by: Armin Kuster
---
meta/conf/machine/include/arm/arch-armv8.inc | 25 +
1 file changed, 25 insertions(+)
diff --git a/meta/conf/machine/include/arm/arch-armv8.inc
b/meta/conf/machine/include/arm/arch-armv8.inc
index 5e832fa..dc1ba5e 100644
--- a/meta/conf/machine/include/arm/arch-armv8.inc
+++ b/meta/conf/machine/include/arm/arch-armv8.inc
@@ -1 +1,26 @@
+DEFAULTTUNE ?= "armv8-a"
do we want the '-a'? The other arm (7) are of the format armv7a (no '-').
works for me either way.
While we are at it. How would we want ‘armv8.1-a’, ‘armv8.2-a’, ‘armv8.3-a'
formated as?
My preference is to drop the '-'. As for the '.', I'm not sure.. not something
we've run across before.
We could just drop it (the '.'), but it really depends on if armv81a would
confuse someone (familiar with arm) or not.
I would suggest to also sync with other distros and ensure that we dont
do something different. Its very costly later. Since applications get
ported to most common combination
Sync what part? naming of file? ( sorry lost regarding your comment)
- armin
--Mark
- armin
--Mark
+
+TUNEVALID[armv8-a] = "Enable instructions for ARMv8-a"
+TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'armv8-a', ' -march=armv8-a',
'', d)}"
+
+TUNEVALID[crypto] = "Enable crypto instructions for ARMv8-a"
+TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'crypto', '+crypto', '',
d)}"
+
+MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'armv8-a', 'armv8a:', ''
,d)}"
+
require conf/machine/include/arm/arch-arm64.inc
+
+AVAILTUNES += "armv8-a armv8-a-crypto"
+ARMPKGARCH_tune-armv8-a ?= "armv8-a"
+
+# Enable Crypto extension. This also enables Advanced SIMD and floating-point
instructions
+ARMPKGARCH_tune-armv8-a-crypto ?= "armv8-a"
+
+TUNE_FEATURES_tune-armv8-a = "aarch64 armv8-a"
+TUNE_FEATURES_tune-armv8-a-crypto = "${TUNE_FEATURES_tune-armv8-a} crypto"
+
+PACKAGE_EXTRA_ARCHS_tune-armv8-a = "aarch64 armv8-a"
+PACKAGE_EXTRA_ARCHS_tune-armv8-a-crypto = "${PACKAGE_EXTRA_ARCHS_tune-armv8-a}
armv8-a-crypto"
+
+BASE_LIB_tune-armv8-a = "${BASE_LIB_tune-aarch64}"
+BASE_LIB_tune-armv8-a-crypto = "${BASE_LIB_tune-aarch64}"
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/2] armv8: update to use armv8-a tune
On Tue, Aug 1, 2017 at 8:17 AM, akuster808 wrote: > > > On 07/31/2017 12:04 PM, Khem Raj wrote: >> >> >> On 7/31/17 10:51 AM, Mark Hatle wrote: >>> >>> On 7/31/17 12:40 PM, akuster808 wrote: On 07/31/2017 10:31 AM, Mark Hatle wrote: > > On 7/31/17 12:16 PM, Armin Kuster wrote: >> >> Signed-off-by: Armin Kuster >> --- >> meta/conf/machine/include/arm/arch-armv8.inc | 25 >> + >> 1 file changed, 25 insertions(+) >> >> diff --git a/meta/conf/machine/include/arm/arch-armv8.inc >> b/meta/conf/machine/include/arm/arch-armv8.inc >> index 5e832fa..dc1ba5e 100644 >> --- a/meta/conf/machine/include/arm/arch-armv8.inc >> +++ b/meta/conf/machine/include/arm/arch-armv8.inc >> @@ -1 +1,26 @@ >> +DEFAULTTUNE ?= "armv8-a" > > do we want the '-a'? The other arm (7) are of the format armv7a (no > '-'). works for me either way. While we are at it. How would we want ‘armv8.1-a’, ‘armv8.2-a’, ‘armv8.3-a' formated as? >>> >>> My preference is to drop the '-'. As for the '.', I'm not sure.. not >>> something >>> we've run across before. >>> >>> We could just drop it (the '.'), but it really depends on if armv81a >>> would >>> confuse someone (familiar with arm) or not. >> >> I would suggest to also sync with other distros and ensure that we dont >> do something different. Its very costly later. Since applications get >> ported to most common combination > > Sync what part? naming of file? ( sorry lost regarding your comment) naming convention for arch e.g. -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/2] armv8: update to use armv8-a tune
On 8/1/17 10:20 AM, Khem Raj wrote: > On Tue, Aug 1, 2017 at 8:17 AM, akuster808 wrote: >> >> >> On 07/31/2017 12:04 PM, Khem Raj wrote: >>> >>> >>> On 7/31/17 10:51 AM, Mark Hatle wrote: On 7/31/17 12:40 PM, akuster808 wrote: > > > On 07/31/2017 10:31 AM, Mark Hatle wrote: >> >> On 7/31/17 12:16 PM, Armin Kuster wrote: >>> >>> Signed-off-by: Armin Kuster >>> --- >>> meta/conf/machine/include/arm/arch-armv8.inc | 25 >>> + >>> 1 file changed, 25 insertions(+) >>> >>> diff --git a/meta/conf/machine/include/arm/arch-armv8.inc >>> b/meta/conf/machine/include/arm/arch-armv8.inc >>> index 5e832fa..dc1ba5e 100644 >>> --- a/meta/conf/machine/include/arm/arch-armv8.inc >>> +++ b/meta/conf/machine/include/arm/arch-armv8.inc >>> @@ -1 +1,26 @@ >>> +DEFAULTTUNE ?= "armv8-a" >> >> do we want the '-a'? The other arm (7) are of the format armv7a (no >> '-'). > > works for me either way. > > While we are at it. How would we want ‘armv8.1-a’, ‘armv8.2-a’, > ‘armv8.3-a' > formated as? My preference is to drop the '-'. As for the '.', I'm not sure.. not something we've run across before. We could just drop it (the '.'), but it really depends on if armv81a would confuse someone (familiar with arm) or not. >>> >>> I would suggest to also sync with other distros and ensure that we dont >>> do something different. Its very costly later. Since applications get >>> ported to most common combination >> >> Sync what part? naming of file? ( sorry lost regarding your comment) > > naming convention for arch e.g. > I'd say Debian/Ubuntu -- Fedora/RH would be the two primary sources I'd look at. Between debian package names and RPM package names, it should give a clue if there is any community standard forming for those names. (May still be too premature for those environments for the armv8.X-a naming... and I've not seen it discussed on any other lists either.) --Mark -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/2] armv8: update to use armv8-a tune
On Tue, Aug 1, 2017 at 8:24 AM, Mark Hatle wrote: > On 8/1/17 10:20 AM, Khem Raj wrote: >> On Tue, Aug 1, 2017 at 8:17 AM, akuster808 wrote: >>> >>> >>> On 07/31/2017 12:04 PM, Khem Raj wrote: On 7/31/17 10:51 AM, Mark Hatle wrote: > > On 7/31/17 12:40 PM, akuster808 wrote: >> >> >> On 07/31/2017 10:31 AM, Mark Hatle wrote: >>> >>> On 7/31/17 12:16 PM, Armin Kuster wrote: Signed-off-by: Armin Kuster --- meta/conf/machine/include/arm/arch-armv8.inc | 25 + 1 file changed, 25 insertions(+) diff --git a/meta/conf/machine/include/arm/arch-armv8.inc b/meta/conf/machine/include/arm/arch-armv8.inc index 5e832fa..dc1ba5e 100644 --- a/meta/conf/machine/include/arm/arch-armv8.inc +++ b/meta/conf/machine/include/arm/arch-armv8.inc @@ -1 +1,26 @@ +DEFAULTTUNE ?= "armv8-a" >>> >>> do we want the '-a'? The other arm (7) are of the format armv7a (no >>> '-'). >> >> works for me either way. >> >> While we are at it. How would we want ‘armv8.1-a’, ‘armv8.2-a’, >> ‘armv8.3-a' >> formated as? > > My preference is to drop the '-'. As for the '.', I'm not sure.. not > something > we've run across before. > > We could just drop it (the '.'), but it really depends on if armv81a > would > confuse someone (familiar with arm) or not. I would suggest to also sync with other distros and ensure that we dont do something different. Its very costly later. Since applications get ported to most common combination >>> >>> Sync what part? naming of file? ( sorry lost regarding your comment) >> >> naming convention for arch e.g. >> > > I'd say Debian/Ubuntu -- Fedora/RH would be the two primary sources I'd look > at. > Between debian package names and RPM package names, it should give a clue if > there is any community standard forming for those names. > > (May still be too premature for those environments for the armv8.X-a naming... > and I've not seen it discussed on any other lists either.) yeah, it will be good to not go through the pain of community doing something else later like *-*-gnueabihf triplet was invented and to date we keep fixing packages for OE to account for gnueabihf can be gnueabi + -mfloat-abi=hard but packages just assume > > --Mark -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] glibc: Update to latest on 2.26 pre-release
Signed-off-by: Khem Raj
---
.../glibc/cross-localedef-native_2.25.90.bb| 2 +-
...ress-pedantic-warning-caused-by-statement.patch | 90 ++
meta/recipes-core/glibc/glibc_2.25.90.bb | 3 +-
3 files changed, 93 insertions(+), 2 deletions(-)
create mode 100644
meta/recipes-core/glibc/glibc/0026-assert-Suppress-pedantic-warning-caused-by-statement.patch
diff --git a/meta/recipes-core/glibc/cross-localedef-native_2.25.90.bb
b/meta/recipes-core/glibc/cross-localedef-native_2.25.90.bb
index 5dd0c70400..6d84e52380 100644
--- a/meta/recipes-core/glibc/cross-localedef-native_2.25.90.bb
+++ b/meta/recipes-core/glibc/cross-localedef-native_2.25.90.bb
@@ -22,7 +22,7 @@ SRCBRANCH ?= "master"
GLIBC_GIT_URI ?= "git://sourceware.org/git/glibc.git"
UPSTREAM_CHECK_GITTAGREGEX = "(?P\d+\.\d+(\.\d+)*)"
-SRCREV_glibc ?= "43a9f537fc121a867981ca31ea9d79f33ce0fd24"
+SRCREV_glibc ?= "930324b356778b985d26f30fd0386163852a35fe"
SRCREV_localedef ?= "dfb4afe551c6c6e94f9cc85417bd1f582168c843"
SRC_URI = "${GLIBC_GIT_URI};branch=${SRCBRANCH};name=glibc \
diff --git
a/meta/recipes-core/glibc/glibc/0026-assert-Suppress-pedantic-warning-caused-by-statement.patch
b/meta/recipes-core/glibc/glibc/0026-assert-Suppress-pedantic-warning-caused-by-statement.patch
new file mode 100644
index 00..b2bb96b818
--- /dev/null
+++
b/meta/recipes-core/glibc/glibc/0026-assert-Suppress-pedantic-warning-caused-by-statement.patch
@@ -0,0 +1,90 @@
+From 037283cbc74739b72f36dfec827d120faa243406 Mon Sep 17 00:00:00 2001
+From: Florian Weimer
+Date: Thu, 6 Jul 2017 11:50:55 +0200
+Subject: [PATCH 26/26] assert: Suppress pedantic warning caused by statement
+ expression [BZ# 21242]
+
+On 07/05/2017 10:15 PM, Zack Weinberg wrote:
+> On Wed, Jul 5, 2017 at 11:51 AM, Florian Weimer wrote:
+>> On 07/05/2017 05:46 PM, Zack Weinberg wrote:
+>>> A problem occurs to me: expressions involving VLAs _are_ evaluated
+>>> inside sizeof.
+>>
+>> The type of the sizeof argument would still be int (due to the
+>> comparison against 0), so this doesn't actually occur.
+>
+> I rechecked what C99 says about sizeof and VLAs, and you're right -
+> the operand of sizeof is only evaluated when sizeof is _directly_
+> applied to a VLA. So this is indeed safe, but I think this wrinkle
+> should be mentioned in the comment. Perhaps
+>
+> /* The first occurrence of EXPR is not evaluated due to the sizeof,
+>but will trigger any pedantic warnings masked by the __extension__
+>for the second occurrence. The explicit comparison against zero
+>ensures that sizeof is not directly applied to a function pointer or
+>bit-field (which would be ill-formed) or VLA (which would be evaluated).
*/
+>
+> zw
+
+What about the attached patch?
+
+Siddhesh, is this okay during the freeze? I'd like to backport it to
+2.25 as well.
+
+Thanks,
+Florian
+
+assert: Suppress pedantic warning caused by statement expression
+
+2017-07-06 Florian Weimer
+
+ [BZ #21242]
+ * assert/assert.h [__GNUC__ && !__STRICT_ANSI__] (assert):
+ Suppress pedantic warning resulting from statement expression.
+ (__ASSERT_FUNCTION): Add missing __extendsion__.
+---
+
+Upstream-Status: Submitted
+Signed-off-by: Khem Raj
+
+ assert/assert.h | 12 +---
+ 1 file changed, 9 insertions(+), 3 deletions(-)
+
+diff --git a/assert/assert.h b/assert/assert.h
+index 22f019537c..6801cfeb10 100644
+--- a/assert/assert.h
b/assert/assert.h
+@@ -91,13 +91,19 @@ __END_DECLS
+ ? __ASSERT_VOID_CAST (0) \
+ : __assert_fail (#expr, __FILE__, __LINE__, __ASSERT_FUNCTION))
+ # else
++/* The first occurrence of EXPR is not evaluated due to the sizeof,
++ but will trigger any pedantic warnings masked by the __extension__
++ for the second occurrence. The explicit comparison against zero is
++ required to support function pointers and bit fields in this
++ context, and to suppress the evaluation of variable length
++ arrays. */
+ # define assert(expr)
\
+-({
\
++ ((void) sizeof ((expr) == 0), __extension__ ({ \
+ if (expr)
\
+ ; /* empty */ \
+ else\
+ __assert_fail (#expr, __FILE__, __LINE__, __ASSERT_FUNCTION); \
+-})
++}))
+ # endif
+
+ # ifdef __USE_GNU
+@@ -113,7 +119,7 @@ __END_DECLS
+C9x has a similar variable called __func__, but prefer the GCC one since
+it demangles C++ function names. */
+ # if defined __cplusplus ? __GNUC_PREREQ (2, 6) : __GNUC_PREREQ (2, 4)
+-# define __ASSERT_FUNCTION __PRETTY_FUNCTION__
++# define __ASSERT_FUNCTION __extension__ __PRETTY_FUNCTION__
+ # else
+ # if defin
[OE-core] [PATCH 1/4] wic-image-minimal: drop WKS_FILE_DEPENDS definition
From: Ming Liu
It's being set in image_types_wic.bbclass, not need to double set it
here, furthermore, the dependencies are incomplete by missing
e2fsprogs-native.
Signed-off-by: Ming Liu
---
meta-selftest/recipes-test/images/wic-image-minimal.bb | 2 --
1 file changed, 2 deletions(-)
diff --git a/meta-selftest/recipes-test/images/wic-image-minimal.bb
b/meta-selftest/recipes-test/images/wic-image-minimal.bb
index e1da203..af40d96 100644
--- a/meta-selftest/recipes-test/images/wic-image-minimal.bb
+++ b/meta-selftest/recipes-test/images/wic-image-minimal.bb
@@ -6,8 +6,6 @@ IMAGE_INSTALL = "packagegroup-core-boot"
IMAGE_FSTYPES = "wic"
-WKS_FILE_DEPENDS = "syslinux syslinux-native dosfstools-native mtools-native
gptfdisk-native"
-
LIC_FILES_CHKSUM =
"file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
IMAGE_ROOTFS_EXTRA_SPACE = "2000"
--
2.7.4
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 3/4] qemux86.conf: drop do_image_wic task dependencies
From: Ming Liu They are being controlled by WKS_FILE_DEPENDS_DEFAULT, the code here is redundant and incomplete as well. Signed-off-by: Ming Liu --- meta/conf/machine/qemux86.conf | 1 - 1 file changed, 1 deletion(-) diff --git a/meta/conf/machine/qemux86.conf b/meta/conf/machine/qemux86.conf index c26dda2..f0bebbf 100644 --- a/meta/conf/machine/qemux86.conf +++ b/meta/conf/machine/qemux86.conf @@ -29,4 +29,3 @@ MACHINE_FEATURES += "x86" MACHINE_ESSENTIAL_EXTRA_RDEPENDS += "v86d" WKS_FILE ?= "directdisk.wks" -do_image_wic[depends] += "syslinux:do_populate_sysroot syslinux-native:do_populate_sysroot mtools-native:do_populate_sysroot dosfstools-native:do_populate_sysroot" -- 2.7.4 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/4] Clean up some do_image_wic redundant code
From: Ming Liu Ming Liu (4): wic-image-minimal: drop WKS_FILE_DEPENDS definition image_types_wic.bbclass: deal with dependencies only with WKS_FILE_DEPENDS_DEFAULT qemux86.conf: drop do_image_wic task dependencies qemux86-64.conf: drop do_image_wic task dependencies meta-selftest/recipes-test/images/wic-image-minimal.bb | 2 -- meta/classes/image_types_wic.bbclass | 3 +-- meta/conf/machine/qemux86-64.conf | 1 - meta/conf/machine/qemux86.conf | 1 - 4 files changed, 1 insertion(+), 6 deletions(-) -- 2.7.4 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 2/4] image_types_wic.bbclass: deal with dependencies only with WKS_FILE_DEPENDS_DEFAULT
From: Ming Liu
Drop do_image_wic depends varflags, move the dependencies to
WKS_FILE_DEPENDS_DEFAULT. I can not see the need to maintain them
in two different ways, besides that it's out of USING_WIC control.
Signed-off-by: Ming Liu
---
meta/classes/image_types_wic.bbclass | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/meta/classes/image_types_wic.bbclass
b/meta/classes/image_types_wic.bbclass
index b825b47..7b0a1c7 100644
--- a/meta/classes/image_types_wic.bbclass
+++ b/meta/classes/image_types_wic.bbclass
@@ -39,9 +39,8 @@ IMAGE_CMD_wic[vardepsexclude] = "WKS_FULL_PATH WKS_FILES"
USING_WIC = "${@bb.utils.contains_any('IMAGE_FSTYPES', 'wic ' + '
'.join('wic.%s' % c for c in '${CONVERSIONTYPES}'.split()), '1', '', d)}"
WKS_FILE_CHECKSUM = "${@'${WKS_FULL_PATH}:%s' %
os.path.exists('${WKS_FULL_PATH}') if '${USING_WIC}' else ''}"
do_image_wic[file-checksums] += "${WKS_FILE_CHECKSUM}"
-do_image_wic[depends] += "${@' '.join('%s-native:do_populate_sysroot' % r for
r in ('parted', 'gptfdisk', 'dosfstools', 'mtools'))}"
-WKS_FILE_DEPENDS_DEFAULT = "syslinux-native bmap-tools-native cdrtools-native
btrfs-tools-native squashfs-tools-native e2fsprogs-native"
+WKS_FILE_DEPENDS_DEFAULT = "parted-native gptfdisk-native dosfstools-native
mtools-native syslinux-native bmap-tools-native cdrtools-native
btrfs-tools-native squashfs-tools-native e2fsprogs-native"
WKS_FILE_DEPENDS_BOOTLOADERS = ""
WKS_FILE_DEPENDS_BOOTLOADERS_x86 = "syslinux grub-efi systemd-boot"
WKS_FILE_DEPENDS_BOOTLOADERS_x86-64 = "syslinux grub-efi systemd-boot"
--
2.7.4
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 4/4] qemux86-64.conf: drop do_image_wic task dependencies
From: Ming Liu They are being controlled by WKS_FILE_DEPENDS_DEFAULT, the code here is redundant and incomplete as well. Signed-off-by: Ming Liu --- meta/conf/machine/qemux86-64.conf | 1 - 1 file changed, 1 deletion(-) diff --git a/meta/conf/machine/qemux86-64.conf b/meta/conf/machine/qemux86-64.conf index 10189cb..9f55aaa 100644 --- a/meta/conf/machine/qemux86-64.conf +++ b/meta/conf/machine/qemux86-64.conf @@ -30,4 +30,3 @@ MACHINE_FEATURES += "x86" MACHINE_ESSENTIAL_EXTRA_RDEPENDS += "v86d" WKS_FILE ?= "directdisk.wks" -do_image_wic[depends] += "syslinux:do_populate_sysroot syslinux-native:do_populate_sysroot mtools-native:do_populate_sysroot dosfstools-native:do_populate_sysroot" -- 2.7.4 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [oe-core][PATCH] powertop: update to v2.9
> +S = "${WORKDIR}/${PN}-v${PV}"
ERROR: lib32-powertop-2.9-r0 do_populate_lic: QA Issue: lib32-powertop:
LIC_FILES_CHKSUM points to an invalid file:
/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-world/build/build/tmp/work/x86-pokymllib32-linux/lib32-powertop/2.9-r0/lib32-powertop-v2.9/COPYING
[license-checksum]
BPN, not PN.
Ross
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [oe-core][PATCH 1/1] slang: fix terminfo related problems
Do not use the JD_TERMCAP macro since we cannot get the terminfo from
ncurses pkg-config variants, but fix the macro to not reference host
directories. Also add src/test/Makefile.in so that we can use -ltermcap
if we want to.
Since the recipe DEPENDS on ncurses, we assume terminfo is there.
Signed-off-by: Joe Slater
---
.../slang/slang/terminfo_fixes.patch | 148 +
meta/recipes-extended/slang/slang_2.3.1a.bb| 1 +
2 files changed, 149 insertions(+)
create mode 100644 meta/recipes-extended/slang/slang/terminfo_fixes.patch
diff --git a/meta/recipes-extended/slang/slang/terminfo_fixes.patch
b/meta/recipes-extended/slang/slang/terminfo_fixes.patch
new file mode 100644
index 000..3e6d15a
--- /dev/null
+++ b/meta/recipes-extended/slang/slang/terminfo_fixes.patch
@@ -0,0 +1,148 @@
+Do not use the JD_TERMCAP macro since we cannot get the terminfo from
+ncurses pkg-config, but fix the macro to not reference host directories.
+Also add src/test/Makefile.in so that we can use -ltermcap if we want to.
+
+Upstream-Status: Pending
+
+Signed-off-by: Joe Slater
+
+
+--- a/autoconf/aclocal.m4
b/autoconf/aclocal.m4
+@@ -506,14 +506,10 @@ then
+ else
+MISC_TERMINFO_DIRS=""
+ fi
+-JD_Terminfo_Dirs="$MISC_TERMINFO_DIRS \
+- /usr/lib/terminfo \
+- /usr/share/terminfo \
+- /usr/share/lib/terminfo \
+-/usr/local/lib/terminfo"
++
+ TERMCAP=-ltermcap
+
+-for terminfo_dir in $JD_Terminfo_Dirs
++for terminfo_dir in $MISC_TERMINFO_DIRS
+ do
+if test -d $terminfo_dir
+then
+--- a/autoconf/configure.ac
b/autoconf/configure.ac
+@@ -249,7 +249,14 @@ AC_CHECK_SIZEOF(size_t)
+ JD_CHECK_LONG_LONG
+ JD_LARGE_FILE_SUPPORT
+
+-JD_TERMCAP
++dnl Do not use JD_TERMCAP, since we cannot get terminfo from ncurses*-config
anymore.
++dnl Set TERMCAP=-ltermcap and AC_DEFINE(USE_TERMCAP,1,[Define to use termcap])
++dnl to use libtermcap.
++TERMCAP=""
++MISC_TERMINFO_DIRS=""
++AC_SUBST(TERMCAP)dnl
++AC_SUBST(MISC_TERMINFO_DIRS)dnl
++
+ JD_GCC_WARNINGS
+
+ JD_SET_OBJ_SRC_DIR(src)
+@@ -364,7 +371,7 @@ AC_CONFIG_HEADER(src/sysconf.h:src/confi
+ dnl AC_CONFIG_SUBDIRS(demo)
+
+ AC_OUTPUT(Makefile:autoconf/Makefile.in \
+- src/Makefile slsh/Makefile modules/Makefile demo/Makefile \
++ src/Makefile src/test/Makefile slsh/Makefile modules/Makefile demo/Makefile
\
+ slang.pc:autoconf/slangpc.in \
+ )
+
+--- /dev/null
b/src/test/Makefile.in
+@@ -0,0 +1,90 @@
++# -*- make -*-
++TEST_SCRIPTS_SLC = argv syntax scircuit eqs sscanf loops arith array strops \
++ bstring pack stdio assoc selfload struct nspace path ifeval anytype arrmult
\
++ time utf8 except bugs list regexp method deref naninf overflow sort \
++ longlong signal dollar req docfun debug qualif compare break multline \
++ stack misc posixio posdir proc math
++
++TEST_SCRIPTS_NO_SLC = autoload nspace2 prep
++
++TEST_SCRIPTS = $(TEST_SCRIPTS_SLC) $(TEST_SCRIPTS_NO_SLC)
++
++TEST_PGM = sltest
++MEMCHECK = valgrind --tool=memcheck --leak-check=yes --leak-resolution=med
--num-callers=20
++RUN_TEST_PGM = ./$(TEST_PGM)
++SLANGINC = ..
++SLANGLIB = ../$(ARCH)objs
++OTHER_LIBS = -lm @TERMCAP@
++OTHER_CFLAGS =
++
++runtests: $(TEST_PGM) cleantmp
++ @tests=""; \
++ for test in $(TEST_SCRIPTS); \
++ do \
++ tests="$$tests $$test.sl"; \
++ done; \
++ for test in $(TEST_SCRIPTS_SLC); \
++ do \
++ tests="$$tests $$test.slc"; \
++ done; \
++ MAKERUNNING=1 ./runtests.sh $$tests
++# @touch $(TEST_PGM).c
++
++update: $(TEST_PGM) cleantmp
++ @tests=""; \
++ for X in $(TEST_SCRIPTS); \
++ do \
++if [ ! -e lastrun/$$X.sl ] || [ $$X.sl -nt lastrun/$$X.sl ] ; \
++then \
++ tests="$$tests $$X.sl"; \
++fi \
++ done; \
++ for X in $(TEST_SCRIPTS_SLC); \
++ do \
++if [ ! -e lastrun/$$X.slc ] || [ $$X.sl -nt lastrun/$$X.slc ] ; \
++then \
++ tests="$$tests $$X.slc"; \
++fi \
++ done; \
++ if test -n "$$tests"; \
++ then \
++MAKERUNNING=1 ./runtests.sh $$tests; \
++ fi
++# @touch $(TEST_PGM).c
++
++memcheck_runtests: $(TEST_PGM) cleantmp
++ @echo ""
++ @echo "Running tests:"
++ @echo ""
++ -@for X in $(TEST_SCRIPTS); \
++ do \
++ $(MEMCHECK) --log-file=log.$${X} $(RUN_TEST_PGM) $$X.sl; \
++ grep ERROR log.$${X}; grep 'lost: [^0]' log.$${X}; \
++ $(MEMCHECK) --log-file=log.$${X}_u $(RUN_TEST_PGM) -utf8 $$X.sl; \
++ grep ERROR log.$${X}_u; grep 'lost: [^0]' log.$${X}_u; \
++ done
++# touch $(TEST_PGM).c
++
++memcheck_runtests_slc: $(TEST_PGM) cleantmp
++ @echo ""
++ @echo "Running tests:"
++ @echo ""
++ -@for X in $(TEST_SCRIPTS_SLC); \
++ do \
++ $(MEMCHECK) --log-file=log.$${X}_c $(RUN_TEST_PGM) $$X.slc; \
++ $(MEMCHECK) --log-file=log.$${X}_uc $(RUN_TEST_PGM) -utf8 $$X.slc; \
++
Re: [OE-core] [PATCHv2] (morty) Arch Linux build fixes
On 08/01/2017 02:50 AM, Ian Arkver wrote: On 21/06/17 10:05, Anton Novikov wrote: [3 patch attachments] only one patch is missing "fix case fallthrough and printf overflow warnings" the others I already had from other back ports. all are in my akuster/morty-next. - armin Any word on getting these patches applied to Morty? Is anything blocking them? Maybe they need resubmitted as individual patches? They do seem to apply cleanly on the current tip of morty (7d5822bf4c) and do fix various automake and gcc7 host build failures. Regards, Ian -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCHv2] (morty) Arch Linux build fixes
On Tue, Aug 1, 2017 at 5:30 PM, akuster808 wrote: > > > On 08/01/2017 02:50 AM, Ian Arkver wrote: >> >> On 21/06/17 10:05, Anton Novikov wrote: >>> >>> [3 patch attachments] > > > only one patch is missing > > "fix case fallthrough and printf overflow warnings" > > the others I already had from other back ports. all are in my > akuster/morty-next. It has been there for a while; what is holding them to be applied? -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCHv2] (morty) Arch Linux build fixes
On 08/01/2017 01:32 PM, Otavio Salvador wrote: On Tue, Aug 1, 2017 at 5:30 PM, akuster808 wrote: On 08/01/2017 02:50 AM, Ian Arkver wrote: On 21/06/17 10:05, Anton Novikov wrote: [3 patch attachments] only one patch is missing "fix case fallthrough and printf overflow warnings" the others I already had from other back ports. all are in my akuster/morty-next. It has been there for a while; what is holding them to be applied? clean build in the AB. - armin -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCHv2] (morty) Arch Linux build fixes
On Tue, Aug 1, 2017 at 5:33 PM, akuster808 wrote: > > > On 08/01/2017 01:32 PM, Otavio Salvador wrote: >> >> On Tue, Aug 1, 2017 at 5:30 PM, akuster808 wrote: >>> >>> >>> On 08/01/2017 02:50 AM, Ian Arkver wrote: On 21/06/17 10:05, Anton Novikov wrote: > > [3 patch attachments] >>> >>> >>> only one patch is missing >>> >>> "fix case fallthrough and printf overflow warnings" >>> >>> the others I already had from other back ports. all are in my >>> akuster/morty-next. >> >> It has been there for a while; what is holding them to be applied? > > > clean build in the AB. What are the errors? maybe we could help. -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
