Thanks Ross, my TOOLCHAIN_TARGET_TASK_append = " hals hals-doc" does have the
‘space’, so that is not the issue.
( when I forgot it, got errors which had the ‘hal’ on the previous package, i.e
gtesthal “, so it was apparent about the missing space.
no real idea how to ‘debug’ the populate_sdk_e
On 01/09/2017 04:49 AM, Patrick Ohly wrote:
>...
>
> I'm wondering if we can address two bugs with the same fix, something
> that requires that the Subject line is starting with a set of tags plus
> the [PATCH] tag. For example:
>
> patch_prefix = re.match('(\s*\[[^]]*\]\s*)*\[\s*PATCH', mail.g
As we do around each Embedded Linux Conference, OpenEmbedded will host a
developer meeting to discuss the state of OpenEmbedded and what efforts
we should focus on over the next six months or so.
All developers and users are welcome to attend. We like to hear feedback
from a variety of people over
I just want to make sure that we dont pile collection of patches that
we end up maintaining forever.
On Mon, Jan 9, 2017 at 12:34 PM, Jose Lamego
wrote:
>
>
> On 01/09/2017 02:30 PM, Khem Raj wrote:
>> On Mon, Jan 9, 2017 at 12:21 PM, Jose Lamego
>> wrote:
>>>
>>>
>>> On 01/09/2017 12:44 PM, Khe
On 01/09/2017 02:30 PM, Khem Raj wrote:
> On Mon, Jan 9, 2017 at 12:21 PM, Jose Lamego
> wrote:
>>
>>
>> On 01/09/2017 12:44 PM, Khem Raj wrote:
>>> On Fri, Jan 6, 2017 at 6:50 AM, Jose Lamego
>>> wrote:
From: Jose Lamego
Reviewing patches from a series requires heavy usage of t
On Mon, Jan 9, 2017 at 12:21 PM, Jose Lamego
wrote:
>
>
> On 01/09/2017 12:44 PM, Khem Raj wrote:
>> On Fri, Jan 6, 2017 at 6:50 AM, Jose Lamego
>> wrote:
>>> From: Jose Lamego
>>>
>>> Reviewing patches from a series requires heavy usage of the
>>> browser navigation buttons, providing a poor UX
On 01/09/2017 12:44 PM, Khem Raj wrote:
> On Fri, Jan 6, 2017 at 6:50 AM, Jose Lamego
> wrote:
>> From: Jose Lamego
>>
>> Reviewing patches from a series requires heavy usage of the
>> browser navigation buttons, providing a poor UX.
>>
>> This changes allows viewing content from each patch in
On Fri, Jan 6, 2017 at 3:52 AM, Chris Trobridge
wrote:
> I am getting "Exception: OSError: [Errno 7] Argument list too long" for
> sign_rpm in the do_package_write_rpm tasks for the
> linux-yocto and glibc-locale recipes.
>
> This is building core-image-minimal (and also my own image) with morty
On Fri, Jan 6, 2017 at 6:50 AM, Jose Lamego
wrote:
> From: Jose Lamego
>
> Reviewing patches from a series requires heavy usage of the
> browser navigation buttons, providing a poor UX.
>
> This changes allows viewing content from each patch in a series,
> without leaving the series view.
>
The
On Sat, Jan 7, 2017 at 5:53 AM, John Rama wrote:
> Dear Yocto specialists
>
> I have one question.
> When building the kernel module and install to rootfs with Yocto, I got the
> kernel module without debug information.
> Investigating a little bit revealed that it seems do_package process remove
I believe you need to apply a patch that is already in the poky git tree but
might not be in the branch you are on. Try:
git fetch origin
git cherry-pick b6253350fb86d8e54792905342a5892af570d526
Rich
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctopro
On 9 January 2017 at 15:51, wrote:
> TOOLCHAIN_TARGET_TASK_append = "hals hals-doc"
>
_append doesn't insert whitespace, so you need to do it. Use
TOOLCHAIN_TARGET_TASK_append = " hals hals-doc" in your image recipe
instead of changing it globally.
Ross
--
__
Hi Paul
Thanks, I am new in this area, so could be miss-understanding some of these:
What I would like to occur, when
local.conf has:
IMAGE_INSTALL_append = "hals"
TOOLCHAIN_TARGET_TASK_append = "hals hals-doc"
1) image has the "hals" runtime
2)when I use -c populate_sdk and/or -c populate_sd
Hi,
I'm int the process of enabling multlib configuration for my distro, by adding
following lines to local.conf file:
# Define multilib target
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "armv7athf-neon"
I'm able to produce images, where applica
Current Dev Position: YP 2.3 M2 -> M3
Next Deadline: YP 2.3 M2 by Jan 23, 2017
SWAT team rotation: Joshua -> Armin
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
Key Status/Updates:
*The M1 issues proved tricky to debug and potentially meant there were
widespread p
Hi,
Configuring the eclipse(window7 luna) yocto plug-in is error,
Eclipse Report this error:
!ENTRY org.eclipse.jface 4 0 2017-01-05 10:39:37.646
!MESSAGE java.lang.NullPointerException
!STACK 0
java.lang.NullPointerException
at org.yocto.sdk.ide.YoctoSDKChecker.checkYoctoSDK(Un
Hi all,
This is my first post to this list, so my apologies if I have not
conformed in some way to the posting etiquette.
I'm managing on a CI server that starts many morty builds which use
the setscene state cache to do incremental builds where possible. I
have a problem which can be broken down
On 01/07/2017 05:05 PM, Rohit Jindal wrote:
Please suggest me the solution for compiling
Openjdk 8 for arm adding support for any jit compiler like shark or jamvm
This is not how you should ask for help from people who have no
obligation to help you. No one is going to respond, and sending the
On 01/07/2017 05:29 PM, Robert P. J. Day wrote:
colleague wants to know how one stays up to date with security
alerts related to YP releases, i checked out the yocto-security
mailing list:
https://lists.yoctoproject.org/pipermail/yocto-security/
but that looks like a very dead mailing list.
Please help.me adding support for JIT to openjdk 8 in arm architecture.
Immediate help is highly appreciated.
Rohit
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Fri, 2017-01-06 at 17:03 -0600, Jose Lamego wrote:
> Patchwork may incorrectly identify emails containing patch-like content as
> patches.
> This change makes "[PATCH" prefix in subject mandatory for emails to be
> considered as new patches.
>
> [YOCTO #10764]
>
> Signed-off-by: Jose Lamego
>
On 7 January 2017 at 10:49, Andreas Cord-Landwehr
wrote:
> Hi, since it's roughly two weeks, I just wanted to bump this patch again
> (yes,
> I know many people were on vacations).
> But actually, I would already be glad to hear whether I sent the patch to
> the
> right list.
>
The correct list
Apply patch from iotivity-1.2.1:
* [PATCH 081/341] yocto: Add aarch64 for DragonBoard-410c
Signed-off-by: Philippe Coval
---
...81-yocto-Add-aarch64-for-DragonBoard-410c.patch | 48 ++
recipes-core/iotivity/iotivity_1.2.0.bb| 1 +
2 files changed, 49 insertions(
This patch was in iotivity 1.1-rel branch,
and (wrongly) removed in 1.2.0
So it needed to be reintroduced in upstream 1.2-rel
and as a patch for 1.2.0, track upstream bug at:
https://jira.iotivity.org/browse/IOT-1219
Signed-off-by: Philippe Coval
---
...ools-from-sysroot-before-system-PATH-a
It was discovered while building AGL using Intel BSP.
Also fix dangling syslink,
discovered while building ostro OS.
Signed-off-by: Philippe Coval
---
recipes-core/iotivity/iotivity_1.2.0.bb | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/recipes-core/iotivity/iotivity
Nope, we're missing a tarball somewhere. Can you file a bug?
Ross
On 6 January 2017 at 22:30, Robert P. J. Day wrote:
>
> i notice that if you search for the powerpc BSP in the latest
> release here:
>
> https://www.yoctoproject.org/downloads/bsps?release=98&;
> processer%5B%5D=22&title=
>
>
On Saturday, January 7, 2017, Rohit Jindal wrote:
> Please suggest me the solution for compiling
> Openjdk 8 for arm adding support for any jit compiler like shark or jamvm
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.or
Hi,
I am upgrading Yocto version from daisy to krogoth. In this process when
building kernel, i am getting below error
ERROR: linux-altera-ltsi-3.10-r1 do_deploy: Taskhash mismatch
c4875fc746f382558fe137fc1188dfe7 verses 1c5cadda9369cc54cb44d732ed6004e8
for /home/rajesh/k2_poky-krogoth/k2/source/p
28 matches
Mail list logo
