I am using
- meta-xilinx and meta-xilinx-tools @ branch 2017.1
- meta-openembedded, poky @ branch morty
When I bitbake core-image-minimal I get the following error. Can you
suggest me a solution?
ERROR: Nothing PROVIDES 'python3-pyyaml-native'. Close matches:
python-pyyaml-native
Signed-off-by: Armin Kuster
---
.../freediameter/files/freeDiameter.conf | 250 +
recipes-security/freediameter/files/init | 160 +
.../freediameter/files/no_test_run.patch | 12 +
"Burton, Ross" writes:
> On 24 April 2017 at 23:00, Nathan Lynch wrote:
>
>> Does adding this patch to lttng-modules work around it?
>>
>
> Yes, it fixes the build here. I'll throw it at the autobuilder now, can
> you send a patch with a commit
Signed-off-by: Khem Raj
---
.../0001-Fix-fallthrough-warnings.patch| 237 +
.../0002-Fix-printf-overflow-warnings.patch| 57 +
recipes-devtools/elfutils/elfutils_0.148.bb| 2 +
3 files changed, 296 insertions(+)
create
On 4/20/17 5:04 PM, Martin Kelly wrote:
> Hi,
>
> After compiling a package with GCC 6, I noticed the following error,
> which is a known issue:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70129
>
> The problem is caused by adding -isystem /usr/include, which breaks the
> GCC 6's
On 04/25/2017 02:14 AM, Patrick Ohly wrote:
Native recipes must be called -native. This is more than just a
recommendation, there's actual code which checks for the suffix.
Not following that rule broke swtpm-wrappers when using the "usrmerge"
DISTRO_FEATURE, because the code in
Hi! This worked perfectly!
But now I have the following problem:
If I set prefered virtual/libgl as my nvidia recipe, then mesa is not
installed and when xorg-xserver is compiling the library libepoxy cannot
compile because of: No package 'egl' found (because this is provided by
mesa I guess)
If
On Tue, Apr 25, 2017 at 11:15 AM, Alvaro Garcia wrote:
> Hi! This worked perfectly!
>
> But now I have the following problem:
> If I set prefered virtual/libgl as my nvidia recipe, then mesa is not
> installed and when xorg-xserver is compiling the library libepoxy cannot
>
Hello Paul,
thanks for the try. It should means that there is a detail on my setup
which prevents the build from being done. I encounter the error on the
commits id your provided too. I also tried being on last tag on poky
project for morty branch, without success. I also suspected my python
On 04/25/2017 07:41 AM, Malte Thiel wrote:
Hello,
I am trying to compile a Qt 5.8 application using the master branch
of meta-qt5/recipes-qt/qt5/ (For 5.8 support).
Within my recipe I have:
RDEPENDS_${PN} = "libgcc glibc qtbase [...] qtdeclarative"
My recipe (and therefore the application)
On 24-04-17 16:29, Martin Jansa wrote:
* gnutls depends on nettle-3.1* since 3.4.0:
The requirement for nettle was bumped from 3.0 to 3.1 in gnutls_3_4_0
https://gitlab.com/gnutls/gnutls/commit/c84129af91b21d33ffe086e507632771b0e76498
and from 2.7 to 3.0 a bit earlier also in
On 04/25/2017 07:53 AM, Malte Thiel wrote:
Good day,
Hello,
How can I add my own dts file to the arch/arm/boot/dts folder? Within
my yocto installation the whole path for the dts files is:
tmp/work/sm2_imx6-poky-linux-gnueabi/linux-yocto-custom/4.1.15-2/git/arch/arm/boot/dts
As you can
On Mon, Apr 24, 2017 at 10:20 PM, Mike Looijmans
wrote:
> On 24-04-17 16:29, Martin Jansa wrote:
>>
>> * gnutls depends on nettle-3.1* since 3.4.0:
>> The requirement for nettle was bumped from 3.0 to 3.1 in gnutls_3_4_0
>>
>>
Hi
I am trying to include CPPCheck into Yocto to be used by CMake as a Cmake
Module.
Hence when building my application recipes that are based on using CMake
build as build system, CPPCheck is performed.
What I currently did, was:
Making a recipe for CPPCheck to be used in the toolchain by:
On Mon, Apr 24, 2017 at 7:25 PM, wrote:
> Hello,
> I am currently encountering an issue with meta-raspberry and more
> specifically Raspberry Pi 3 build. Since I was not sure the problem was
> not my fault, I cloned a fresh copy of poky and meta-raspberrypi (both
>
The libQtDBus requires libQtXml at link time otherwise it fails with
the following error:
x86_64-pokysdk-linux-g++
--sysroot=/home/build/dev/yocto/build/tmp/sysroots/x86_64-nativesdk-pokysdk-linux
-Wl,-O1 -fno-exceptions -Wl,--no-undefined -Wl,-O1
-Wl,-rpath,/opt/poky-oso/2.2/sysroots/x86_64
Native recipes must be called -native. This is more than just a
recommendation, there's actual code which checks for the suffix.
Not following that rule broke swtpm-wrappers when using the "usrmerge"
DISTRO_FEATURE, because the code in native.bbclass which cleans up
DISTRO_FEATURES for native
On 24 April 2017 at 23:00, Nathan Lynch wrote:
> Does adding this patch to lttng-modules work around it?
>
Yes, it fixes the build here. I'll throw it at the autobuilder now, can
you send a patch with a commit message that isn't "someone told me to try
this"? :)
Ross
On 04/25/2017 12:09 PM, Olivier Sobrie wrote:
This patch ensures that libQtXml is build before libQtDBus and that
both libQtGui and libQtNetwork are built before libQt3Support.
Applied, thanks. Please add a [meta-qt4] to the subject, so that it's
easier to see which layer the patch is
On Tue, Apr 25, 2017 at 01:58:25PM +0300, Alexander Kanavin wrote:
> On 04/25/2017 12:09 PM, Olivier Sobrie wrote:
>
> > This patch ensures that libQtXml is build before libQtDBus and that
> > both libQtGui and libQtNetwork are built before libQt3Support.
>
> Applied, thanks. Please add a
Hello,
I am trying to compile a Qt 5.8 application using the master branch
of meta-qt5/recipes-qt/qt5/ (For 5.8 support).
Within my recipe I have:
RDEPENDS_${PN} = "libgcc glibc qtbase [...] qtdeclarative"
My recipe (and therefore the application) compiles fine. However, in
do_rootfs I get the
21 matches
Mail list logo