-e
A release candidate build for yocto-2.1_M2.rc1 is now available at:
http://autobuilder.yoctoproject.org/pub/releases/yocto-2.1_M2.rc1
Please begin QA on this build as soon as possible.
Build hash information:
meta-intel : b42a7e91320a75871b30ec851d6ec02711bbad0d
meta-fsl-arm : c1a4b18f
Hello,
If a recipe has a missing build dependency that the sysroot just
happens to contain anyway from an earlier build, then the build will
succeed only to fail later when the sysroot no longer has the build
dependency. We want to avoid that, so we're looking for ways to
automatically check for u
On Wed, Jan 27, 2016 at 03:45:30PM +0100, Ulf Magnusson wrote:
> Hello,
>
> If a recipe has a missing build dependency that the sysroot just
> happens to contain anyway from an earlier build, then the build will
> succeed only to fail later when the sysroot no longer has the build
> dependency. We
On 27 January 2016 at 14:45, Ulf Magnusson wrote:
> The only method I know of at the moment is to remove or rename tmp/ so
> that the build uses a fresh sysroot and then trying to rebuild the
> recipe. Is there something nicer? I think I remember reading about a
> script for testing for missing b
On Wed, Jan 27, 2016 at 3:59 PM, Martin Jansa wrote:
> On 27 January 2016 at 14:45, Ulf Magnusson wrote:
>> ...
> See openembedded-core/scripts/test-dependencies.sh but it basically
> automates rebuilding recipes after removing TMPDIR, but also it detects
> autodetected dependencies.
>
> Regards,
On 27 January 2016 at 15:29, Ulf Magnusson wrote:
> 1) Why does test-dependencies.sh remove TMPDIR instead of just wiping the
> sysroots?
>
For the thorough testing that test-dependencies does you could argue that
entirely wiping tmpdir ensures that the builds are done from clean.
2) Is t
The lsof recipe needs to be excluded from our checkuri tests because the
upstream FTP server refuses to let the autobuilder machines connect to it.
Also run checkuri against universe instead of world to catch more variations on
recipe permuatations.
Signed-off-by: Ross Burton
---
buildset-confi
Hi!
The first time I tried to upgrade my build to Jethro I received the following
error message while do_compiling krb5:
(...)
|
.build/tmp/sysroots/x86_64-linux/usr/libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/5.2.0/ld:
plugins.so: relocation R_X86_64_PC32 against symbol `krb5int_open_plug
Hi.
Thank you in advance for your support.
I'm using Yocto project Linux for the iMX6 CPU and imx6ulevk board.
I think that I have a problem with image size. I've seen the basic image
for that board and it's size was about 6Mb, but it didn't contain any
graphical library.
I need a basic graphical
Enviado desde mi iPhone
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
If you are planning to attend the Embedded Linux Conference in San
Diego this April, I wanted to let you know about the Yocto Project
Developer Day that the team is planning. This will be similar to
previous DevDays, with hands-on training in both introductory and
advanced tracks. The day will happ
On 27 January 2016 at 15:54, Ross Burton wrote:
> The lsof recipe needs to be excluded from our checkuri tests because the
> upstream FTP server refuses to let the autobuilder machines connect to it.
>
> Also run checkuri against universe instead of world to catch more variations
> on
> recipe pe
On 01/27/2016 10:15 AM, Jeff Osier-Mixon wrote:
> If you are planning to attend the Embedded Linux Conference in San
> Diego this April, I wanted to let you know about the Yocto Project
> Developer Day that the team is planning. This will be similar to
> previous DevDays, with hands-on training i
On Tue, Jan 26, 2016 at 7:09 PM, 张健 wrote:
> But I have no idea what's inside the .img files, and how to let my fpga
> board to understand the .img files.
>
> So this is reason why I'm here to ask you guys for some help.
>
> And wish to know if it is possible to port the "yocto" to my own projec
On Sat, Jan 23, 2016 at 6:12 AM, Max Sht wrote:
> Hi.
>
> Thank you in advance for your support.
> I'm using Yocto project Linux for the iMX6 CPU and imx6ulevk board.
>
> I think that I have a problem with image size. I've seen the basic image for
> that board and it's size was about 6Mb, but it d
On Wed, Jan 27, 2016 at 11:11 AM, Alexandre Freire da Silva Osorio
wrote:
> Hi!
>
> The first time I tried to upgrade my build to Jethro I received the following
> error message while do_compiling krb5:
>
> (...)
> |
> .build/tmp/sysroots/x86_64-linux/usr/libexec/x86_64-poky-linux/gcc/x86_64-pok
Hi,
Thanks to Guiseppe Pagano, there is a solution for this issue. It is
more a hot fix than a real solution but this is maybe for someone else
helpful.
> Hi Crhistian,
> It is not a clean patch, but it works for me.
>
> File:kernel_imx_3.14/Makefile
>
> - $(Q)$(MAKE) -f $(srctree)/Makefile
On 01/27/2016 07:49 PM, akuster wrote:
>
>
> On 01/27/2016 10:15 AM, Jeff Osier-Mixon wrote:
>> If you are planning to attend the Embedded Linux Conference in San
>> Diego this April, I wanted to let you know about the Yocto Project
>> Developer Day that the team is planning. This will be similar
Dear community,
I am using Freescale's SDK 1.8 based on poky 1.6.2.
How can extract SDK that supports building of both 32 and 64 bit applications?
I defined configuration for my board to be 32 bit with 64 bit kernel and
extracted SDK for application development.
Everything works fine: I can bui
19 matches
Mail list logo
