[oe] [meta-qt5][PATCH] qt5: use correct HostPrefix

2017-11-09 Thread Samuli Piippo 
Different HostPrefix was used when building Qt and in external
SDK's qt.conf. This caused e.g., wrong path in qmodule.pri for
PKG_CONFIG_EXECUTABLE.

Task-number: QTBUG-63097
Signed-off-by: Samuli Piippo 
---
 classes/qmake5_base.bbclass  | 2 +-
 recipes-qt/qt5/qtbase_git.bb | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/classes/qmake5_base.bbclass b/classes/qmake5_base.bbclass
index 29e8cff..3bc1279 100644
--- a/classes/qmake5_base.bbclass
+++ b/classes/qmake5_base.bbclass
@@ -86,7 +86,7 @@ generate_qt_config_file_effective_paths() {
 [EffectivePaths]
 HostBinaries = ${OE_QMAKE_PATH_EXTERNAL_HOST_BINS}
 HostData = ${OE_QMAKE_PATH_HOST_DATA}
-HostPrefix = ${STAGING_DIR_NATIVE}${prefix_native}
+HostPrefix = ${STAGING_DIR_NATIVE}
 EOF
 }
 #
diff --git a/recipes-qt/qt5/qtbase_git.bb b/recipes-qt/qt5/qtbase_git.bb
index 3ac6b21..802da3b 100644
--- a/recipes-qt/qt5/qtbase_git.bb
+++ b/recipes-qt/qt5/qtbase_git.bb
@@ -214,7 +214,7 @@ do_install_append() {
 touch ${D}/${OE_QMAKE_PATH_QT_ARCHDATA}/mkspecs/oe-device-extra.pri
 
 # Replace host paths with qmake built-in properties
-sed -i -e 
's|${STAGING_DIR_NATIVE}${prefix_native}|$$[QT_HOST_PREFIX/get]|g' \
+sed -i -e 's|${STAGING_DIR_NATIVE}|$$[QT_HOST_PREFIX/get]|g' \
 -e 's|${STAGING_DIR_HOST}|$$[QT_SYSROOT]|g' \
 ${D}/${OE_QMAKE_PATH_QT_ARCHDATA}/mkspecs/*.pri
 
-- 
2.7.4

-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Re: [oe] [OE-core] State of bitbake world, Failed tasks 2017-10-31

2017-11-09 Thread akuster808 


On 11/01/2017 08:30 AM, Khem Raj wrote:
> Hi Martin/Armin
>
> I looked at the first report with musl from Martin. Most of the
> failures are familiar except 2 I think which I plan to look at. I
> haven't blacklisted them intentionally, to get annoyed enough to keep
> fixing them as time permits.
> infact none of the build failures are due to musl limitation. So we
> need to fix the applications to behave. We can use "musl:" token in
> blacklist message so, if we need to fix one of these recipes them we
> know what to look for
> to find not yet ported recipes.
thanks. I going to grab the netkit packages.

- armin
> On Wed, Nov 1, 2017 at 2:59 AM, Martin Jansa  wrote:
>> Hi Armin,
>>
>> I'll leave this question to Khem, this was my just 2nd build with musl, Khem
>> is doing musl builds for very long time and fixing all the issue he finds,
>> maybe some of the issues detected in world builds already have fixes in
>> Khem's queue.
>>
>> Regards,
>>
>> On Wed, Nov 1, 2017 at 5:53 AM, akuster808  wrote:
>>> Martin,
>>>
>>>
>>> On 10/31/2017 01:58 PM, Martin Jansa wrote:
>>>
>>> With 2 pending patches from Khem to build systemd with musl:
>>>
>>> 62c7c98 systemd: Fix build on musl
>>> de68252 systemd: Fix build with musl/mips64
>>>
>>> the qemux86+musl build was able to progress much further and fewer ERROR
>>> messages were shown. Basically only uim recipe now depends on glibc and
>>> fails to be included in build queue:
>>>
>>>
>>> Are we going to blacklist the recipes failing via musl? is there
>>> blacklisting by TCLIB?
>>>
>>> - armin
>>>
>>> Summary: There were 55 ERROR messages shown, returning a non-zero exit
>>> code.
>>>
>>> Parsing of 2356 .bb files complete (2355 cached, 1 parsed). 3228 targets,
>>> 48 skipped, 0 masked, 0 errors.
>>> NOTE: Resolving any missing task queue dependencies
>>> ERROR: Nothing RPROVIDES 'glibc-gconv-euc-jp' (but
>>> /home/jenkins/oe/world/shr-core/meta-openembedded/meta-oe/recipes-support/uim/uim_1.8.6.bb
>>> RDEPENDS on or otherwise requires it)
>>> NOTE: Runtime target 'glibc-gconv-euc-jp' is unbuildable, removing...
>>> Missing or unbuildable dependency chain was: ['glibc-gconv-euc-jp']
>>> NOTE: Runtime target 'uim-dev' is unbuildable, removing...
>>> Missing or unbuildable dependency chain was: ['uim-dev',
>>> 'glibc-gconv-euc-jp']
>>> NOTE: Runtime target 'uim' is unbuildable, removing...
>>> Missing or unbuildable dependency chain was: ['uim', 'glibc-gconv-euc-jp']
>>> NOTE: Runtime target 'libuim0' is unbuildable, removing...
>>> Missing or unbuildable dependency chain was: ['libuim0',
>>> 'glibc-gconv-euc-jp']
>>> ERROR: Nothing RPROVIDES 'glibc-utils' (but
>>> /home/jenkins/oe/world/shr-core/meta-openembedded/meta-oe/recipes-support/uim/uim_1.8.6.bb
>>> RDEPENDS on or otherwise requires it)
>>> NOTE: Runtime target 'glibc-utils' is unbuildable, removing...
>>> Missing or unbuildable dependency chain was: ['glibc-utils']
>>>
>>> Some logs weren't uploaded to the http://logs.nslu2-linux.org/buildlogs
>>> because it run out of disk space again.
>>>
>>> http://www.openembedded.org/wiki/Bitbake_World_Status
>>>
>>> == Number of issues - stats ==
>>> {| class='wikitable'
>>> !|Date   !!colspan='4'|Failed tasks 
>>> !!|Signatures   
>>> !!colspan='15'|QA !!Comment
>>> |-
>>> ||  ||qemuarm   ||qemuarm64 ||qemux86   ||qemux86_64
>>> ||all
>>> ||already-stripped  ||libdir||textrel   ||build-deps
>>> ||file-rdeps||version-going-backwards   ||host-user-contaminated
>>> ||installed-vs-shipped  ||unknown-configure-option  
>>> ||symlink-to-sysroot||invalid-pkgconfig ||pkgname   ||ldflags   
>>> ||compile-host-path ||qa_pseudo ||  
>>> |-
>>>
>>>
>>> ||2017-10-30||2 ||6 ||26||1 ||0 ||0 
>>> ||0 ||1 ||0 ||0 ||28
>>> ||2 ||0 ||0 ||0 ||0 
>>> ||0 ||0 ||0 ||158   ||  
>>> 
>>> |}
>>>
>>> == Failed tasks 2017-10-30 ==
>>>
>>> INFO: jenkins-job.sh-1.8.39 Complete log available at
>>> http://logs.nslu2-linux.org/buildlogs/oe/world/rocko/log.report.20171031_095148.log
>>>
>>> === common (0) ===
>>>
>>> === common-x86 (0) ===
>>>
>>> === qemuarm (2) ===
>>> *
>>> meta-openembedded/meta-oe/recipes-devtools/android-tools/android-tools_5.1.1.r37.bb:do_compile
>>> *
>>> openembedded-core/meta/recipes-core/glibc/glibc-locale_2.26.bb:do_package_qa
>>>
>>> === qemuarm64 (5) ===
>>> *
>>> meta-browser/recipes-browser/chromium/chromium_54.0.2810.2.bb:do_compile
>>> *
>>> meta-browser/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb:do_compile
>>> *
>>> meta-openembedded/meta-initramfs/recipes-devtools/mtd/ubi-utils-klibc_1.5.2.bb:do_install
>>> *
>>>

Re: [oe] [meta-oe][morty][PATCH] mariadb: Do not use ucontext_* APIs with musl

2017-11-09 Thread Andre McCurdy 
On Wed, Oct 4, 2017 at 11:51 AM, Andre McCurdy  wrote:
> From: Khem Raj 
>
> musl has ucontext.h header but does not implement the APIs

Ping. CCing Armin.

> Signed-off-by: Khem Raj 
> (cherry picked from commit b545c0643d2b2a1f1a816e789ff67116c613de5b)
> Signed-off-by: Andre McCurdy 
> ---
>  meta-oe/recipes-support/mysql/mariadb.inc  |  1 +
>  .../mariadb/0001-disable-ucontext-on-musl.patch| 28 
> ++
>  2 files changed, 29 insertions(+)
>  create mode 100644 
> meta-oe/recipes-support/mysql/mariadb/0001-disable-ucontext-on-musl.patch
>
> diff --git a/meta-oe/recipes-support/mysql/mariadb.inc 
> b/meta-oe/recipes-support/mysql/mariadb.inc
> index 689b8ab..f3eb4c7 100644
> --- a/meta-oe/recipes-support/mysql/mariadb.inc
> +++ b/meta-oe/recipes-support/mysql/mariadb.inc
> @@ -16,6 +16,7 @@ SRC_URI = 
> "http://downloads.mariadb.com/MariaDB/mariadb-${PV}/source/mariadb-${P
> file://configure.cmake-fix-valgrind.patch \
> file://fix-a-building-failure.patch \
> file://change-cc-to-cc-version.patch \
> +   file://0001-disable-ucontext-on-musl.patch \
>"
>  SRC_URI[md5sum] = "fca86f1eaed2163b4bdce4f98f472324"
>  SRC_URI[sha256sum] = 
> "e142f9459507b97c5848042863b313ce70750118446bb4e35e5c07fe66007293"
> diff --git 
> a/meta-oe/recipes-support/mysql/mariadb/0001-disable-ucontext-on-musl.patch 
> b/meta-oe/recipes-support/mysql/mariadb/0001-disable-ucontext-on-musl.patch
> new file mode 100644
> index 000..60e9199
> --- /dev/null
> +++ 
> b/meta-oe/recipes-support/mysql/mariadb/0001-disable-ucontext-on-musl.patch
> @@ -0,0 +1,28 @@
> +From 5bc3e7ef9700d12054e0125a126f1bb093f01ef9 Mon Sep 17 00:00:00 2001
> +From: Khem Raj 
> +Date: Sun, 26 Mar 2017 14:30:33 -0700
> +Subject: [PATCH] disable ucontext on musl
> +
> +musl does not have *contex() APIs even though it has ucontext.h header
> +
> +Signed-off-by: Khem Raj 
> +---
> + include/my_context.h | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +diff --git a/include/my_context.h b/include/my_context.h
> +index dd44103..9b28c17 100644
> +--- a/include/my_context.h
>  b/include/my_context.h
> +@@ -31,7 +31,7 @@
> + #define MY_CONTEXT_USE_X86_64_GCC_ASM
> + #elif defined(__GNUC__) && __GNUC__ >= 3 && defined(__i386__)
> + #define MY_CONTEXT_USE_I386_GCC_ASM
> +-#elif defined(HAVE_UCONTEXT_H)
> ++#elif defined(__GLIBC__) && defined(HAVE_UCONTEXT_H)
> + #define MY_CONTEXT_USE_UCONTEXT
> + #else
> + #define MY_CONTEXT_DISABLE
> +--
> +2.12.1
> +
> --
> 1.9.1
>
-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Re: [oe] [meta-oe][PATCH 3/3] php: add libgcc to the runtime depends

2017-11-09 Thread Andre McCurdy 
On Mon, Oct 30, 2017 at 6:31 PM, Andre McCurdy  wrote:
> On Wed, Sep 20, 2017 at 8:11 AM, Derek Straka  wrote:
>> Avoids issues with 'libgcc_s.so.1 must be installed for pthread_cancel to 
>> work'
>
> Does passing the "--enable-libgcc" php configure option fix that too?
> If so, maybe it's a better fix?

To answer my own question, configuring with --enable-libgcc doesn't work.

The php configure script detects the path to libgcc by running "gcc
--print-libgcc-file-name" which doesn't work when cross compiling (or
when building natively if ${CC} is set to something other than gcc).

>> Signed-off-by: Derek Straka 
>> ---
>>  meta-oe/recipes-devtools/php/php.inc | 1 +
>>  1 file changed, 1 insertion(+)
>>
>> diff --git a/meta-oe/recipes-devtools/php/php.inc 
>> b/meta-oe/recipes-devtools/php/php.inc
>> index 0e55020..283d630 100644
>> --- a/meta-oe/recipes-devtools/php/php.inc
>> +++ b/meta-oe/recipes-devtools/php/php.inc
>> @@ -203,6 +203,7 @@ MODPHP_PACKAGE = "${@bb.utils.contains('PACKAGECONFIG', 
>> 'apache2', '${PN}-modphp
>>
>>  PACKAGES = "${PN}-dbg ${PN}-cli ${PN}-cgi ${PN}-fpm ${PN}-fpm-apache2 
>> ${PN}-pear ${PN}-phar ${MODPHP_PACKAGE} ${PN}-dev ${PN}-staticdev ${PN}-doc 
>> ${PN}"
>>
>> +RDEPENDS_${PN} += "libgcc"
>>  RDEPENDS_${PN}-pear = "${PN}"
>>  RDEPENDS_${PN}-phar = "${PN}-cli"
>>  RDEPENDS_${PN}-cli = "${PN}"
>> --
>> 2.7.4
-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Re: [oe] [yocto] [Openembedded-architecture] [RFC] stable branch naming scheme

2017-11-09 Thread akuster808 
Any more comments?


I started to use stable/{branch}-next in all the contrib repos. Poky
will be constructed from oe-contrib repos.


thanks for all the feedback.

regards,

Armin


On 11/06/2017 10:14 AM, akuster808 wrote:
>
>
>
> On 11/06/2017 08:43 AM, Denys Dmytriyenko wrote:
>> On Fri, Nov 03, 2017 at 09:20:43AM -0700, akuster808 wrote:
>>> Hello,
>>>
>>> The problem I hope to solve is that a Maintainer can stage changes in
>>> any branch in the contrib repos making it difficult for folks to track
>>> their back port requests. The also makes it harder to automate any kind
>>> of build automation.
>>>
>>> I would like to propose a contrib naming scheme for the stable release
>>> branches. I am thinking of the following:
>>>
>>> stable/{version}-next or {special char}_stable/{version}-next.
>>>
>>>    "version" is either the code name or numeric like in bitbake.
>>>
>>>    "special char" would be used to have these branches at the top of th
>>> list, if we wont that.
>> I like this branch unification!
>>
>> I know we discussed this at OEDEM and there was some convenience reason 
>> given, 
>> but can we also standardize on the tree? I.e. openembedded-core-contrib vs. 
>> poky-contrib?
>
> The current Poky maintenance process talks about deconstructing
> "stable-next":
> https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance#Stable_branch_maintainers
>  
> # Split out any bitbake changes and send them to the bitbake-devel
> mailing list (marking them with the appropriate stable version in the
> subject line e.g. [1.20])
> # Split out OE-Core changes and create an openembedded-core-contrib
> branch containing them; send the cover letter only (marking it as such
> in the subject) to the openembedded-core mailing list.
> The above has been happening via  a script Richard runs.  I personally
> think it the workflow should be for OE -> Yocto. This does add more
> work for the maintainer but is cleaner.  I did ask Richard to create
> bitbake-contrib for this purpose but am lazy as he uses his script ; )
>
> The reason I choose "stable/" branching is that the "-next" branches
> are out of sync and not being used correctly or not defined on their
> purpose. another subject for another time.
>
> - armin
>
>>> We can apply this to all OE / Yocto repos that have stable branch
>>> maintenance process.
>>>
>>> If we standardize on a naming scheme, We can then document this so
>>> contributers can monitor their requests more easily. The community can
>>> see what changes are being backport.  This will enable the possibility
>>> to automate builds, etc. 
>>>
>>> let me know what you think.
>>>
>>> Kind regards,
>>>
>>> Armin
>>>
>>>
>>>
>>> ___
>>> Openembedded-architecture mailing list
>>> openembedded-architect...@lists.openembedded.org
>>> http://lists.openembedded.org/mailman/listinfo/openembedded-architecture
>

-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Re: [oe] [meta-browser] CFT: Chromium 62 in meta-browser

2017-11-09 Thread Raphael Kubo da Costa 
Hey Otavio, thanks for the quick response!

Otavio Salvador  writes:
> Hello Raphael,
>
>> I'd like people to look at my commits and let me know if there's any big
>> issue that would prevent those changes from landing into meta-browser.
>> If everything's OK, I'd then start sending the patches to the list (or
>> pull requests on GitHub, whichever is preferred).
>
> I went through all the commits, one by one. There are few that might
> need minor adjustments (as for example the removal of cups support
> which should be moved to a PACKAGECONFIG) but in general, they are all
> good. You did a great job making it very granular and well documented
> :-)
>
> I think this is huge enough that using a pull request so we can track
> comments and progress makes sense. Do you mind creating one?
>
> I think we will end picking individual commits on the beginning to
> reduce the delta and keep going until we have the bump done. Do you
> think it is a good way to handle this?

I think that works, and it matches what I originally had in mind:
* Get people to look at the existing commits and raise any objections to
  any major "architectural" issues with the changes.
* Once everyone's on the same page, start sending patches in chunks
  (e.g. all dependency changes in one pull request).
* Once the clean-ups and bug fixes are in, send the big PRs (move to GN
  and update to M62).

I'll start splitting that branch into smaller ones for PRs, but I'll
also wait a little bit for others (such as Jacobo, Trevor and Khem) to
chime in as well.

The only bummer is that I'll be on holidays from 17th November to 8th
December so it may take a little longer than usual for me to get all the
changes landed.
-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Re: [oe] [meta-browser] CFT: Chromium 62 in meta-browser

2017-11-09 Thread Otavio Salvador 
Hello Raphael,

On Thu, Nov 9, 2017 at 2:28 PM, Raphael Kubo da Costa
 wrote:
> Like I said back in September, I'd like to merge the Chromium recipe
> I've been maintaining independently [1] since last year into the
> meta-browser layer so that more people can both benefit from it as well
> as help maintain it. Currently, the meta-browser recipe is still
> tracking Chromium 54 and ozone-wayland with Chromium 53, whereas my
> recipe tracks the latest stable releases (it's currently at
> 62.0.3202.89).

First, I'd like to thank you for all this amazing work. Chromium is
indeed a giant project and its proper integration has some specific
challenges by itself...

...
> I'd like people to look at my commits and let me know if there's any big
> issue that would prevent those changes from landing into meta-browser.
> If everything's OK, I'd then start sending the patches to the list (or
> pull requests on GitHub, whichever is preferred).

I went through all the commits, one by one. There are few that might
need minor adjustments (as for example the removal of cups support
which should be moved to a PACKAGECONFIG) but in general, they are all
good. You did a great job making it very granular and well documented
:-)

I think this is huge enough that using a pull request so we can track
comments and progress makes sense. Do you mind creating one?

I think we will end picking individual commits on the beginning to
reduce the delta and keep going until we have the bump done. Do you
think it is a good way to handle this?

-- 
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

[oe] [meta-browser] CFT: Chromium 62 in meta-browser

2017-11-09 Thread Raphael Kubo da Costa 
Hi everyone,

Like I said back in September, I'd like to merge the Chromium recipe
I've been maintaining independently [1] since last year into the
meta-browser layer so that more people can both benefit from it as well
as help maintain it. Currently, the meta-browser recipe is still
tracking Chromium 54 and ozone-wayland with Chromium 53, whereas my
recipe tracks the latest stable releases (it's currently at
62.0.3202.89).

[1] https://github.com/rakuco/meta-crosswalk

I don't want to just copy-paste my recipe into meta-browser in one giant
commit and call it a day though, so in parallel to maintaining my recipe
I've been working on "organically" turning the meta-browser recipe into
something that looks more similar to mine (while also landing a few bug
fixes into my recipe after looking at the meta-browser one). This way,
people can still track the commit history and know why each change was
done the way it was.

I believe this has finally reached a stage where it's ready for public
consumption, hence the CFT:

https://github.com/rakuco/meta-browser/tree/chromium62

I'd like people to look at my commits and let me know if there's any big
issue that would prevent those changes from landing into meta-browser.
If everything's OK, I'd then start sending the patches to the list (or
pull requests on GitHub, whichever is preferred).

There are 60 new commits in my "chromium62" branch; the majority of them
are clean-ups, bug fixes and adjustments to the recipe. In fact, the
actual update from Chromium 54 to Chromium 62 only happens in the 58th
commit, and the biggest change is actually the move to GN (which I've
done separately and before the Chromium 62 update commit). Compared to
my meta-crosswalk Chromium recipe, the existing changes are mostly just
cosmetic (some variables are defined in different locations, the
available PACKAGECONFIG options are different etc), so it's been tested
on Yocto morty and rocko with GCC 5, 6 and 7.

Possibly controversial issues:
- The ozone-wayland recipe has been removed (this is actually commit
  #1). The ozone-wayland project Intel used to maintain has not been
  maintained in a very long time, and it is impossible to just get it to
  work with Chromium 62. I'd also rather not keep Chromium 53 around
  just because of it due to A) increased maintenance costs 2) we'd be
  shipping an ancient Chromium release with tons of security issues.

- musl support is currently broken. I've sent a few patches upstream
  lately and added a few musl-related changes to the Chromium 62 recipe,
  but getting the code to build requires a lot of time and
  determination, and if we don't have someone actively working with
  upstream it's just going to be an uphill battle that I am not willing
  to take upon myself.

- The 'ignore-lost-context' PACKAGECONFIG knob was removed. The patch
  it required no longer applies cleanly, its context refers a 5-year-old
  discussion and it is not clear if it is still necessary at all.

- It is no longer possible to run Chromium as root. Upstream has done
  some work on this front, and now really requires --no-sandbox to be
  passed on the command line for Chromium to run as root. I'd rather not
  swim against the current here.

- In the future, I'd like to revisit the other PACKAGECONFIG knobs as
  well. In particular, it is not clear to me if 'impl-side-painting' and
  'use-egl' are still needed at all, and I'd like to drop
  'component-build' to simplify the recipe and prevent anyone from using
  this option in production.
-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Re: [oe] [OE-core] State of bitbake world, Failed tasks 2017-11-07

2017-11-09 Thread Martin Jansa 
FYI: You can use PV = "2.0.99+2.1.0-beta3" to make sure that it's sorted
higher than any 2.0.* release and that final 2.1.0 again sorts higher than
this beta3 without PE bump.

On Thu, Nov 9, 2017 at 4:23 PM, akuster808  wrote:

>
>
> On 11/08/2017 11:05 AM, Martin Jansa wrote:
>
> The only change from previous report is slightly newer oe-core and bitbake.
>
> http://www.openembedded.org/wiki/Bitbake_World_Status
>
> == Number of issues - stats ==
> {| class='wikitable'
> !|Date !!colspan='4'|Failed tasks 
> !!|Signatures !!colspan='15'|QA !!Comment
> |-
> ||||qemuarm   ||qemuarm64 ||qemux86   ||qemux86_64
> ||all   ||already-stripped  ||libdir||textrel   ||build-deps  
>   ||file-rdeps||version-going-backwards   ||host-user-contaminated
> ||installed-vs-shipped  ||unknown-configure-option  
> ||symlink-to-sysroot||invalid-pkgconfig ||pkgname   ||ldflags 
>   ||compile-host-path ||qa_pseudo ||  
> |-
> ||2017-11-07  ||3 ||6 ||28||2 ||0 ||0 ||0 
> ||1 ||0 ||0 ||0 ||1   
>   ||0 ||0 ||0 ||0 ||0 
> ||0 ||0 ||365   ||  
> |}
>
> == Failed tasks 2017-11-07 ==
>
> INFO: jenkins-job.sh-1.8.39 Complete log available at 
> http://logs.nslu2-linux.org/buildlogs/oe/world/rocko/log.report.20171108_081616.log
>
> === common (1) ===
> * 
> meta-openembedded/meta-oe/recipes-support/freerdp/freerdp_git.bb:do_configure
>
> === common-x86 (0) ===
>
> === qemuarm (2) ===
> * 
> meta-openembedded/meta-oe/recipes-devtools/android-tools/android-tools_5.1.1.r37.bb:do_compile
> * meta-qt5/recipes-qt/qt5/qtbase_git.bb:do_package_qa
>
> === qemuarm64 (5) ===
> * meta-browser/recipes-browser/chromium/chromium_54.0.2810.2.bb:do_compile
> * 
> meta-browser/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb:do_compile
> * 
> meta-openembedded/meta-initramfs/recipes-devtools/mtd/ubi-utils-klibc_1.5.2.bb:do_install
> * 
> meta-openembedded/meta-initramfs/recipes-kernel/kexec/kexec-tools-klibc_2.0.2.bb:do_configure
>
>
> * 
> meta-openembedded/meta-oe/recipes-devtools/luajit/luajit_2.0.5.bb:do_compile
>
>
> The Arm64 fix  should be in the 2.1.0 when it releases. The fix is in
> LuaJIT-2.1.0-beta3.  I didn't want to backport (beta) it as it may trigger
> the need for PE when 2.1.0 officially releases.
>
>
>
>
> === qemux86 (27) ===
>
>
> * meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb:do_compile
> * 
> meta-openembedded/meta-networking/recipes-connectivity/rdist/rdist_6.1.5.bb:do_package
> * 
> meta-openembedded/meta-networking/recipes-daemons/opensaf/opensaf_5.17.07.bb:do_compile
> * 
> meta-openembedded/meta-networking/recipes-daemons/vsftpd/vsftpd_3.0.3.bb:do_compile
> * 
> meta-openembedded/meta-networking/recipes-netkit/netkit-rsh/netkit-rsh_0.17.bb:do_compile
> * 
> meta-openembedded/meta-networking/recipes-netkit/netkit-rusers/netkit-rusers_0.17.bb:do_compile
> * 
> meta-openembedded/meta-networking/recipes-netkit/netkit-telnet/netkit-telnet_0.17.bb:do_configure
> * 
> meta-openembedded/meta-networking/recipes-protocols/mdns/mdns_765.50.9.bb:do_compile
> * 
> meta-openembedded/meta-networking/recipes-protocols/tsocks/tsocks_1.8beta5.bb:do_compile
> * 
> meta-openembedded/meta-networking/recipes-support/open-isns/open-isns_0.97.bb:do_compile
> * 
> meta-openembedded/meta-oe/recipes-benchmark/libhugetlbfs/libhugetlbfs_git.bb:do_compile
> * 
> meta-openembedded/meta-oe/recipes-connectivity/umip/umip_1.0.bb:do_compile
> * 
> meta-openembedded/meta-oe/recipes-connectivity/wvdial/wvdial_1.61.bb:do_compile
> * meta-openembedded/meta-oe/recipes-devtools/pm-qa/pm-qa_git.bb:do_compile
> * meta-openembedded/meta-oe/recipes-extended/mraa/mraa_git.bb:do_compile
> * 
> meta-openembedded/meta-oe/recipes-extended/tiptop/tiptop_2.3.bb:do_compile
> * meta-openembedded/meta-oe/recipes-kernel/crash/crash_7.1.9.bb:do_compile
> * 
> meta-openembedded/meta-oe/recipes-kernel/minicoredumper/minicoredumper_2.0.0.bb:do_compile
> * 
> meta-openembedded/meta-oe/recipes-multimedia/alsa/alsa-oss_1.0.17.bb:do_compile
> * 
> meta-openembedded/meta-python/recipes-devtools/python/python3-systemd_234.bb:do_compile
> * 
> meta-openembedded/meta-python/recipes-devtools/python/python-systemd_234.bb:do_compile
> * meta-qt5/recipes-qt/qt5/qtlocation_git.bb:do_compile
> * 
> openembedded-core/meta/recipes-devtools/systemd-bootchart/systemd-bootchart_231.bb:do_compile
> * 
> openembedded-core/meta/recipes-graphics/cogl/cogl-1.0_1.22.2.bb:do_compile
> * 
> openembedded-core/meta/recipes-graphics/virglrenderer/virglrenderer_git.bb:do_compile
> * 
>

Re: [oe] [OE-core] State of bitbake world, Failed tasks 2017-11-07

2017-11-09 Thread akuster808 


On 11/08/2017 11:05 AM, Martin Jansa wrote:
> The only change from previous report is slightly newer oe-core and bitbake.
> http://www.openembedded.org/wiki/Bitbake_World_Status
>
> == Number of issues - stats ==
> {| class='wikitable'
> !|Date !!colspan='4'|Failed tasks 
> !!|Signatures !!colspan='15'|QA !!Comment
> |-
> ||||qemuarm   ||qemuarm64 ||qemux86   ||qemux86_64
> ||all   ||already-stripped  ||libdir||textrel   ||build-deps  
>   ||file-rdeps||version-going-backwards   ||host-user-contaminated
> ||installed-vs-shipped  ||unknown-configure-option  
> ||symlink-to-sysroot||invalid-pkgconfig ||pkgname   ||ldflags 
>   ||compile-host-path ||qa_pseudo ||  
> |-
> ||2017-11-07  ||3 ||6 ||28||2 ||0 ||0 ||0 
> ||1 ||0 ||0 ||0 ||1   
>   ||0 ||0 ||0 ||0 ||0 
> ||0 ||0 ||365   ||  
> |}
>
> == Failed tasks 2017-11-07 ==
>
> INFO: jenkins-job.sh-1.8.39 Complete log available at 
> http://logs.nslu2-linux.org/buildlogs/oe/world/rocko/log.report.20171108_081616.log
>
> === common (1) ===
> * 
> meta-openembedded/meta-oe/recipes-support/freerdp/freerdp_git.bb:do_configure
>
> === common-x86 (0) ===
>
> === qemuarm (2) ===
> * 
> meta-openembedded/meta-oe/recipes-devtools/android-tools/android-tools_5.1.1.r37.bb:do_compile
> * meta-qt5/recipes-qt/qt5/qtbase_git.bb:do_package_qa
>
> === qemuarm64 (5) ===
> * meta-browser/recipes-browser/chromium/chromium_54.0.2810.2.bb:do_compile
> * 
> meta-browser/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb:do_compile
> * 
> meta-openembedded/meta-initramfs/recipes-devtools/mtd/ubi-utils-klibc_1.5.2.bb:do_install
> * 
> meta-openembedded/meta-initramfs/recipes-kernel/kexec/kexec-tools-klibc_2.0.2.bb:do_configure

> * 
> meta-openembedded/meta-oe/recipes-devtools/luajit/luajit_2.0.5.bb:do_compile

The Arm64 fix  should be in the 2.1.0 when it releases. The fix is in
LuaJIT-2.1.0-beta3.  I didn't want to backport (beta) it as it may
trigger the need for PE when 2.1.0 officially releases.


>
> === qemux86 (27) ===

> * meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb:do_compile
> * 
> meta-openembedded/meta-networking/recipes-connectivity/rdist/rdist_6.1.5.bb:do_package
> * 
> meta-openembedded/meta-networking/recipes-daemons/opensaf/opensaf_5.17.07.bb:do_compile
> * 
> meta-openembedded/meta-networking/recipes-daemons/vsftpd/vsftpd_3.0.3.bb:do_compile
> * 
> meta-openembedded/meta-networking/recipes-netkit/netkit-rsh/netkit-rsh_0.17.bb:do_compile
> * 
> meta-openembedded/meta-networking/recipes-netkit/netkit-rusers/netkit-rusers_0.17.bb:do_compile
> * 
> meta-openembedded/meta-networking/recipes-netkit/netkit-telnet/netkit-telnet_0.17.bb:do_configure
> * 
> meta-openembedded/meta-networking/recipes-protocols/mdns/mdns_765.50.9.bb:do_compile
> * 
> meta-openembedded/meta-networking/recipes-protocols/tsocks/tsocks_1.8beta5.bb:do_compile
> * 
> meta-openembedded/meta-networking/recipes-support/open-isns/open-isns_0.97.bb:do_compile
> * 
> meta-openembedded/meta-oe/recipes-benchmark/libhugetlbfs/libhugetlbfs_git.bb:do_compile
> * 
> meta-openembedded/meta-oe/recipes-connectivity/umip/umip_1.0.bb:do_compile
> * 
> meta-openembedded/meta-oe/recipes-connectivity/wvdial/wvdial_1.61.bb:do_compile
> * meta-openembedded/meta-oe/recipes-devtools/pm-qa/pm-qa_git.bb:do_compile
> * meta-openembedded/meta-oe/recipes-extended/mraa/mraa_git.bb:do_compile
> * 
> meta-openembedded/meta-oe/recipes-extended/tiptop/tiptop_2.3.bb:do_compile
> * meta-openembedded/meta-oe/recipes-kernel/crash/crash_7.1.9.bb:do_compile
> * 
> meta-openembedded/meta-oe/recipes-kernel/minicoredumper/minicoredumper_2.0.0.bb:do_compile
> * 
> meta-openembedded/meta-oe/recipes-multimedia/alsa/alsa-oss_1.0.17.bb:do_compile
> * 
> meta-openembedded/meta-python/recipes-devtools/python/python3-systemd_234.bb:do_compile
> * 
> meta-openembedded/meta-python/recipes-devtools/python/python-systemd_234.bb:do_compile
> * meta-qt5/recipes-qt/qt5/qtlocation_git.bb:do_compile
> * 
> openembedded-core/meta/recipes-devtools/systemd-bootchart/systemd-bootchart_231.bb:do_compile
> * 
> openembedded-core/meta/recipes-graphics/cogl/cogl-1.0_1.22.2.bb:do_compile
> * 
> openembedded-core/meta/recipes-graphics/virglrenderer/virglrenderer_git.bb:do_compile
> * 
> openembedded-core/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.12.3.bb:do_compile
> * openembedded-core/meta/recipes-multimedia/x264/x264_git.bb:do_package_qa
>
> === qemux86_64 (1) ===
> * 
>

Re: [oe] [meta-oe][PATCH] mercurial: Upgrade to 4.4.1

2017-11-09 Thread Paul Barker 
On Thu, Nov 9, 2017 at 6:20 AM, Zhixiong Chi  wrote:
> * Upgrade to the latest release to fix some CVEs:
>  - CVE-2017-1000115: missing symlink check that can malicious repositories
>  to modify files outside the repository
>  - CVE-2017-1000116: did not adequately sanitize hostnames passed to ssh,
>  leading to possible shell-injection attacks.
>
> * For other changes please see: https://www.mercurial-scm.org/wiki/WhatsNew
>
> * Update SRC_URI with the new download link
>
> Signed-off-by: Zhixiong Chi 

I sent a similar patch a few days ago which is already staged here:
http://git.openembedded.org/meta-openembedded-contrib/log/?h=jansa/master

Thanks,

-- 
Paul Barker
Togán Labs Ltd
-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

[oe] [meta-networking][PATCH 2/3] iscsi-initiator-utils: remove the distro_features_check

2017-11-09 Thread jackie.huang 
From: Jackie Huang 

open-isns supports both systemd and sysvinit now, so
remove the distro_features_check.

Signed-off-by: Jackie Huang 
---
 .../iscsi-initiator-utils/iscsi-initiator-utils_2.0.874.bb| 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git 
a/meta-networking/recipes-daemons/iscsi-initiator-utils/iscsi-initiator-utils_2.0.874.bb
 
b/meta-networking/recipes-daemons/iscsi-initiator-utils/iscsi-initiator-utils_2.0.874.bb
index 16ac19992..50aadb6b6 100644
--- 
a/meta-networking/recipes-daemons/iscsi-initiator-utils/iscsi-initiator-utils_2.0.874.bb
+++ 
b/meta-networking/recipes-daemons/iscsi-initiator-utils/iscsi-initiator-utils_2.0.874.bb
@@ -27,9 +27,7 @@ SRC_URI = "git://github.com/open-iscsi/open-iscsi \
 S = "${WORKDIR}/git"
 B = "${WORKDIR}/build"
 
-inherit update-rc.d systemd autotools distro_features_check
-# open-isns depends on systemd
-REQUIRED_DISTRO_FEATURES = "systemd"
+inherit update-rc.d systemd autotools
 
 EXTRA_OECONF = " \
 --target=${TARGET_SYS} \
-- 
2.11.0

-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

[oe] [meta-networking][PATCH 3/3] iscsi-initiator-utils: check file existence before moving

2017-11-09 Thread jackie.huang 
From: Jackie Huang 

Check the file existence before moving to avoid the error:
| mv: cannot stat //git/utils/fwparam_ibft/prom_lex.l:
| No such file or directory

Signed-off-by: Jackie Huang 
---
 .../iscsi-initiator-utils/iscsi-initiator-utils_2.0.874.bb| 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git 
a/meta-networking/recipes-daemons/iscsi-initiator-utils/iscsi-initiator-utils_2.0.874.bb
 
b/meta-networking/recipes-daemons/iscsi-initiator-utils/iscsi-initiator-utils_2.0.874.bb
index 50aadb6b6..95848d0b3 100644
--- 
a/meta-networking/recipes-daemons/iscsi-initiator-utils/iscsi-initiator-utils_2.0.874.bb
+++ 
b/meta-networking/recipes-daemons/iscsi-initiator-utils/iscsi-initiator-utils_2.0.874.bb
@@ -57,7 +57,9 @@ do_configure () {
 
 do_compile () {
 # Make sure we DO NOT regenerate prom_lex.c.
-mv ${S}/utils/fwparam_ibft/prom_lex.l 
${S}/utils/fwparam_ibft/prom_lex.l.unused
+if [ -f ${S}/utils/fwparam_ibft/prom_lex.l ]; then
+mv ${S}/utils/fwparam_ibft/prom_lex.l 
${S}/utils/fwparam_ibft/prom_lex.l.unused
+fi
 oe_runmake -C ${S} ${EXTRA_OEMAKE} user
 }
 
-- 
2.11.0

-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

[oe] [meta-networking][PATCH 1/3] open-isns: add sysvinit support

2017-11-09 Thread jackie.huang 
From: Jackie Huang 

It's not mandatory to depend on systemd for open-isns,
the sysvinit script is also provided in open-isns source
code, so add it to support sysvinit and remove the
distro_features_check.

Signed-off-by: Jackie Huang 
---
 meta-networking/recipes-support/open-isns/open-isns_0.97.bb | 12 
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/meta-networking/recipes-support/open-isns/open-isns_0.97.bb 
b/meta-networking/recipes-support/open-isns/open-isns_0.97.bb
index 420ef5be0..9ee1f87c8 100644
--- a/meta-networking/recipes-support/open-isns/open-isns_0.97.bb
+++ b/meta-networking/recipes-support/open-isns/open-isns_0.97.bb
@@ -11,7 +11,7 @@ LICENSE = "GPLv2+ & LGPLv2+"
 LIC_FILES_CHKSUM = "file://COPYING;md5=321bf41f280cf805086dd5a720b37785"
 SECTION = "net"
 
-DEPENDS = "openssl systemd"
+DEPENDS = "openssl"
 
 SRC_URI = " \
 git://github.com/open-iscsi/open-isns \
@@ -21,9 +21,7 @@ SRCREV ?= "09954404e948e41eb0fce8e28836018b4ce3d20d"
 
 S = "${WORKDIR}/git"
 
-inherit systemd autotools-brokensep distro_features_check
-# depends on systemd
-REQUIRED_DISTRO_FEATURES = "systemd"
+inherit systemd autotools-brokensep update-rc.d
 
 EXTRA_OECONF = " --prefix=${prefix} --enable-shared"
 EXTRA_OEMAKE += "SYSTEMDDIR=${D}${systemd_unitdir}/system"
@@ -31,6 +29,12 @@ EXTRA_OEMAKE += "SYSTEMDDIR=${D}${systemd_unitdir}/system"
 do_install_append () {
 oe_runmake INCDIR=${D}${includedir}/libisns/ install_hdrs
 oe_runmake LIBDIR=${D}${libdir} install_lib
+
+install -D -m 755 ${S}/etc/openisns.init ${D}${sysconfdir}/init.d/openisns
+sed -i 's|daemon isnsd|start-stop-daemon --start --quiet --oknodo --exec 
${sbindir}/isnsd --|' \
+${D}${sysconfdir}/init.d/openisns
 }
 
 FILES_${PN} += "${libdir} ${systemd_unitdir}"
+
+INITSCRIPT_NAME = "openisns"
-- 
2.11.0

-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

[oe] [meta-networking][PATCH 0/3] iscsi-initiator-utils/open-isns: fix for sysvinit

2017-11-09 Thread jackie.huang 
From: Jackie Huang 

--
The following changes since commit 5d6d21e98ed594809169d2b2f6964e90a3369a96:

  libreport: fix Nothing RPROVIDES 'lib32-python3-libreport' (2017-10-27 
16:39:34 +)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib.git jhuang0/d_iscsi-openisns_171109_0
  http://git.pokylinux.org/cgit.cgi//log/?h=jhuang0/d_iscsi-openisns_171109_0

Jackie Huang (3):
  open-isns: add sysvinit support
  iscsi-initiator-utils: remove the distro_features_check
  iscsi-initiator-utils: check file existence before moving

 .../iscsi-initiator-utils/iscsi-initiator-utils_2.0.874.bb   |  8 
 meta-networking/recipes-support/open-isns/open-isns_0.97.bb  | 12 
 2 files changed, 12 insertions(+), 8 deletions(-)

-- 
2.11.0

-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Re: [oe] [OE-core] State of bitbake world, Failed tasks 2017-11-07

2017-11-09 Thread Andrea Adami 
On Thu, Nov 9, 2017 at 10:43 AM, Andrea Adami  wrote:
> On Wed, Nov 8, 2017 at 8:05 PM, Martin Jansa  wrote:
>> The only change from previous report is slightly newer oe-core and bitbake.
>>
>>
>> http://www.openembedded.org/wiki/Bitbake_World_Status
>>
>> == Number of issues - stats ==
>> {| class='wikitable'
>> !|Date !!colspan='4'|Failed tasks!!|Signatures
>> !!colspan='15'|QA !!Comment
>> |-
>> || ||qemuarm ||qemuarm64 ||qemux86 ||qemux86_64 ||all
>> ||already-stripped ||libdir ||textrel ||build-deps ||file-rdeps 
>> ||version-going-backwards ||host-user-contaminated ||installed-vs-shipped 
>> ||unknown-configure-option ||symlink-to-sysroot ||invalid-pkgconfig 
>> ||pkgname ||ldflags ||compile-host-path ||qa_pseudo ||
>> |-
>> ||2017-11-07 ||3 ||6 ||28 ||2 ||0 ||0 ||0 ||1 ||0 ||0 ||0 ||1 ||0 ||0 ||0 
>> ||0 ||0 ||0 ||0 ||365 ||
>> |}
>>
>> == Failed tasks 2017-11-07 ==
>>
>> INFO: jenkins-job.sh-1.8.39 Complete log available at
>> http://logs.nslu2-linux.org/buildlogs/oe/world/rocko/log.report.20171108_081616.log
>>
>> === common (1) ===
>> *
>> meta-openembedded/meta-oe/recipes-support/freerdp/freerdp_git.bb:do_configure
>>
>> === common-x86 (0) ===
>>
>> === qemuarm (2) ===
>> *
>> meta-openembedded/meta-oe/recipes-devtools/android-tools/android-tools_5.1.1.r37.bb:do_compile
>> * meta-qt5/recipes-qt/qt5/qtbase_git.bb:do_package_qa
>>
>> === qemuarm64 (5) ===
>> *
>> meta-browser/recipes-browser/chromium/chromium_54.0.2810.2.bb:do_compile
>> *
>> meta-browser/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb:do_compile
>> *
>> meta-openembedded/meta-initramfs/recipes-devtools/mtd/ubi-utils-klibc_1.5.2.bb:do_install
>
> I am wondering about this failure, specific for aarch64-oe-linux
>
>  error: '-mgeneral-regs-only' is incompatible with floating-point
>
> Klibc does not support floating point and -mgeneral-regs-only should
> "Prevents the use of floating-point instructions or floating-point registers."
>
> Khem, do you have an idea?
>
>
>> *
>> meta-openembedded/meta-initramfs/recipes-kernel/kexec/kexec-tools-klibc_2.0.2.bb:do_configure
>
>
> | configure: loading site script
> /home/jenkins/oe/world/shr-core/tmp-glibc/work/aarch64-oe-linux/kexec-tools-klibc/2.0.2-r1/recipe-sysroot/usr/share/aarch64-oe-linux_config_site.d/glibc_config
> | checking build system type... x86_64-pc-linux-gnu
> | checking host system type... aarch64-oe-linux-gnu
> | checking target system type... aarch64-oe-linux-gnu
> | configure: error: unsupported architecture aarch64
>
> I think there is something wrong because the main package kexec-tools
> seems not giving build errors on aarch64.
>

In fact for kexec-tools_2.0.14.bb there is a specific patch "Add arm64 support"

We will backport it.

> Cheers
> Andrea
>
>> *
>> meta-openembedded/meta-oe/recipes-devtools/luajit/luajit_2.0.5.bb:do_compile
>>
>> === qemux86 (27) ===
>> * meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb:do_compile
>> *
>> meta-openembedded/meta-networking/recipes-connectivity/rdist/rdist_6.1.5.bb:do_package
>> *
>> meta-openembedded/meta-networking/recipes-daemons/opensaf/opensaf_5.17.07.bb:do_compile
>> *
>> meta-openembedded/meta-networking/recipes-daemons/vsftpd/vsftpd_3.0.3.bb:do_compile
>> *
>> meta-openembedded/meta-networking/recipes-netkit/netkit-rsh/netkit-rsh_0.17.bb:do_compile
>> *
>> meta-openembedded/meta-networking/recipes-netkit/netkit-rusers/netkit-rusers_0.17.bb:do_compile
>> *
>> meta-openembedded/meta-networking/recipes-netkit/netkit-telnet/netkit-telnet_0.17.bb:do_configure
>> *
>> meta-openembedded/meta-networking/recipes-protocols/mdns/mdns_765.50.9.bb:do_compile
>> *
>> meta-openembedded/meta-networking/recipes-protocols/tsocks/tsocks_1.8beta5.bb:do_compile
>> *
>> meta-openembedded/meta-networking/recipes-support/open-isns/open-isns_0.97.bb:do_compile
>> *
>> meta-openembedded/meta-oe/recipes-benchmark/libhugetlbfs/libhugetlbfs_git.bb:do_compile
>> *
>> meta-openembedded/meta-oe/recipes-connectivity/umip/umip_1.0.bb:do_compile
>> *
>> meta-openembedded/meta-oe/recipes-connectivity/wvdial/wvdial_1.61.bb:do_compile
>> *
>> meta-openembedded/meta-oe/recipes-devtools/pm-qa/pm-qa_git.bb:do_compile
>> * meta-openembedded/meta-oe/recipes-extended/mraa/mraa_git.bb:do_compile
>> *
>> meta-openembedded/meta-oe/recipes-extended/tiptop/tiptop_2.3.bb:do_compile
>> *
>> meta-openembedded/meta-oe/recipes-kernel/crash/crash_7.1.9.bb:do_compile
>> *
>> meta-openembedded/meta-oe/recipes-kernel/minicoredumper/minicoredumper_2.0.0.bb:do_compile
>> *
>> meta-openembedded/meta-oe/recipes-multimedia/alsa/alsa-oss_1.0.17.bb:do_compile
>> *
>> meta-openembedded/meta-python/recipes-devtools/python/python3-systemd_234.bb:do_compile
>> *
>> meta-openembedded/meta-python/recipes-devtools/python/python-systemd_234.bb:do_compile
>> *

Re: [oe] [OE-core] State of bitbake world, Failed tasks 2017-11-07

2017-11-09 Thread Andrea Adami 
On Wed, Nov 8, 2017 at 8:05 PM, Martin Jansa  wrote:
> The only change from previous report is slightly newer oe-core and bitbake.
>
>
> http://www.openembedded.org/wiki/Bitbake_World_Status
>
> == Number of issues - stats ==
> {| class='wikitable'
> !|Date !!colspan='4'|Failed tasks!!|Signatures
> !!colspan='15'|QA !!Comment
> |-
> || ||qemuarm ||qemuarm64 ||qemux86 ||qemux86_64 ||all
> ||already-stripped ||libdir ||textrel ||build-deps ||file-rdeps 
> ||version-going-backwards ||host-user-contaminated ||installed-vs-shipped 
> ||unknown-configure-option ||symlink-to-sysroot ||invalid-pkgconfig ||pkgname 
> ||ldflags ||compile-host-path ||qa_pseudo ||
> |-
> ||2017-11-07 ||3 ||6 ||28 ||2 ||0 ||0 ||0 ||1 ||0 ||0 ||0 ||1 ||0 ||0 ||0 ||0 
> ||0 ||0 ||0 ||365 ||
> |}
>
> == Failed tasks 2017-11-07 ==
>
> INFO: jenkins-job.sh-1.8.39 Complete log available at
> http://logs.nslu2-linux.org/buildlogs/oe/world/rocko/log.report.20171108_081616.log
>
> === common (1) ===
> *
> meta-openembedded/meta-oe/recipes-support/freerdp/freerdp_git.bb:do_configure
>
> === common-x86 (0) ===
>
> === qemuarm (2) ===
> *
> meta-openembedded/meta-oe/recipes-devtools/android-tools/android-tools_5.1.1.r37.bb:do_compile
> * meta-qt5/recipes-qt/qt5/qtbase_git.bb:do_package_qa
>
> === qemuarm64 (5) ===
> *
> meta-browser/recipes-browser/chromium/chromium_54.0.2810.2.bb:do_compile
> *
> meta-browser/recipes-browser/chromium/chromium-wayland_53.0.2785.143.bb:do_compile
> *
> meta-openembedded/meta-initramfs/recipes-devtools/mtd/ubi-utils-klibc_1.5.2.bb:do_install

I am wondering about this failure, specific for aarch64-oe-linux

 error: '-mgeneral-regs-only' is incompatible with floating-point

Klibc does not support floating point and -mgeneral-regs-only should
"Prevents the use of floating-point instructions or floating-point registers."

Khem, do you have an idea?


> *
> meta-openembedded/meta-initramfs/recipes-kernel/kexec/kexec-tools-klibc_2.0.2.bb:do_configure


| configure: loading site script
/home/jenkins/oe/world/shr-core/tmp-glibc/work/aarch64-oe-linux/kexec-tools-klibc/2.0.2-r1/recipe-sysroot/usr/share/aarch64-oe-linux_config_site.d/glibc_config
| checking build system type... x86_64-pc-linux-gnu
| checking host system type... aarch64-oe-linux-gnu
| checking target system type... aarch64-oe-linux-gnu
| configure: error: unsupported architecture aarch64

I think there is something wrong because the main package kexec-tools
seems not giving build errors on aarch64.

Cheers
Andrea

> *
> meta-openembedded/meta-oe/recipes-devtools/luajit/luajit_2.0.5.bb:do_compile
>
> === qemux86 (27) ===
> * meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb:do_compile
> *
> meta-openembedded/meta-networking/recipes-connectivity/rdist/rdist_6.1.5.bb:do_package
> *
> meta-openembedded/meta-networking/recipes-daemons/opensaf/opensaf_5.17.07.bb:do_compile
> *
> meta-openembedded/meta-networking/recipes-daemons/vsftpd/vsftpd_3.0.3.bb:do_compile
> *
> meta-openembedded/meta-networking/recipes-netkit/netkit-rsh/netkit-rsh_0.17.bb:do_compile
> *
> meta-openembedded/meta-networking/recipes-netkit/netkit-rusers/netkit-rusers_0.17.bb:do_compile
> *
> meta-openembedded/meta-networking/recipes-netkit/netkit-telnet/netkit-telnet_0.17.bb:do_configure
> *
> meta-openembedded/meta-networking/recipes-protocols/mdns/mdns_765.50.9.bb:do_compile
> *
> meta-openembedded/meta-networking/recipes-protocols/tsocks/tsocks_1.8beta5.bb:do_compile
> *
> meta-openembedded/meta-networking/recipes-support/open-isns/open-isns_0.97.bb:do_compile
> *
> meta-openembedded/meta-oe/recipes-benchmark/libhugetlbfs/libhugetlbfs_git.bb:do_compile
> *
> meta-openembedded/meta-oe/recipes-connectivity/umip/umip_1.0.bb:do_compile
> *
> meta-openembedded/meta-oe/recipes-connectivity/wvdial/wvdial_1.61.bb:do_compile
> *
> meta-openembedded/meta-oe/recipes-devtools/pm-qa/pm-qa_git.bb:do_compile
> * meta-openembedded/meta-oe/recipes-extended/mraa/mraa_git.bb:do_compile
> *
> meta-openembedded/meta-oe/recipes-extended/tiptop/tiptop_2.3.bb:do_compile
> *
> meta-openembedded/meta-oe/recipes-kernel/crash/crash_7.1.9.bb:do_compile
> *
> meta-openembedded/meta-oe/recipes-kernel/minicoredumper/minicoredumper_2.0.0.bb:do_compile
> *
> meta-openembedded/meta-oe/recipes-multimedia/alsa/alsa-oss_1.0.17.bb:do_compile
> *
> meta-openembedded/meta-python/recipes-devtools/python/python3-systemd_234.bb:do_compile
> *
> meta-openembedded/meta-python/recipes-devtools/python/python-systemd_234.bb:do_compile
> * meta-qt5/recipes-qt/qt5/qtlocation_git.bb:do_compile
> *
> openembedded-core/meta/recipes-devtools/systemd-bootchart/systemd-bootchart_231.bb:do_compile
> *
> openembedded-core/meta/recipes-graphics/cogl/cogl-1.0_1.22.2.bb:do_compile
> *
> openembedded-core/meta/recipes-graphics/virglrenderer/virglrenderer_git.bb:do_compile
> *
>

Re: [oe] [meta-oe][PATCH] gnome-common: add PACKAGECONFIG for autoconf-archive

2017-11-09 Thread Martin Jansa 
gnome-common is marked as allarch, autoconf-archive isn't. So gnome-common
cannot depend on it as it is now.

This change causes:

 === Comparing signatures for task do_configure.sigdata between qemux86 and
qemux86copy ===
ERROR: gnome-common different signature for task do_configure.sigdata
between qemux86 and qemux86copy
runtaskdeps changed:
gnome-common/gnome-common_3.18.0.bb.do_prepare_recipe_sysroot with hash
f3130e0be68211325008e37b3d49460b
 changed to
gnome-common/gnome-common_3.18.0.bb.do_prepare_recipe_sysroot with hash
0360cfa01ddf508a7670af2fcb306e20
Hash for dependent task
gnome-common/gnome-common_3.18.0.bb.do_prepare_recipe_sysroot changed from
f3130e0be68211325008e37b3d49460b to 0360cfa01ddf508a7670af2fcb306e20


On Tue, Nov 7, 2017 at 3:10 AM, ChenQi  wrote:

> ping
>
>
> On 10/24/2017 04:19 PM, qi.c...@windriver.com wrote:
>
>> From: Chen Qi 
>>
>> Add PACKAGECONFIG for autoconf-archive. Default to enable it to avoid
>> m4 file conflicts between gnome-common and autoconf-archive.
>>
>> e.g.
>> IMAGE_INSTALL_append = " gnome-common autoconf-archive-dev"
>> bitbake 
>>
>> We enable autoconf-archive PACKAGECONFIG to avoid the following error.
>>
>> Error: Transaction check error:
>>file /usr/share/aclocal/ax_check_enable_debug.m4 conflicts between
>> attempted installs of gnome-common-3.18.0-r0.noarch and
>> autoconf-archive-dev-2016.09.16-r0.core2_64
>>file /usr/share/aclocal/ax_code_coverage.m4 conflicts between
>> attempted installs of gnome-common-3.18.0-r0.noarch and
>> autoconf-archive-dev-2016.09.16-r0.core2_64
>>
>> Signed-off-by: Chen Qi 
>> ---
>>   meta-oe/recipes-gnome/gnome-common/gnome-common_3.18.0.bb | 4 
>>   1 file changed, 4 insertions(+)
>>
>> diff --git a/meta-oe/recipes-gnome/gnome-common/gnome-common_3.18.0.bb
>> b/meta-oe/recipes-gnome/gnome-common/gnome-common_3.18.0.bb
>> index 06f3bb3..d874164 100644
>> --- a/meta-oe/recipes-gnome/gnome-common/gnome-common_3.18.0.bb
>> +++ b/meta-oe/recipes-gnome/gnome-common/gnome-common_3.18.0.bb
>> @@ -14,6 +14,10 @@ SRC_URI[archive.sha256sum] =
>> "22569e370ae755e04527b76328befc4c73b62bfd4a572499fd
>>   EXTRA_AUTORECONF = ""
>>   DEPENDS = ""
>>   +# Default to enable autoconf-archive to avoid conflicts
>> +PACKAGECONFIG ??= "autoconf-archive"
>> +PACKAGECONFIG[autoconf-archive] = "--with-autoconf-archive,
>> --without-autoconf-archive, autoconf-archive"
>> +
>>   FILES_${PN} += "${datadir}/aclocal"
>>   FILES_${PN}-dev = ""
>>
>>
>
>
> --
> ___
> 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