Ross and Joshua, thanks for your comments, I will send a v2 later.
On 1/16/19 9:17 PM, Burton, Ross wrote:
Just in case you hadn't noticed, that this depends on a corresponding
patch to oe-core, which I've comments on.
Ross
On Wed, 16 Jan 2019 at 13:14, Joshua Watt wrote:
On Wed, Jan
Dear Yocto Experts,
I am trying to customize my vendor specific Yocto BSP's to my custom
OS. I am facing the below error, could you please do the needful or
provide me some pointers from your end for solving this issue
Error:
$ bitbake fsl-image-validation-imx
WARNING: Host distribution
Dear Yocto Experts,
I am trying to customize my vendor specific Yocto BSP's to my custom
OS. I am facing the below error, could you please do the needful or
provide me some pointers from your end for solving this issue
Error:
$ bitbake fsl-image-validation-imx
WARNING: Host distribution
Hi,
I have some build error.
Now, I have working on rocko release.
When I have built python3-pycairo, I met this error message
build_src/tmp/work/aarch64-poky-linux/python3-pycairo/1.10.0-r2/temp/log.do_configure.81617
Log data follows:
| DEBUG:Executing shell function do_configure
| sh :1:
> -Original Message-
> From: yocto-boun...@yoctoproject.org On
> Behalf
> Of Mauro Ziliani
> Sent: 16 January 2019 15:31
> To: yocto@yoctoproject.org
> Subject: [yocto] How to share buildhistory?
[snip]
>
> Is it possible to do that?
>
>
> Often I work with PC1 placed in my office,
On 1/16/19 12:47 AM, Sam Zeter wrote:
Hello all,
I've been attempting to build firewalld by adding it through 'devtool
add ' and then 'devtool build firewalld'. However, I am stuck with the
following errors. I have no idea what could be causing this. Could
someone please help?
xsltproc -o
Hi all.
I'm working with imx6dlsabresd and krogoth with 2 pc (PC1, PC2) which
commit the sources in the same git repository
I need to share buildhistory between PC1 and PC2.
That is:
- I build app_1.0.bb on PC1 and I get app_1.0-r0.3_armhf.deb
- I commit/push from PC1 to the git repos.
- In
Hello,
We are seeing build failures every now and then regarding our out of tree
modules.
I have tracked the issue down to make-mod-scripts performing the make
oldconfig and prepare operations. Normally this works, however, if for
some reason a clean is done on the linux kernel, the build
On 1/16/19 2:58 AM, Gaurang Shastri wrote:
> Thanks Nicolas for the prompt answer and wiki page information.
>
> So as you said, "Typically, alongside the latest release the previous two
> releases are also maintained.", do you mean any release will be maintained
> for 1
> year by community?
Just in case you hadn't noticed, that this depends on a corresponding
patch to oe-core, which I've comments on.
Ross
On Wed, 16 Jan 2019 at 13:14, Joshua Watt wrote:
>
>
>
> On Wed, Jan 16, 2019, 3:37 AM >
>> From: Changqing Li
>>
>> Current sdk type is tar.xz, but for mingw sdk, since we
>>
On Wed, Jan 16, 2019, 3:37 AM From: Changqing Li
>
> Current sdk type is tar.xz, but for mingw sdk, since we
> have symlink under the sdk folder, 7zip which used to
> extract tar.xz cannot handle it, refer 7zip upstream bug:
> https://sourceforge.net/p/sevenzip/discussion/45797/thread/c71d6b96/
Signed-off-by: Alexander Kanavin
---
README | 11 ++-
1 file changed, 2 insertions(+), 9 deletions(-)
diff --git a/README b/README
index 4752dc6..cb9f87e 100644
--- a/README
+++ b/README
@@ -30,13 +30,6 @@ Setup
upgrade-helper.conf. A sample file is provided in AUH source tree;
From: Changqing Li
Current sdk type is tar.xz, but for mingw sdk, since we
have symlink under the sdk folder, 7zip which used to
extract tar.xz cannot handle it, refer 7zip upstream bug:
https://sourceforge.net/p/sevenzip/discussion/45797/thread/c71d6b96/
so change to .zip type
Also tried to
Thanks Nicolas for the prompt answer and wiki page information.
So as you said, "Typically, alongside the latest release the previous two
releases are also maintained.", do you mean any release will be maintained
for 1 year by community?
Regards,
Gaurang
On Wed, Jan 16, 2019 at 9:50 AM Nicolas
Hello,
On Wed, Jan 16, 2019 at 9:47 AM Gaurang Shastri wrote:
>
> Hi All,
>
> For how many years yocto community officially support any Yocto release?
> (This includes like bug fixes, CVE fixes, enhancements, etc etc)
>
> For example, the latest release happened on 11/15/2018 (Yocto 2.6), so
Hi All,
For how many years yocto community officially support any Yocto release?
(This includes like bug fixes, CVE fixes, enhancements, etc etc)
For example, the latest release happened on 11/15/2018 (Yocto 2.6), so how
long this will be supported by community?
Sorry, if this information is
16 matches
Mail list logo
