The previous wording, e.g.
ERROR: wget was skipped: incompatible with license GPLv3
isn't very clear and could be taken to imply that the recipe is
incompatible with its own license.
Signed-off-by: Andre McCurdy
---
meta/classes/base.bbclass | 2 +-
1 file changed, 1
* This is converging the recipes for go from
meta-virtualization and oe-meta-go
* Add recipes for go 1.7
* go.bbclass is added to ease out writing
recipes for go packages
* go-examples: Add an example, helloworld written in go
This should serve as temlate for writing go recipes
* This is converging the recipes for go from
meta-virtualization and oe-meta-go
* Add recipes for go 1.7
* go.bbclass is added to ease out writing
recipes for go packages
* go-examples: Add an example, helloworld written in go
This should serve as temlate for writing go recipes
On Fri, Mar 3, 2017 at 2:54 PM, Burton, Ross wrote:
>
> On 3 March 2017 at 21:39, Khem Raj wrote:
>>
>> > Enabling building the Intel Memory Protection Extension library for x86.
>> >
>>
>> hope this works on amd chips as well ?
>
>
>
If sdk ins't in BUILDHISTORY_FEATURES the get_extra_sdkinfo fails
because no information about sdk is generated in buildhistory repo.
Signed-off-by: Aníbal Limón
---
meta/classes/buildhistory.bbclass | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff
On 3 March 2017 at 21:39, Khem Raj wrote:
> > Enabling building the Intel Memory Protection Extension library for x86.
> >
>
> hope this works on amd chips as well ?
https://en.wikipedia.org/wiki/Intel_MPX
It depends on new instructions, so you'll have to ask AMD. :)
Ross
* This is converging the recipes for go from
meta-virtualization and oe-meta-go
* Add recipes for go 1.7
* go.bbclass is added to ease out writing
recipes for go packages
* go-examples: Add an example, helloworld written in go
This should serve as temlate for writing go recipes
Typo in summary, but thanks for taking care of this!
On Fri, Mar 3, 2017 at 10:36 PM, Andreas Müller <
schnitzelt...@googlemail.com> wrote:
> Was detected in Martin's world build
>
> Signed-off-by: Andreas Müller
> ---
>
* This is converging the recipes for go from
meta-virtualization and oe-meta-go
* Add recipes for go 1.7
* go.bbclass is added to ease out writing
recipes for go packages
* go-examples: Add an example, helloworld written in go
This should serve as temlate for writing go recipes
On Fri, Mar 3, 2017 at 3:54 AM, Richard Purdie
wrote:
> Enabling building the Intel Memory Protection Extension library for x86.
>
hope this works on amd chips as well ?
> Signed-off-by: Richard Purdie
> ---
>
After the introduction of RSS, I still found it hard to get
dependencies on some common tools that are typically installed on the
build host correct. Using the wrong version of tools like pkg-config,
gdbus-codegen and dbus-binding-tool can cause build failures.
To circumvent this, I created dummy
This is intended to catch missing dependencies on the real version.
Signed-off-by: Peter Kjellerstedt
---
scripts/blacklisted/pkg-config | 16
1 file changed, 16 insertions(+)
create mode 100755 scripts/blacklisted/pkg-config
diff --git
This is intended to catch missing dependencies on the real version.
Signed-off-by: Peter Kjellerstedt
---
scripts/blacklisted/dbus-binding-tool | 11 +++
1 file changed, 11 insertions(+)
create mode 100755 scripts/blacklisted/dbus-binding-tool
diff --git
The scripts/blacklisted directory contains dummy tools that blocks out
the corresponding tool from the host installation. It is excpected
that the correct version of the tools are instead built and installed
to the RSS for recipes that need any of these tools.
Signed-off-by: Peter Kjellerstedt
This is intended to catch missing dependencies on the real version.
Signed-off-by: Peter Kjellerstedt
---
scripts/blacklisted/gdbus-codegen | 11 +++
1 file changed, 11 insertions(+)
create mode 100755 scripts/blacklisted/gdbus-codegen
diff --git
This is needed for the make_scripts task.
Signed-off-by: Peter Kjellerstedt
---
meta/classes/module.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/module.bbclass b/meta/classes/module.bbclass
index a588873..99b7ebc 100644
pkg-config is used by the kernel build system when creating the
configuration tools.
Signed-off-by: Peter Kjellerstedt
---
meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Was detected in Martin's world build
Signed-off-by: Andreas Müller
---
...link-libapr-against-phtread-to-make-gold-.patch | 50 ++
meta/recipes-support/apr/apr_1.5.2.bb | 1 +
2 files changed, 51 insertions(+)
create mode 100644
Was detected in Martin's world build
Signed-off-by: Andreas Müller
---
...s_resize-link-against-libuuid-explicitly-.patch | 34 ++
meta/recipes-extended/parted/parted_3.2.bb | 1 +
2 files changed, 35 insertions(+)
create mode 100644
That's reasonable I think
On Fri, Mar 3, 2017 at 12:36 PM Martin Kelly wrote:
> On 03/03/2017 12:23 PM, Khem Raj wrote:
> > On Fri, Mar 3, 2017 at 12:15 PM, Martin Kelly wrote:
> >> On 03/03/2017 12:12 PM, Khem Raj wrote:
> >>>
> >>> with meta-clang there is
On 03/03/2017 12:12 PM, Khem Raj wrote:
with meta-clang there is no desire to support multiple versions of
llvm and thats why versioning was dropped however, I would still like
to fix the versioning if that makes it more useful.
OK, keeping a single version is certainly simpler. Could you
On 03/03/2017 12:23 PM, Khem Raj wrote:
On Fri, Mar 3, 2017 at 12:15 PM, Martin Kelly wrote:
On 03/03/2017 12:12 PM, Khem Raj wrote:
with meta-clang there is no desire to support multiple versions of
llvm and thats why versioning was dropped however, I would still like
to
Hi,
I'm attempting to build a recipe using the LLVM/clang cross toolchain
provided in meta-clang. However, I'm hitting issues with the llvm-config
wrapper in llvm-common. Specifically, it looks like the wrapper was
copied over from the LLVM recipe in meta-oe, but the versioning logic
was not
On Fri, Mar 3, 2017 at 12:15 PM, Martin Kelly wrote:
> On 03/03/2017 12:12 PM, Khem Raj wrote:
>>
>> with meta-clang there is no desire to support multiple versions of
>> llvm and thats why versioning was dropped however, I would still like
>> to fix the versioning if that makes
On Fri, Mar 3, 2017 at 10:44 AM, Martin Kelly wrote:
> Hi,
>
> I'm attempting to build a recipe using the LLVM/clang cross toolchain
> provided in meta-clang. However, I'm hitting issues with the llvm-config
> wrapper in llvm-common. Specifically, it looks like the wrapper was
On Fri, Mar 3, 2017 at 11:15 AM, Martin Kelly wrote:
> Hi,
>
> I noticed that meta-clang builds only static LLVM libraries, unlike the
> meta-oe version of LLVM 3.3, which builds shared libraries. In fact, this
> appears to be the LLVM upstream default as well.
>
> What is the
> -Original Message-
> From: Max Krummenacher [mailto:max.oss...@gmail.com]
> Sent: den 3 mars 2017 17:24
> To: Peter Kjellerstedt
> Cc: OE-core
> Subject: Re: [OE-core] [PATCHv3 0/5] Add dummy tools to help identify
> needed dependencies
>
> Hi
>
> 2017-03-03 12:17 GMT+01:00 Peter
Hi,
I noticed that meta-clang builds only static LLVM libraries, unlike the
meta-oe version of LLVM 3.3, which builds shared libraries. In fact,
this appears to be the LLVM upstream default as well.
What is the reason for the difference? Shared versions of LLVM would be
useful for reducing
Hi
2017-03-03 12:17 GMT+01:00 Peter Kjellerstedt :
> To circumvent this, I created dummy versions of the tools that always
> fail and placed them in the scripts directory. Thus, if the real tool
> has not been installed in the RSS, the dummy version is used and the
>
On 3 March 2017 at 14:41, Burton, Ross wrote:
> This appears to be causing cryptodev-module to fail:
> http://errors.yoctoproject.org/Errors/Details/134637/
>
> TOPDIR/tmp/work/qemux86_64-poky-linux/cryptodev-module/1.
> 8-r0/cryptodev-linux-1.8/zc.c:63:8: error: too few
Signed-off-by: Ross Burton
---
meta/recipes-kernel/cryptodev/cryptodev.inc| 3 +-
.../cryptodev/files/kernel-4-10-changes.patch | 57 ++
2 files changed, 59 insertions(+), 1 deletion(-)
create mode 100644
Hi Bruce,
On 27 February 2017 at 03:10, Bruce Ashfield
wrote:
> Here is the latest updates to the linux-yocto kernel versions, and
represents
> the versions that we'd like to be included in the upcoming release.
This appears to be causing cryptodev-module to fail:
Based on the blacklist behaviour, recipes can be tagged as deprecated.
Such recipes will produce a warning message when included in a build but
unlike blacklisted recipes, the build will continue.
Signed-off-by: Joe MacDonald
---
Literally no different than v1, differs
On 3 March 2017 at 12:12, Fabio Berton
wrote:
> Sorry for delay. This error for qemux86 is because common.wks.inc and
> directdisk-gpt.wks files in scripts/lib/wic/canned-wks directory doesn't
> have option --fstype= for part /boot.
>
> For qemuarm machines I get
Signed-off-by: Markus Lehtonen
Signed-off-by: Ross Burton
(cherry picked from commit a00a362e3dc18ba04230cbbd6f91264e5d76f40d)
---
meta/lib/oe/gpg_sign.py | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git
Split the file list into chunks in order to avoid
"OSError: [Errno 7] Argument list too long"
This would happend when a package has huge amount of subpackages, e.g.
glibc-locale.
[YOCTO #11069]
Signed-off-by: Markus Lehtonen
Signed-off-by: Ross Burton
This patchset backports two fixes to gpg signing of rpm packages. The first
patch fixes signing of packages with a large amount of subpackages (e.g.
glibc-locale). The last three patches makes rpm package signing possible with
gpg version > 2.1.
The following changes since commit
We need to check the gpg version and alter its command line options
accordingly.
[YOCTO #11054]
Signed-off-by: Markus Lehtonen
Signed-off-by: Ross Burton
(cherry picked from commit 44a44b7e582a5a654baf21829d168568481c13d9)
---
Add a new %_gpg_sign_cmd_extra_args macro that allows customizing the
gpg options used when signing rpm packages. This is needed to be able to
sign packages with gpg 2.1 which requires "--pinentry-mode loopback" to
allow non-interactive signing.
[YOCTO #11054]
Signed-off-by: Markus Lehtonen
Using of bitbake environment variables in-place of hardcoded strings makes this
recipe portable to all environments.
Signed-off-by: Amarnath Valluri
---
meta/recipes-extended/lsb/lsb_4.1.bb | 40 +---
1 file changed, 19 insertions(+),
Use appropriate bitbake variable inplace of hardcoded sbin path in Makefile
Signed-off-by: Amarnath Valluri
---
meta/recipes-extended/mdadm/mdadm_4.0.bb | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-extended/mdadm/mdadm_4.0.bb
Hi Ross,
Sorry for delay. This error for qemux86 is because common.wks.inc and
directdisk-gpt.wks files in scripts/lib/wic/canned-wks directory doesn't
have option --fstype= for part /boot.
For qemuarm machines I get the error:
| DEBUG: Executing python function set_image_size
| DEBUG:
Enabling building the Intel Memory Protection Extension library for x86.
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/gcc/gcc-runtime.inc | 20 +++-
1 file changed, 19 insertions(+), 1 deletion(-)
diff --git
Having dependency on do_patch will fail while building kernel using
externalsrc. Depend on do_configure instead of do_patch to bypass the
compilation error.
Signed-off-by: Manjukumar Matha
---
meta/classes/kernelsrc.bbclass | 2 +-
virtio-gpu: memory leakage when destroying gpu resource
Reference:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9912
Reference to upstream patch:
http://git.qemu-project.org/?p=qemu.git;a=patch;h=b8e23926c568f2e963af39028b71c472e3023793
Signed-off-by: Sona Sarmadi
virtio-gpu: information leakage in virgl_cmd_get_capset
References:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9908
Signed-off-by: Sona Sarmadi
---
.../recipes-devtools/qemu/qemu/CVE-2016-9908.patch | 44 ++
This is intended to catch missing dependencies on the real version.
Signed-off-by: Peter Kjellerstedt
---
scripts/pkg-config | 16
1 file changed, 16 insertions(+)
create mode 100755 scripts/pkg-config
diff --git a/scripts/pkg-config
pkg-config is used by the kernel build system when creating the
configuration tools.
Signed-off-by: Peter Kjellerstedt
---
meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This is needed for the make_scripts task.
Signed-off-by: Peter Kjellerstedt
---
meta/classes/module.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/module.bbclass b/meta/classes/module.bbclass
index a588873..99b7ebc 100644
This is intended to catch missing dependencies on the real version.
Signed-off-by: Peter Kjellerstedt
---
scripts/dbus-binding-tool | 11 +++
1 file changed, 11 insertions(+)
create mode 100755 scripts/dbus-binding-tool
diff --git
After the introduction of RSS, I still found it hard to get
dependencies on some common tools that are typically installed on the
build host correct. Using the wrong version of tools like pkg-config,
gdbus-codegen and dbus-binding-tool can cause build failures.
To circumvent this, I created dummy
This is intended to catch missing dependencies on the real version.
Signed-off-by: Peter Kjellerstedt
---
scripts/gdbus-codegen | 11 +++
1 file changed, 11 insertions(+)
create mode 100755 scripts/gdbus-codegen
diff --git a/scripts/gdbus-codegen
auto.conf is included before local.conf. Instead of keeping them separate, merge
them into the extsdk local.conf. As it happens we can do this quite neatly, more
neatly than the current code IMO and it makes the configuration easier for the
end
user to understand too.
This means auto.conf is
We should be able to test sdks in parallel. As far as I can tell, this
restriction crept in for no good reason, based on locks that testimage used
for the non-qemu case.
Therefore remove the lock and allow sdks to test in parallel.
Signed-off-by: Richard Purdie
We need to appent to SSTATE_MIRRORS in case other areas of code are also
setting the variable.
Signed-off-by: Richard Purdie
---
meta/classes/populate_sdk_ext.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
test_extend_autotools_recipe_creation needs libxml2 so ensure this is
installed/present as it may not be in the minimal eSDK case.
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/sdkext/cases/devtool.py | 1 +
1 file changed, 1 insertion(+)
diff --git
On Fri, 3 Mar 2017, Jack Mitchell wrote:
> On 03/03/17 10:06, Robert P. J. Day wrote:
> > On Fri, 3 Mar 2017, Anders Darander wrote:
> >
> >> * Robert P. J. Day [170302 12:33]:
> >>
> >>> On Thu, 2 Mar 2017, Robert P. J. Day wrote:
> >>
> inherit pypi setuptools
>
On 03/03/2017 12:45 PM, Josef Holzmayr wrote:
- Given the current situation, the best practise seems to be to have
package.json take care of the needed modules, and have it handle that.
Means in my opinion that there should be as little npm-based stuff
installed as possible. Exactly one, in the
After the introduction of RSS, I still found it hard to get
dependencies on some common tools that are typically installed on the
build host correct. Using the wrong version of tools like pkg-config,
gdbus-codegen and dbus-binding-tool can cause build failures.
To circumvent this, I created dummy
This is intended to catch missing dependencies on the real version.
Signed-off-by: Peter Kjellerstedt
---
scripts/gdbus-codegen | 11 +++
1 file changed, 11 insertions(+)
create mode 100755 scripts/gdbus-codegen
diff --git a/scripts/gdbus-codegen
pkg-config is used by the kernel build system when creating the
configuration tools.
Signed-off-by: Peter Kjellerstedt
---
meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This is intended to catch missing dependencies on the real version.
Signed-off-by: Peter Kjellerstedt
---
scripts/pkg-config | 16
1 file changed, 16 insertions(+)
create mode 100755 scripts/pkg-config
diff --git a/scripts/pkg-config
This is needed for the make_scripts task.
---
meta/classes/module.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/module.bbclass b/meta/classes/module.bbclass
index a588873..99b7ebc 100644
--- a/meta/classes/module.bbclass
+++ b/meta/classes/module.bbclass
This is intended to catch missing dependencies on the real version.
Signed-off-by: Peter Kjellerstedt
---
scripts/dbus-binding-tool | 11 +++
1 file changed, 11 insertions(+)
create mode 100755 scripts/dbus-binding-tool
diff --git
On 03/03/17 10:06, Robert P. J. Day wrote:
> On Fri, 3 Mar 2017, Anders Darander wrote:
>
>> * Robert P. J. Day [170302 12:33]:
>>
>>> On Thu, 2 Mar 2017, Robert P. J. Day wrote:
>>
inherit pypi setuptools
require python-psutil.inc
>>
and the
Additional packaging/dependency thoughts:
Using the devtool mechanism to create a recipe basically packs up all
dependencies. While this is a relatively easy solution to make sure that
the resulting package is functional, I can see some issues:
- Dependency tracking via bitbake is virtually
Hi Trevor,
On 28.02.2017 19:00, Trevor Woerner wrote:
Ideally "devtool add ..." wouldn't choke and crash when it encounters a
LICENSE string it doesn't understand. When parsing license strings from random
places on The Internet it's inevitable odd things will come up :-)
Yeah, it even seems
On Fri, 3 Mar 2017, Anders Darander wrote:
> * Robert P. J. Day [170302 12:33]:
>
> > On Thu, 2 Mar 2017, Robert P. J. Day wrote:
>
> > > inherit pypi setuptools
> > > require python-psutil.inc
>
> > > and the corresponding .inc file contains:
>
> > > RDEPENDS_${PN}
* Robert P. J. Day [170302 12:33]:
> On Thu, 2 Mar 2017, Robert P. J. Day wrote:
> > inherit pypi setuptools
> > require python-psutil.inc
> > and the corresponding .inc file contains:
> > RDEPENDS_${PN} += " \
> > ${PYTHON_PN}-shell \
> >
69 matches
Mail list logo