Hello,
I’m having an issue when I try to use the SDK generated by my yocto instance.
Currently I have yocto set-up to correctly build my image – this all works well.
I've built the SDK in the following ways:
* bitbake {image} –c populate_sdk
* bitbake meta-toolchain-qt5
* bitbake {image-
On 2018-09-20 10:08, Evan O'Loughlin wrote:
Hello,
I’m having an issue when I try to use the SDK generated by my yocto
instance.
Currently I have yocto set-up to correctly build my image – this all
works well.
I've built the SDK in the following ways:
* bitbake {image} –c populate_sdk
On Thu, 20 Sep 2018 at 10:01, Mohamed Youseif
wrote:
> I had changed the source of my package, and create a new recipe for my
> package so it fetches from SourceForge, the new recipe does not inherit
> Autotools and modify the do_compile, do_install as following:
> do_compile () {
> oe_run
Hi Bas,
I'm using the offending line in helloworld.c to highlight the issue I'm seeing.
My main program is a Qt application where I see the same issue when trying to
build in QtCreator.
My issue relates to the fact that several include files are not readily
available after 'sourcing' the envir
On 2018-09-20 11:40, Evan O'Loughlin wrote:
-Original Message-
From: Bas Mevissen [mailto:ab...@basmevissen.nl]
Sent: 20 September 2018 10:12
To: Evan O'Loughlin
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Yocto SDK generated - unable to compile
application
On 2018-09-20 10:08, Ev
From: Bas Mevissen [ab...@basmevissen.nl]
Sent: 20 September 2018 10:50
To: Evan O'Loughlin
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Yocto SDK generated - unable to compile application
On 2018-09-20 11:40, Evan O'Loughlin wrote:
> -Original Mes
So your makefile is explictly saying "ignore the value from the
environment, always use gcc on the host".
Delete that line from the makefile, the default is good and then the
environment value to set CC to the cross compiler will work.
This is why people shouldn't hand-code Makefiles: it is harde
On 2018-09-17 10:27, Burton, Ross wrote:
On Mon, 17 Sep 2018 at 08:13, Peter Bergin wrote:
I'm pretty sure I have narrowed down the root cause to the restriction
of virtual memory and that liblzma base its memory calculations on
physical RAM.
To prove this I added a printout in rpm-native/rpmi
On 2018-09-20 12:28, Evan O'Loughlin wrote:
From: Bas Mevissen [ab...@basmevissen.nl]
Sent: 20 September 2018 10:50
To: Evan O'Loughlin
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Yocto SDK generated - unable to compile
application
On 2018-09-20 11:
From: Bas Mevissen [ab...@basmevissen.nl]
Sent: 20 September 2018 13:23
To: Evan O'Loughlin
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Yocto SDK generated - unable to compile application
On 2018-09-20 12:28, Evan O'Loughlin wrote:
> _
Hello,
I have several projects hosted in Azure DepOs (former Visual Studio online).
When I glone them with git inside my host machine or the Ubuntu 16.04
container, everything works fine. When I use bitbake to build the recipe
with the same ssh uri, it fails (yocto inside Ubuntu 16.04 container
From: yocto-boun...@yoctoproject.org [yocto-boun...@yoctoproject.org] on behalf
of Jakob Hasse [jakob.ha...@qiio.com]
Sent: 19 September 2018 10:05
To: Yocto List
Cc: Andrii Voloshyn
Subject: [yocto] git works standalone, but not within yocto for weird Az
quot;
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "i586-poky-linux"
MACHINE = "qemux86"
DISTRO = "poky"
DISTRO_VERSION = "2.5+snapshot-20180920"
TUNE_FEATU
Thanks, Ross I had modified the makefile like what you said and now it works
fine.
Yusuf
From: Burton, Ross
Sent: Thursday, September 20, 2018 12:43 PM
To: mohamedyous...@outlook.com
Cc: Yocto-mailing-list
Subject: Re: [yocto] Adding nInvaders game package recipe
On Wed, 19 Sep 2018 12:33:37 +0100
"Burton, Ross" wrote:
> Is anyone actually writing a patch?
I have a tentative fix for this checked into master, I don't know
whether it actually works because I don't have any inodes over 2^63.
It doesn't seem to have *broken* anything, though in casual testi
Dell - Internal Use - Confidential
> On Wed, 19 Sep 2018 12:33:37 +0100
> "Burton, Ross" wrote:
>
> > Is anyone actually writing a patch?
>
> I have a tentative fix for this checked into master, I don't know
> whether it actually works because I don't have any inodes over 2^63.
>
> It doesn't s
On Thu, 20 Sep 2018 20:41:02 +
wrote:
> Okay, so I found the problem, and I have a patch for it. Throughout
> the pseudo_db.c code, the handling of the msg->ino objects is not
> consistent. Many get passed to the sqlite3_bind_int64 function, but
> NOT ALL. 9 instances in the code, includin
Nice catch. Merged a patch that applies this also.
-s
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
I had run the command and it prints out that:
nInvaders: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically
linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32,
BuildID[sha1]=73d88937de4f28a243ba40001af8dbd5c1ca3ac8, not stripped
the ${CC} in makefile is defined
On 9/20/18 3:32 PM, Evan O'Loughlin wrote:
>
>
> From: Bas Mevissen [ab...@basmevissen.nl]
> Sent: 20 September 2018 13:23
> To: Evan O'Loughlin
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Yocto SDK generated - unable to compile application
>
>
On Thu, Sep 20, 2018 at 1:03 PM Peter Bergin wrote:
>
> On 2018-09-17 10:27, Burton, Ross wrote:
>
> On Mon, 17 Sep 2018 at 08:13, Peter Bergin wrote:
>
> I'm pretty sure I have narrowed down the root cause to the restriction
> of virtual memory and that liblzma base its memory calculations on
>
I had changed the source of my package, and create a new recipe for my package
so it fetches from SourceForge, the new recipe does not inherit Autotools and
modify the do_compile, do_install as following:
do_compile () {
oe_runmake
}
do_install () {
:
}
but i had modified the do_ins
22 matches
Mail list logo
