Re: [oe] mesa-gl build failing for RPi0
On Fri, Oct 27, 2017 at 4:43 AM, Scott Ellis wrote: > Using rocko > > ... > | glsl/.libs/libstandalone.a(libmesautil_la-disk_cache.o): In function > `evict_lru_item': > | /usr/src/debug/mesa-gl/2_17.1.7-r0/mesa-17.1.7/src/util/disk_cache.c:615: > undefined reference to `__atomic_fetch_add_8' > | glsl/.libs/libstandalone.a(libmesautil_la-disk_cache.o): In function > `cache_put': > | /usr/src/debug/mesa-gl/2_17.1.7-r0/mesa-17.1.7/src/util/disk_cache.c:886: > undefined reference to `__atomic_fetch_add_8' > | glsl/.libs/libstandalone.a(libmesautil_la-disk_cache.o): In function > `disk_cache_remove': > | /usr/src/debug/mesa-gl/2_17.1.7-r0/mesa-17.1.7/src/util/disk_cache.c:637: > undefined reference to `__atomic_fetch_add_8' > | collect2: error: ld returned 1 exit status > | Makefile:2076: recipe for target 'glsl_compiler' failed > | make[4]: *** [glsl_compiler] Error 1 > | make[4]: Leaving directory > '/oe4/rocko/tmp-rocko/work/arm1176jzfshf-vfp-poky-linux-gnueabi/mesa-gl/2_17.1.7-r0/build/src/compiler' > | Makefile:1528: recipe for target 'all' failed > | make[3]: *** [all] Error 2 > | make[3]: Leaving directory > '/oe4/rocko/tmp-rocko/work/arm1176jzfshf-vfp-poky-linux-gnueabi/mesa-gl/2_17.1.7-r0/build/src/compiler' > | Makefile:840: recipe for target 'all-recursive' failed > | make[2]: *** [all-recursive] Error 1 > | make[2]: Leaving directory > '/oe4/rocko/tmp-rocko/work/arm1176jzfshf-vfp-poky-linux-gnueabi/mesa-gl/2_17.1.7-r0/build/src' > | Makefile:631: recipe for target 'all' failed > | make[1]: *** [all] Error 2 > | make[1]: Leaving directory > '/oe4/rocko/tmp-rocko/work/arm1176jzfshf-vfp-poky-linux-gnueabi/mesa-gl/2_17.1.7-r0/build/src' > | Makefile:631: recipe for target 'all-recursive' failed > | make: *** [all-recursive] Error 1 > | ERROR: oe_runmake failed > > > The solution used for armv5 boards in mesa.inc works for armv6 > > CFLAGS_append_armv6 = " -DMISSING_64BIT_ATOMICS" > isn't rpi0 based on armv6k for which 64bit atomics should be fine. are we using wrong tune files ? > > I'm using it in a private layer bbappend, but might belong > in mesa.inc alongside the armv5 line. > > > Some discussion of the bug here > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874531 > > > -- > ___ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-webserver][PATCH] phpmyadmin: update to version 4.7.5
Signed-off-by: Derek Straka
---
.../phpmyadmin/{phpmyadmin_4.7.3.bb => phpmyadmin_4.7.5.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta-webserver/recipes-php/phpmyadmin/{phpmyadmin_4.7.3.bb =>
phpmyadmin_4.7.5.bb} (90%)
diff --git a/meta-webserver/recipes-php/phpmyadmin/phpmyadmin_4.7.3.bb
b/meta-webserver/recipes-php/phpmyadmin/phpmyadmin_4.7.5.bb
similarity index 90%
rename from meta-webserver/recipes-php/phpmyadmin/phpmyadmin_4.7.3.bb
rename to meta-webserver/recipes-php/phpmyadmin/phpmyadmin_4.7.5.bb
index 9949a73..fa447b9 100644
--- a/meta-webserver/recipes-php/phpmyadmin/phpmyadmin_4.7.3.bb
+++ b/meta-webserver/recipes-php/phpmyadmin/phpmyadmin_4.7.5.bb
@@ -11,8 +11,8 @@ SRC_URI =
"https://files.phpmyadmin.net/phpMyAdmin/${PV}/phpMyAdmin-${PV}-all-la
file://apache.conf \
"
-SRC_URI[md5sum] = "4b0c5dbaf871eb86671613da3c31e6b3"
-SRC_URI[sha256sum] =
"ed51669043f62494dc3bc21a87423373164ff63865a6c6bceaee535ef785f33e"
+SRC_URI[md5sum] = "23f65155f37bef0addb7324d45671a4e"
+SRC_URI[sha256sum] =
"e4f53b8a5a8e32cea389718c6f6f282e9ac22ed5f31f67d88266aa27ae0a1ca3"
S = "${WORKDIR}/phpMyAdmin-${PV}-all-languages"
--
2.7.4
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-webserver][PATCH] apache2: update to version 2.4.29
Updated license checksum due to whitespace modifications
Signed-off-by: Derek Straka
---
.../apache2/{apache2-native_2.4.27.bb => apache2-native_2.4.29.bb} | 6 +++---
.../recipes-httpd/apache2/{apache2_2.4.27.bb => apache2_2.4.29.bb} | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
rename meta-webserver/recipes-httpd/apache2/{apache2-native_2.4.27.bb =>
apache2-native_2.4.29.bb} (86%)
rename meta-webserver/recipes-httpd/apache2/{apache2_2.4.27.bb =>
apache2_2.4.29.bb} (97%)
diff --git a/meta-webserver/recipes-httpd/apache2/apache2-native_2.4.27.bb
b/meta-webserver/recipes-httpd/apache2/apache2-native_2.4.29.bb
similarity index 86%
rename from meta-webserver/recipes-httpd/apache2/apache2-native_2.4.27.bb
rename to meta-webserver/recipes-httpd/apache2/apache2-native_2.4.29.bb
index 4e893db..36f073c 100644
--- a/meta-webserver/recipes-httpd/apache2/apache2-native_2.4.27.bb
+++ b/meta-webserver/recipes-httpd/apache2/apache2-native_2.4.29.bb
@@ -14,9 +14,9 @@ SRC_URI = "${APACHE_MIRROR}/httpd/httpd-${PV}.tar.bz2 \
S = "${WORKDIR}/httpd-${PV}"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=dbff5a2b542fa58854455bf1a0b94b83"
-SRC_URI[md5sum] = "97b6bbfa83c866dbe20ef317e3afd108"
-SRC_URI[sha256sum] =
"71fcc128238a690515bd8174d5330a5309161ef314a326ae45c7c15ed139c13a"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=a62b0c7623826ff99766ff13fb9007f8"
+SRC_URI[md5sum] = "0c599404ef6b69eee95bcd9fcd094407"
+SRC_URI[sha256sum] =
"53a5a25568a2a27428b2214980564bc1c38c1abf9ccc7630b639991f7f00"
EXTRA_OECONF = "--with-apr=${STAGING_BINDIR_CROSS}/apr-1-config \
--with-apr-util=${STAGING_BINDIR_CROSS}/apu-1-config \
diff --git a/meta-webserver/recipes-httpd/apache2/apache2_2.4.27.bb
b/meta-webserver/recipes-httpd/apache2/apache2_2.4.29.bb
similarity index 97%
rename from meta-webserver/recipes-httpd/apache2/apache2_2.4.27.bb
rename to meta-webserver/recipes-httpd/apache2/apache2_2.4.29.bb
index 1880867..f0298b9 100644
--- a/meta-webserver/recipes-httpd/apache2/apache2_2.4.27.bb
+++ b/meta-webserver/recipes-httpd/apache2/apache2_2.4.29.bb
@@ -23,9 +23,9 @@ SRC_URI = "${APACHE_MIRROR}/httpd/httpd-${PV}.tar.bz2 \
file://volatiles.04_apache2 \
"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=dbff5a2b542fa58854455bf1a0b94b83"
-SRC_URI[md5sum] = "97b6bbfa83c866dbe20ef317e3afd108"
-SRC_URI[sha256sum] =
"71fcc128238a690515bd8174d5330a5309161ef314a326ae45c7c15ed139c13a"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=a62b0c7623826ff99766ff13fb9007f8"
+SRC_URI[md5sum] = "0c599404ef6b69eee95bcd9fcd094407"
+SRC_URI[sha256sum] =
"53a5a25568a2a27428b2214980564bc1c38c1abf9ccc7630b639991f7f00"
S = "${WORKDIR}/httpd-${PV}"
--
2.7.4
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-qt5][PATCH 2/2] qmake5_base: add OE_QMAKE_OBJCOPY from OBJCOPY
I've dropped the "qmake5_base: add OE_QMAKE_OBJCOPY from OBJCOPY"
change, so now I have only following 3 included:
== Tested changes (not included in master yet) - meta-qt5 ==
latest upstream commit:
2c3ef00 qt5: add missing commercial license
not included in master yet:
bbb3044 meta-qt5: Update to 5.9.2 release
8fd20e8 nativesdk-qtbase Enable objcopy for qmake
60329bc qt5-ptest.inc: fix qtxmlpatterns:do_install_ptest out-of-order call
and it still fails the same as shown in:
http://errors.yoctoproject.org/Errors/Build/47776/
I'm going to drop the 2nd objcopy change and retrigger the builds.
On Fri, Oct 27, 2017 at 7:53 AM, Daniel Mack wrote:
> On Thursday, October 26, 2017 03:36 PM, Denys Dmytriyenko wrote:
> > On Thu, Oct 26, 2017 at 03:07:36PM +0200, Daniel Mack wrote:
> >> On Thursday, October 26, 2017 02:55 PM, Denys Dmytriyenko wrote:
> >>> On Tue, Oct 24, 2017 at 03:33:10PM +0200, Daniel Mack wrote:
> Hi,
>
> On Saturday, October 21, 2017 12:54 AM, Martin Jansa wrote:
> > Either this or the ptest change seems to cause:
> > http://errors.yoctoproject.org/Errors/Details/157417/
>
> FTR, I see the same error locally. Reverting both 8fd20e8b1
> ("nativesdk-qtbase Enable objcopy for qmake") and 5ec6b97a8
> ("qmake5_base: add OE_QMAKE_OBJCOPY from OBJCOPY") in the master-next
> branch of meta-qt5 fixes things for me.
> >>>
> >>> Have you tried bisecting by any chance?
> >>
> >> bisect what exactly? If I take your patch out of my stack, qtbase
> >> builds. If I don't it doesn't. Can I provide more information somehow?
> >
> > That's not what you said above - we are trying to figure out which of
> the 2
> > (*two*) patches causes the breakage, hence the question about
> bisecting...
>
> Ah, sorry, my bad.
>
> Only reverting "qmake5_base: add OE_QMAKE_OBJCOPY from OBJCOPY" fixes a
> build that does not have a native sdk target. I assume the 2nd patch
> would break a native sdk, but I can't tell.
>
> I can provide full build logs if you want.
>
>
> Thanks,
> Daniel
>
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] openjdk checksum wrong
On Fri, Oct 27, 2017 at 3:03 AM, Fan Xin wrote: Hello, I am trying to build openjdk-8 based jethro, and I use the recipe file from meta-java. I meet the following error message. ERROR: Fetcher failure for URL: 'http://hg.openjdk.java.net/jdk8u/jdk8u/jdk/archive/48c99b423839.tar.bz2;name=jdk;unpack=false'. Checksum mismatch! File: '/downloads/48c99b423839.tar.bz2' has md5 checksum 7cde47e80f540aa01d51376affe6b8b0 when 316fc871a823ff8f1db39a2fca51bd12 was expected File: '/downloads/48c99b423839.tar.bz2' has sha256 checksum 8627e3e19ac6cfd250e435be659fbfdf65f3cb2c6c9678c9e5ec0db2ae1fcc90 when bca18458ba0a0b8d79639829b8a71cdf65dd788b5c28658102b6b4691a47a420 was expected If this change is expected (e.g. you have upgraded to a new version without updating the checksums) then you can use these lines within the recipe: SRC_URI[jdk.md5sum] = "7cde47e80f540aa01d51376affe6b8b0" SRC_URI[jdk.sha256sum] = "8627e3e19ac6cfd250e435be659fbfdf65f3cb2c6c9678c9e5ec0db2ae1fcc90" Otherwise you should retry the download and/or check with upstream to determine if the file has become corrupted or otherwise unexpectedly modified. It said the checksum mismatch, but I did not modify the recipe file and archive file. I just download the recipe file and try to build it. Cound anyone tell me what is wrong I have done? or how to modify this. By the way, if I modify the recipe file with the new md5sum code, the build will fail at the unpack phase and get the "Data integrity error". create a patch to fix the checksums (and send it to the mailing list) and for the other issue, start a new thread with the problem. Best Regards, Fan Xin -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] Method for specifying which among a recipe's multiple available licenses is desired?
Hi,
I'm searching for an annotation that I can insert (perhaps with a
.bbappend) into a recipe that indicates which of the multiple licensing
terms I elect to use for a given recipe.
The regular LICENSE_FLAGS_WHITELIST variable is somewhat related, but it
works in the opposite way: make an exception to global preference against a
license.
What I had in mind would work as follows. Suppose foo.bb has:
LICENSE="MIT BSD LGPLv2 LGPLv3"
If I choose to take only the MIT or LGPLv2 terms of use for this one
package (not as an overall global prohibition against the remaining
licenses), the idea is that I would write something like:
LICENSE_CHOSEN="MIT LGPLv2"
The main desired outcome is that the build/tmp/deploy/license/
directory will only contain the texts of the license terms that I actually
accepted, rather than all conceivable ones under which Foo is offered.
It would be a bonus if some Bitbake magic behind the scenes would validate
that there is a nonempty intersection between ${LICENSE} and
${LICENSE_CHOSEN}. If there's no overlap, an explicit fatal error would be
nice. But this isn't a deal-breaker; I can infer this from an empty
build/tmp/deploy/license/ directory.
Are there any existing add-on bbclass'es that might do this? I had a brief
try at rolling my own, but parsing the nested LICENSE text involving && and
|| operators looks non-trivial.
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-browser] Modern Chromium with GN
On Mon, Oct 23, 2017 at 9:33 AM, Raphael Kubo da Costa wrote: > Otavio Salvador writes: | g++ -MMD -MF base/base_paths.o.d | -I/z/chromium/crosswalk/build/tmp-glibc/work/x86_64-linux/gn-native/62.0.3202.62-r0/chromium-62.0.3202.62/out_bootstrap/gen | -I/z/chromium/crosswalk/build/tmp-glibc/work/x86_64-linux/gn-native/62.0.3202.62-r0/chromium-62.0.3202.62 | -isystem/z/chromium/crosswalk/build/tmp-glibc/work/x86_64-linux/gn-native/62.0.3202.62-r0/recipe-sysroot-native/usr/include | -O2 -pipe -DNO_TCMALLOC -D__STDC_FORMAT_MACROS -O2 -g0 | -D_FILE_OFFSET_BITS=64 -D__STDC_CONSTANT_MACROS | -D__STDC_FORMAT_MACROS -pthread -pipe -fno-exceptions | -isystem/z/chromium/crosswalk/build/tmp-glibc/work/x86_64-linux/gn-native/62.0.3202.62-r0/recipe-sysroot-native/usr/include | -O2 -pipe -std=c++14 -Wno-c++11-narrowing -c | /z/chromium/crosswalk/build/tmp-glibc/work/x86_64-linux/gn-native/62.0.3202.62-r0/chromium-62.0.3202.62/base/base_paths.cc | -o base/base_paths.o | g++: error: unrecognized command line option ‘-std=c++14’ >>> >>> Ouch :( That's a new kind of issue I was not expecting. >> >> It needs to check if c++14 is really needed for GN to work. Better >> would it depends on gn-native and it to be handled elsewhere. > > While this specific issue is in GN, I expect it to happen during the > Chromium build as well, as some tools are built and run on the host > machine. > > Even if GN specifically does not depend on C++14 now, working around > that is an uphill battle, as the Chromium project requires a C++14 > compiler and multiple parts of the code base will start using C++14 > features (or already are). Ouch for sure! For some strange reason I was under the impression OE builds created a native gcc for things like this! Oh well, I was able to sort out the native compiler issue on my openSUSE 42.2 system; the default gcc is 4.8, but there are packages for gcc5 and gcc6 so I just installed the gcc6 one and used update-alternatives. It works, but it will lead to some interesting questions wrt support and basic OE support for openSUSE (however, that'll be a different discussion for another day and probably for another mailing list). I was able to successfully build for the minnow board (x86_64), but when I tried building for the 32-bit variant for raspberrypi3 I got: | install: cannot stat 'swiftshader/libEGL.so': No such file or directory during the do_install step for chromium itself. Odd, I thought egl came from mesa? (but then again I thought OE built its own gcc-native... :-S -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-perl][PATCH v2] README: add self as maintainer
I have been, in practice, maintaining meta-perl for several years now. Given discussion at OEDEM, make it official. Signed-off-by: Tim Orling --- meta-perl/README | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/meta-perl/README b/meta-perl/README index 68160a628..67f291079 100644 --- a/meta-perl/README +++ b/meta-perl/README @@ -80,7 +80,9 @@ Send patches / pull requests to openembedded-devel@lists.openembedded.org with When sending single patches, please using something like: 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-perl][PATCH' -Layer maintainer: Hongxu Jia +Layer maintainers: +Hongxu Jia +Tim "moto-timo" Orling License --- -- 2.13.5 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-perl][PATCH] README: add self as maintainer
I have been, in practice, maintinaing meta-perl for several years now. Given discussion at OEDEM, make it official. Signed-off-by: Tim Orling --- meta-perl/README | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/meta-perl/README b/meta-perl/README index 68160a628..67f291079 100644 --- a/meta-perl/README +++ b/meta-perl/README @@ -80,7 +80,9 @@ Send patches / pull requests to openembedded-devel@lists.openembedded.org with When sending single patches, please using something like: 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-perl][PATCH' -Layer maintainer: Hongxu Jia +Layer maintainers: +Hongxu Jia +Tim "moto-timo" Orling License --- -- 2.13.5 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-webserver] [PATCH] fix nginx with large files support
Thanks, patch attached.
Signed-off-by: Wangchong Zhou
---
meta-webserver/recipes-httpd/nginx/nginx.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-webserver/recipes-httpd/nginx/nginx.inc
b/meta-webserver/recipes-httpd/nginx/nginx.inc
index 4a97e2670..4cdf892c7 100644
--- a/meta-webserver/recipes-httpd/nginx/nginx.inc
+++ b/meta-webserver/recipes-httpd/nginx/nginx.inc
@@ -57,7 +57,7 @@ do_configure () {
--with-ptr-size=${PTRSIZE} \
--with-sig-atomic-t=${PTRSIZE} \
--with-size-t=${PTRSIZE} \
---with-off-t=${PTRSIZE} \
+--with-off-t=8 \
--with-time-t=${PTRSIZE} \
--with-sys-nerr=132 \
--conf-path=${sysconfdir}/nginx/nginx.conf \
--
2.13.5
On Thu, Oct 26, 2017 at 9:05 PM, Andre McCurdy wrote:
> On Tue, Oct 24, 2017 at 8:06 PM, Wangchong Zhou
> wrote:
> > On Tue, Oct 24, 2017 at 11:01 PM, Andre McCurdy
> wrote:
> >> Note that disabling the largefile distro feature isn't supported in
> >> oe-core any more (the conditional tests have been removed, so all
> >> recipes in oe-core build with LFS enabled even if you disable the
> >> largefile distro feature).
> >>
> >> http://git.openembedded.org/openembedded-core/commit/?id=
> a75ccaea77c8aad8d46e87e8ed4af2e2e0ad5327
> >>
> >> It's perhaps not the right approach to be adding new conditional tests
> >> now in meta-oe.
> >
> > So guess we are safe to hardcode off_t to be 8?
>
> Yes, I think so.
>
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-oe][PATCH] mraa/upm: drop HAVE_NODEJS conditional
HAVE_NODEJS is a leftover from meta-refkit-core where the
layer had to adapt to different BBLAYER combinations (some
where nodejs wasn't available but mraa/upm were).
mraa/upm nodejs bindings currently fail to build (due to a problem
in swig with nodejs > v7.x) so we keep them disabled until a newer
version of swig lands in OE-core.
The commit adds BINDINGS overrides for armv4/5 to remind that nodejs
isn't available on those architectures.
Signed-off-by: Mikko Ylinen
---
meta-oe/recipes-extended/mraa/mraa_git.bb | 8 +++-
meta-oe/recipes-extended/upm/upm_git.bb | 8 +++-
2 files changed, 14 insertions(+), 2 deletions(-)
diff --git a/meta-oe/recipes-extended/mraa/mraa_git.bb
b/meta-oe/recipes-extended/mraa/mraa_git.bb
index 616048fac..c4b9c6f90 100644
--- a/meta-oe/recipes-extended/mraa/mraa_git.bb
+++ b/meta-oe/recipes-extended/mraa/mraa_git.bb
@@ -31,7 +31,13 @@ FILES_${PN}-utils = "${bindir}/"
# override this in local.conf to get needed bindings.
# BINDINGS_pn-mraa="python"
# will result in only the python bindings being built/packaged.
-BINDINGS ??= "python ${@ 'nodejs' if oe.types.boolean(d.getVar('HAVE_NODEJS')
or '0') else '' }"
+# Note: 'nodejs' is disabled by default because the bindings
+# generation currently fails with nodejs (>v7.x).
+BINDINGS ??= "python"
+
+# nodejs isn't available for armv4/armv5 architectures
+BINDINGS_armv4 ??= "python"
+BINDINGS_armv5 ??= "python"
PACKAGECONFIG ??= "${@bb.utils.contains('PACKAGES', 'node-${PN}', 'nodejs',
'', d)} \
${@bb.utils.contains('PACKAGES', '${PYTHON_PN}-${PN}', 'python', '', d)}"
diff --git a/meta-oe/recipes-extended/upm/upm_git.bb
b/meta-oe/recipes-extended/upm/upm_git.bb
index 38065ce53..a5c2bb321 100644
--- a/meta-oe/recipes-extended/upm/upm_git.bb
+++ b/meta-oe/recipes-extended/upm/upm_git.bb
@@ -26,7 +26,13 @@ inherit distutils3-base cmake
# override this in local.conf to get needed bindings.
# BINDINGS_pn-upm="python"
# will result in only the python bindings being built/packaged.
-BINDINGS ??= "python ${@ 'nodejs' if oe.types.boolean(d.getVar('HAVE_NODEJS')
or '0') else '' }"
+# Note: 'nodejs' is disabled by default because the bindings
+# generation currently fails with nodejs (>v7.x).
+BINDINGS ??= "python"
+
+# nodejs isn't available for armv4/armv5 architectures
+BINDINGS_armv4 ??= "python"
+BINDINGS_armv5 ??= "python"
PACKAGECONFIG ??= "${@bb.utils.contains('PACKAGES', 'node-${PN}', 'nodejs',
'', d)} \
${@bb.utils.contains('PACKAGES', '${PYTHON_PN}-${PN}', 'python', '', d)}"
--
2.11.0
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] mesa-gl build failing for RPi0
Using rocko ... | glsl/.libs/libstandalone.a(libmesautil_la-disk_cache.o): In function `evict_lru_item': | /usr/src/debug/mesa-gl/2_17.1.7-r0/mesa-17.1.7/src/util/disk_cache.c:615: undefined reference to `__atomic_fetch_add_8' | glsl/.libs/libstandalone.a(libmesautil_la-disk_cache.o): In function `cache_put': | /usr/src/debug/mesa-gl/2_17.1.7-r0/mesa-17.1.7/src/util/disk_cache.c:886: undefined reference to `__atomic_fetch_add_8' | glsl/.libs/libstandalone.a(libmesautil_la-disk_cache.o): In function `disk_cache_remove': | /usr/src/debug/mesa-gl/2_17.1.7-r0/mesa-17.1.7/src/util/disk_cache.c:637: undefined reference to `__atomic_fetch_add_8' | collect2: error: ld returned 1 exit status | Makefile:2076: recipe for target 'glsl_compiler' failed | make[4]: *** [glsl_compiler] Error 1 | make[4]: Leaving directory '/oe4/rocko/tmp-rocko/work/arm1176jzfshf-vfp-poky-linux-gnueabi/mesa-gl/2_17.1.7-r0/build/src/compiler' | Makefile:1528: recipe for target 'all' failed | make[3]: *** [all] Error 2 | make[3]: Leaving directory '/oe4/rocko/tmp-rocko/work/arm1176jzfshf-vfp-poky-linux-gnueabi/mesa-gl/2_17.1.7-r0/build/src/compiler' | Makefile:840: recipe for target 'all-recursive' failed | make[2]: *** [all-recursive] Error 1 | make[2]: Leaving directory '/oe4/rocko/tmp-rocko/work/arm1176jzfshf-vfp-poky-linux-gnueabi/mesa-gl/2_17.1.7-r0/build/src' | Makefile:631: recipe for target 'all' failed | make[1]: *** [all] Error 2 | make[1]: Leaving directory '/oe4/rocko/tmp-rocko/work/arm1176jzfshf-vfp-poky-linux-gnueabi/mesa-gl/2_17.1.7-r0/build/src' | Makefile:631: recipe for target 'all-recursive' failed | make: *** [all-recursive] Error 1 | ERROR: oe_runmake failed The solution used for armv5 boards in mesa.inc works for armv6 CFLAGS_append_armv6 = " -DMISSING_64BIT_ATOMICS" I'm using it in a private layer bbappend, but might belong in mesa.inc alongside the armv5 line. Some discussion of the bug here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874531 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe][PATCH] spi-tools: Add version info.
On 10/27/2017 12:14 PM, Fan Xin wrote:
> Signed-off-by: Fan Xin
> ---
> meta-oe/recipes-support/spitools/spitools_git.bb | 7 ++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/meta-oe/recipes-support/spitools/spitools_git.bb
> b/meta-oe/recipes-support/spitools/spitools_git.bb
> index f808125..2eedf8c 100644
> --- a/meta-oe/recipes-support/spitools/spitools_git.bb
> +++ b/meta-oe/recipes-support/spitools/spitools_git.bb
> @@ -4,11 +4,16 @@ AUTHOR = "Christophe BLAESS"
> LICENSE="GPLv2"
> LIC_FILES_CHKSUM = "file://LICENSE;md5=8c1ae6c159876a0ba63099614381"
>
> +PR = "r0"
Drop the PR.
Philip
> +
> +BPV = "0.8.1"
> +PV = "${BPV}"
> +SRCREV = "03405ab45884e4264dfa0371c032b2baaeeaaa98"
> +
> S = "${WORKDIR}/git"
>
> SRC_URI = "git://github.com/cpb-/spi-tools.git;protocol=git"
>
> -SRCREV = "03405ab45884e4264dfa0371c032b2baaeeaaa98"
>
> inherit autotools
>
>
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-oe][PATCH] spi-tools: Add version info.
Signed-off-by: Fan Xin
---
meta-oe/recipes-support/spitools/spitools_git.bb | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/meta-oe/recipes-support/spitools/spitools_git.bb
b/meta-oe/recipes-support/spitools/spitools_git.bb
index f808125..2eedf8c 100644
--- a/meta-oe/recipes-support/spitools/spitools_git.bb
+++ b/meta-oe/recipes-support/spitools/spitools_git.bb
@@ -4,11 +4,16 @@ AUTHOR = "Christophe BLAESS"
LICENSE="GPLv2"
LIC_FILES_CHKSUM = "file://LICENSE;md5=8c1ae6c159876a0ba63099614381"
+PR = "r0"
+
+BPV = "0.8.1"
+PV = "${BPV}"
+SRCREV = "03405ab45884e4264dfa0371c032b2baaeeaaa98"
+
S = "${WORKDIR}/git"
SRC_URI = "git://github.com/cpb-/spi-tools.git;protocol=git"
-SRCREV = "03405ab45884e4264dfa0371c032b2baaeeaaa98"
inherit autotools
--
2.7.4
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-browser] Modern Chromium with GN
On 27/10/17 10:49, Daniel Mack wrote: > > I'd like to give Chromium 62 a shot on arm64, but the recipes currently > only support x11, is that correct? My platform is based on wayland, any > plans on supporting that? > The problem is that upstream Chromium does not support Wayland natively yet. There is a fork under development to implement this support, which is quite advanced now: https://github.com/Igalia/chromium Patches from the fork will start pouring into upstream Chromium shortly. -- Jacobo Aragunde Software Engineer at Igalia -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-browser] Modern Chromium with GN
Hi, On Wednesday, October 11, 2017 05:00 PM, Raphael Kubo da Costa wrote: > Trevor Woerner writes: >> Hi Raphael, >> >> On Tue, Oct 10, 2017 at 3:10 PM, Kubo Da Costa, Raphael >> wrote: >>> On Tue, 2017-10-10 at 14:28 -0400, Trevor Woerner wrote: >>> I've pushed commit a0db280 to my chromium61 branch; that one allowed me >>> to get to the end of the build without any other issues. Let me know if >>> that's enough to get master working for you. >> >> Excellent! Yes, this update works for me against master :-) >> >> Has anyone started trying to integrate this with meta-browser? > > That's the next part of my plan, I hope to get around to it this week. I'd like to give Chromium 62 a shot on arm64, but the recipes currently only support x11, is that correct? My platform is based on wayland, any plans on supporting that? Thanks, Daniel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-selinux][PATCH] audit: upgrade 2.7.6 -> 2.8.1
Signed-off-by: Fan Xin
---
recipes-security/audit/{audit_2.7.6.bb => audit_2.8.1.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename recipes-security/audit/{audit_2.7.6.bb => audit_2.8.1.bb} (96%)
diff --git a/recipes-security/audit/audit_2.7.6.bb
b/recipes-security/audit/audit_2.8.1.bb
similarity index 96%
rename from recipes-security/audit/audit_2.7.6.bb
rename to recipes-security/audit/audit_2.8.1.bb
index 5bfda7b..52ae4bf 100644
--- a/recipes-security/audit/audit_2.7.6.bb
+++ b/recipes-security/audit/audit_2.8.1.bb
@@ -15,8 +15,8 @@ SRC_URI =
"http://people.redhat.com/sgrubb/${BPN}/${BPN}-${PV}.tar.gz \
file://auditd.service \
file://audit-volatile.conf \
"
-SRC_URI[md5sum] = "55a81bbed973b58a90590c949e71dc3e"
-SRC_URI[sha256sum] =
"fa65289cffdc95a25bfbdba541f43ee1b12c707090a38fd027dcf9354b9014e7"
+SRC_URI[md5sum] = "76ce8b6a00a1dd0b52a87312eaec0e8e"
+SRC_URI[sha256sum] =
"1becde92ff6e81798fa8878820ab2497d867036a6596f55109504b37c8b33b6c"
inherit autotools pythonnative update-rc.d systemd
--
2.7.4
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] openjdk checksum wrong
Hello, I am trying to build openjdk-8 based jethro, and I use the recipe file from meta-java. I meet the following error message. ERROR: Fetcher failure for URL: 'http://hg.openjdk.java.net/jdk8u/jdk8u/jdk/archive/48c99b423839.tar.bz2;name=jdk;unpack=false'. Checksum mismatch! File: '/downloads/48c99b423839.tar.bz2' has md5 checksum 7cde47e80f540aa01d51376affe6b8b0 when 316fc871a823ff8f1db39a2fca51bd12 was expected File: '/downloads/48c99b423839.tar.bz2' has sha256 checksum 8627e3e19ac6cfd250e435be659fbfdf65f3cb2c6c9678c9e5ec0db2ae1fcc90 when bca18458ba0a0b8d79639829b8a71cdf65dd788b5c28658102b6b4691a47a420 was expected If this change is expected (e.g. you have upgraded to a new version without updating the checksums) then you can use these lines within the recipe: SRC_URI[jdk.md5sum] = "7cde47e80f540aa01d51376affe6b8b0" SRC_URI[jdk.sha256sum] = "8627e3e19ac6cfd250e435be659fbfdf65f3cb2c6c9678c9e5ec0db2ae1fcc90" Otherwise you should retry the download and/or check with upstream to determine if the file has become corrupted or otherwise unexpectedly modified. It said the checksum mismatch, but I did not modify the recipe file and archive file. I just download the recipe file and try to build it. Cound anyone tell me what is wrong I have done? or how to modify this. By the way, if I modify the recipe file with the new md5sum code, the build will fail at the unpack phase and get the "Data integrity error". Best Regards, Fan Xin -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [PATCH] openjdk: correct the typo mistake
Signed-off-by: Fan Xin --- recipes-core/openjdk/openjdk-8-common.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recipes-core/openjdk/openjdk-8-common.inc b/recipes-core/openjdk/openjdk-8-common.inc index def779d..4c45e36 100644 --- a/recipes-core/openjdk/openjdk-8-common.inc +++ b/recipes-core/openjdk/openjdk-8-common.inc @@ -1,5 +1,5 @@ DESCRIPTION = "Java runtime based upon the OpenJDK Project" -HOMEPAGE = "http://http://openjdk.java.net/"; +HOMEPAGE = "http://openjdk.java.net/"; LICENSE = "GPL-2.0-with-classpath-exception" LIC_FILES_CHKSUM = "file://LICENSE;md5=7b4baeedfe2d40cb03536573bc2c89b1" -- 2.7.4 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
