From: Kai Kang
Backport patch from setools upstream to fix build failure with GCC 7 due
to possible truncation of snprintf output. It could be reproduced on 64
bit bsps such as qemux86-64 and qemumips64 with configs:
SELECTED_OPTIMIZATION = "${DEBUG_OPTIMIZATION}"
DEBUG_BUILD = "1"
From: Kai Kang
Sync with oe-core to update to warrior release name series.
Signed-off-by: Kai Kang
---
conf/layer.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/conf/layer.conf b/conf/layer.conf
index 5fecac6..b10bd76 100644
--- a/conf/layer.conf
+++
There are tow errors when compiling powerpc rt kernel.
1.
Error: operand out of range (0x00208690 is not between
0x and 0x)
2.
error: implicit declaration of function 'printk_safe_flush_on_panic'
There are for v5.0/standard/preempt-rt/base
From: Sebastian Andrzej Siewior
Powerpc32/64 does not compile because TIF_SYSCALL_TRACE's bit is higher
than 15 and the assembly instructions don't expect that.
Move TIF_RESTOREALL, TIF_NOERROR to the higher bits and keep
TIF_NEED_RESCHED_LAZY in the lower range. As a result one split load is
From: John Ogness
This commit contains addresses several build failures which were
reported by the kbuild test robot.
The fixes were folded into the original commits.
Reported-by: kbuild test robot
Signed-off-by: John Ogness
Signed-off-by: Sebastian Andrzej Siewior
Backport the commit from
Hello All,
Intel and WR YP QA is now working on QA execution for YP build 2.5.3.RC3. We
are planning to execute following tests for this cycle:
OEQA-Manual tests for following modules:
1. SDK
2. Eclipse-plugin
3. Kernel
4. Toaster
5. Bitbake (oe-core)
6.
On 4/9/19 8:44 PM, Sinan Kaya wrote:
> On 4/9/2019 7:49 AM, akuster wrote:
>> After closer look, I don't the "Upstream-Status:" nor a signoff in the
>> patch being added in the bb file.
>>
>> Does this issue affect later branches ?
>
> I can fix this. The issue was introduced while backporting
On 4/9/19 8:52 PM, Richard Purdie wrote:
> I'm sorry to have to say this but the project is terminating its
> official eclipse plugin support with immediate effect.
Does this affect the stable branches as well?
- armin
>
> There is nobody willing to keep the builds going, fix bugs, port to
On 4/9/19 9:09 PM, bruce.ashfi...@gmail.com wrote:
> From: Bruce Ashfield
>
> Updating poky-tiny to prefer 5.0 as the kernel version. Boot
> tested against qemux86 and qemuarm. This removes the last user
> of the 4.18 kernel, so we can queue it for removal from master.
Thanks Bruce.
- Armin
>
We are pleased to announce the third milestone release for Yocto Project 2.7
(yocto-2.7_M3) is available for download now.
Download:
http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-2.7_M3/
poky: 753e2a0ede4449917c75353b57f13bbafe70fac8
oecore:
Hi,
I'm facing some strange problems trying to backport old 1.9 Ruby to Thud Poky.
All packages build fine but the image's do_rootfs fails with below message and
without any image winding up in tmp/deploy/images/:
probably it has to be added to linker flags explicitly.
On Tue, Apr 9, 2019 at 12:00 AM Clement CHERBEIX
wrote:
>
> It's done but I keep the same problem, I've add zlib in the PACKAGECONFIG too
> without any result...
>
>
>
>
> De : Khem Raj
> Envoyé : lundi 8
Your recipes seem a bit off. Doesn't bitbake complain about them at all?
In your logger library you declare a dependency to
"texa-cmake-modules", not "cmake-modules". Also, assuming the naming
conflict is only present in pastebin versions of your recipes, in
cmake-modules.bb you add all files
From: Bruce Ashfield
Updating poky-tiny to prefer 5.0 as the kernel version. Boot
tested against qemux86 and qemuarm. This removes the last user
of the 4.18 kernel, so we can queue it for removal from master.
Signed-off-by: Bruce Ashfield
---
meta-poky/conf/distro/poky-tiny.conf | 2 +-
1
I'm sorry to have to say this but the project is terminating its
official eclipse plugin support with immediate effect.
There is nobody willing to keep the builds going, fix bugs, port to new
eclipse releases or release the current plugin. This has been raised in
many forums, multiple times and
On 4/9/2019 7:49 AM, akuster wrote:
After closer look, I don't the "Upstream-Status:" nor a signoff in the
patch being added in the bb file.
Does this issue affect later branches ?
I can fix this. The issue was introduced while backporting a CVE patch
from debian.
So, we are fixing a problem
On Mon, Apr 8, 2019 at 11:25 AM Paul Gortmaker
wrote:
>
> Bruce, Yocto kernel folks:
>
> Here is the next 4.18.x stable update "extension" primarily created
> for the Yocto project, continuing from the previous v4.18.33 release.
>
> There are just over 160 commits here, based on commits chosen
Current Dev Position: YP 2.7 M4 (New feature Freeze has begun.)
Next Deadline: YP 2.7 M3 Release Target was Mar. 8, 2019 and it should
release today!
SWAT Team Rotation:
* SWAT lead is currently: Amanda
* SWAT team rotation: Amanda -> Chen on Apr. 12, 2019
* SWAT team
Hi,
yes, following:
- cmake-modules.bb https://pastebin.com/5VqN9msS
- xxx-log.bb : https://pastebin.com/LYcPW3hc
The first one install the modules, thus is a dependency of many libraries,
the second one is a simple logger library that uses first's module
Thanks for your help,
Gabriele
Il
Most likely neither of these recipes actually provides a package named
'dhcp' or 'avahi'. Run 'bitbake -e avahi' and look for the PACKAGES
variable in the output, that would tell you the actual package names
that you can add to the image.
Alex
On Tue, 9 Apr 2019 at 16:16, Pandey, Kamal wrote:
>
Hello,
I was trying to add avahi and dhcp to my image. While running $bitbake dhcp
avahi, everything is working fine but when I add these packages to packagegroup
or directly to the image recipe using EXTRA_IMAGE_INSTALL or
IMAGE_INSTALL_append. It starts giving error.
The error for avahi
On 4/9/19 5:45 AM, Sinan Kaya wrote:
> On 3/29/2019 10:42 AM, Sinan Kaya wrote:
>> musl compilation has been broken since systemd: fix CVE-2018-6954.
>> Fixing this
>> by placing #ifdef for glob definition.
>>
>> Signed-off-by: Sinan Kaya
>
> I didn't see any comments here but I wanted to let
Hi,
The Marvell firmware sd8887_uapsta_a2 seems diff to the current sd8887_uapsta.
Thanks.
- jupiter
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
An upgrade should just be a matter of taking the meta-python recipe
and doing a version bump/checksum update. If you've written a recipe
from scratch then you're probably missing some of the glue required.
Ross
On Tue, 9 Apr 2019 at 11:17, Guenther Meyer wrote:
>
> On Tue, 9 Apr 2019 11:11:04
On Tue, 9 Apr 2019 11:11:04 +0100
"Burton, Ross" wrote:
> So for me they're in python3-twisted-core on target, and if you have
> the right DEPENDS then it should be there for build time.
I will have a look at this, when I'm back in the office again.
The thing is, I needed a newer version of
On Tue, 9 Apr 2019, Burton, Ross wrote:
> On Tue, 9 Apr 2019 at 11:14, Robert P. J. Day wrote:
> > so, to confirm what i thought, this is a bug in gnulib which
> > suggests i should dig through the build configuration to see where i
> > can, say, set a PREFERRED_VERSION of a newer version of
On Tue, 9 Apr 2019 at 11:14, Robert P. J. Day wrote:
> so, to confirm what i thought, this is a bug in gnulib which
> suggests i should dig through the build configuration to see where i
> can, say, set a PREFERRED_VERSION of a newer version of gnulib that
> no longer has tat bug? or, barring
On Mon, 8 Apr 2019, Burton, Ross wrote:
> Looks like that bug in gnulib that broke m4 (and others) when glibc
> changed.
>
> Fixed upstream
> https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=4af4a4a718
> and oe-core master/thud/possibly sumo also carry the relevant patch
> for m4.
>
> If
So for me they're in python3-twisted-core on target, and if you have
the right DEPENDS then it should be there for build time.
Ross
On Tue, 9 Apr 2019 at 11:03, Guenther Meyer wrote:
>
> On Tue, 9 Apr 2019 10:55:38 +0100
> "Burton, Ross" wrote:
>
> > Specifically for twisted, do you mean these
On Tue, 9 Apr 2019 10:55:38 +0100
"Burton, Ross" wrote:
> Specifically for twisted, do you mean these files:
>
> python3-twisted-core:
>
> /usr/lib/python3.7/site-packages/Twisted-18.4.0-py3.7.egg-info/PKG-INFO
>
>
Specifically for twisted, do you mean these files:
python3-twisted-core:
/usr/lib/python3.7/site-packages/Twisted-18.4.0-py3.7.egg-info/PKG-INFO
/usr/lib/python3.7/site-packages/Twisted-18.4.0-py3.7.egg-info/SOURCES.txt
On Fri, 5 Apr 2019 18:17:43 +0100
"Burton, Ross" wrote:
> What metadata in particular do you refer to?
The *egg-info folders and everything contained in them, especially
the files PKG-INFO or METADATA. The recipes are basically identical.
Some packages have it, some not:
32 matches
Mail list logo
