Re: [yocto] [meta-mingw][PATCH] mingw32-common: change mingw sdk to .zip type

[Changqing Li]

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 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/
so change to .zip type

Also tried to use option --dereference of tar which use means:
"follow symlinks; archive and dump the files they point to"
with this option, when archive it will deal with symlink to hard link,
but windows not support hard link, so drop this solution,
and use .zip for windows.

Signed-off-by: Changqing Li 
---
  conf/machine-sdk/include/mingw32-common.inc | 5 +
  1 file changed, 5 insertions(+)

diff --git a/conf/machine-sdk/include/mingw32-common.inc 
b/conf/machine-sdk/include/mingw32-common.inc
index 9011ded..dbad50a 100644
--- a/conf/machine-sdk/include/mingw32-common.inc
+++ b/conf/machine-sdk/include/mingw32-common.inc
@@ -46,3 +46,8 @@ GCCPIE_mingw32 = ""
  # wine and wineserver are required to test MinGW SDKs
  HOSTTOOLS += "${@'wine wineserver' if (bb.utils.contains_any('IMAGE_CLASSES', 'testsdk', True, False, d) or 
any(x in (d.getVar("BBINCLUDED") or "") for x in ["testsdk.bbclass"])) else ''}"

+# mingw sdk use .zip type
+SDK_TAR_TYPE = "zip"
+SDK_TAR_DEPENDS = "zip-native"
+SDK_TAR_CMD ?= "zip -r  ${SDKDEPLOYDIR}/${TOOLCHAIN_OUTPUTNAME}.${SDK_TAR_TYPE} 
."
+


You will also need to update the QA tests, since right now they expecting a tar 
file (lib/oeqa/sdkmingw/testsdk.py)


--

2.7.4

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


--
BRs

Sandy(Li Changqing)

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[linux-yocto] Error: base-files/3.0.14-r89/temp/run.do_install.80432: Syntax error: Unterminated quoted string

[srinivasan]

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 "ubuntu-18.04" has not been validated with
this version of the build system; you may possibly experience
unexpected failures. It is recommended that you use a tested
distribution.
Loading cache: 100%
|###|
Time: 0:00:00
Loaded 3196 entries from dependency cache.
Parsing recipes: 100%
|#|
Time: 0:00:02
Parsing of 2298 .bb files complete (2284 cached, 14 parsed). 3202
targets, 398 skipped, 6 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.38.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "aarch64-poky-linux"
MACHINE  = "imx8mmevk"
DISTRO   = "custom-TRK"
DISTRO_VERSION   = "${custom_DISTRO_VERSION}"
TUNE_FEATURES= "aarch64"
TARGET_FPU   = ""
meta-traktor-imx8= "sumo:4b25c1ee6896b5447f8502f13c28570341505360"
meta-traktor = "sumo:818be7ec4f768ba485e437dc26beb7bdc4b8120a"
meta-qt5 = "qt-5.11:ff6127ddd318d422f595295d1c189a86b3032873"
meta-custom= "sumo:d98452914e201d46a6b1360ca957d9b3e396b31f"
meta-freescale   = "HEAD:1deea6b4a2f83521ff247ea4743d09cc705ecd8e"
meta
meta-poky= "sumo:623b77885051174d0e05198843e739110977bd18"
meta-oe
meta-python
meta-networking  = "sumo:8760facba1bceb299b3613b8955621ddaa3d4c3f"
meta-bsp
meta-sdk = "HEAD:1de93d3d5128b8422c23a87cb8b54149e2bfb942"

Initialising tasks: 100%
|##|
Time: 0:00:02
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: base-files-3.0.14-r89 do_install: Function failed: do_install
(log file is located at
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/log.do_install.80432)
ERROR: Logfile of failure stored in:
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/log.do_install.80432
Log data follows:
| DEBUG: Executing python function extend_recipe_sysroot
| NOTE: Direct dependencies are
['/home/srinishanmugam/customBuild_test_rpi/custom/sources/poky/meta/recipes-devtools/quilt/quilt-native_0.65.bb:do_populate_sysroot',
'virtual:native:/home/srinishanmugam/customBuild_test_rpi/custom/sources/poky/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot']
| NOTE: Installed into sysroot: []
| NOTE: Skipping as already exists in sysroot: ['quilt-native', 'pseudo-native']
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_install
| 
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/run.do_install.80432:
176: 
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/run.do_install.80432:
Syntax error: Unterminated quoted string
| WARNING: exit code 2 from a shell command.
| ERROR: Function failed: do_install (log file is located at
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/log.do_install.80432)
ERROR: Task 
(/home/srinishanmugam/customBuild_test_rpi/custom/sources/poky/meta/recipes-core/base-files/base-files_3.0.14.bb:do_install)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 1256 tasks of which 1204 didn't need to
be rerun and 1 failed.

Summary: 1 task failed:
  
/home/srinishanmugam/customBuild_test_rpi/custom/sources/poky/meta/recipes-core/base-files/base-files_3.0.14.bb:do_install
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
srinishanmugam@ni-bln-07594:~/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8$


Kindly do the needful,
Many Thanks in advance
-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org

[Yocto-bsp] Error: base-files/3.0.14-r89/temp/run.do_install.80432: Syntax error: Unterminated quoted string

[srinivasan]

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 "ubuntu-18.04" has not been validated with
this version of the build system; you may possibly experience
unexpected failures. It is recommended that you use a tested
distribution.
Loading cache: 100%
|###|
Time: 0:00:00
Loaded 3196 entries from dependency cache.
Parsing recipes: 100%
|#|
Time: 0:00:02
Parsing of 2298 .bb files complete (2284 cached, 14 parsed). 3202
targets, 398 skipped, 6 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION   = "1.38.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING  = "universal"
TARGET_SYS   = "aarch64-poky-linux"
MACHINE  = "imx8mmevk"
DISTRO   = "custom-TRK"
DISTRO_VERSION   = "${custom_DISTRO_VERSION}"
TUNE_FEATURES= "aarch64"
TARGET_FPU   = ""
meta-traktor-imx8= "sumo:4b25c1ee6896b5447f8502f13c28570341505360"
meta-traktor = "sumo:818be7ec4f768ba485e437dc26beb7bdc4b8120a"
meta-qt5 = "qt-5.11:ff6127ddd318d422f595295d1c189a86b3032873"
meta-custom= "sumo:d98452914e201d46a6b1360ca957d9b3e396b31f"
meta-freescale   = "HEAD:1deea6b4a2f83521ff247ea4743d09cc705ecd8e"
meta
meta-poky= "sumo:623b77885051174d0e05198843e739110977bd18"
meta-oe
meta-python
meta-networking  = "sumo:8760facba1bceb299b3613b8955621ddaa3d4c3f"
meta-bsp
meta-sdk = "HEAD:1de93d3d5128b8422c23a87cb8b54149e2bfb942"

Initialising tasks: 100%
|##|
Time: 0:00:02
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: base-files-3.0.14-r89 do_install: Function failed: do_install
(log file is located at
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/log.do_install.80432)
ERROR: Logfile of failure stored in:
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/log.do_install.80432
Log data follows:
| DEBUG: Executing python function extend_recipe_sysroot
| NOTE: Direct dependencies are
['/home/srinishanmugam/customBuild_test_rpi/custom/sources/poky/meta/recipes-devtools/quilt/quilt-native_0.65.bb:do_populate_sysroot',
'virtual:native:/home/srinishanmugam/customBuild_test_rpi/custom/sources/poky/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot']
| NOTE: Installed into sysroot: []
| NOTE: Skipping as already exists in sysroot: ['quilt-native', 'pseudo-native']
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_install
| 
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/run.do_install.80432:
176: 
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/run.do_install.80432:
Syntax error: Unterminated quoted string
| WARNING: exit code 2 from a shell command.
| ERROR: Function failed: do_install (log file is located at
/home/srinishanmugam/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8/tmp/work/imx8mmevk-poky-linux/base-files/3.0.14-r89/temp/log.do_install.80432)
ERROR: Task 
(/home/srinishanmugam/customBuild_test_rpi/custom/sources/poky/meta/recipes-core/base-files/base-files_3.0.14.bb:do_install)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 1256 tasks of which 1204 didn't need to
be rerun and 1 failed.

Summary: 1 task failed:
  
/home/srinishanmugam/customBuild_test_rpi/custom/sources/poky/meta/recipes-core/base-files/base-files_3.0.14.bb:do_install
Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
srinishanmugam@ni-bln-07594:~/customBuild_test_rpi/custom/buid_test3_customtrk_distro_imx8$


Kindly do the needful,
Many Thanks in advance
-- 
___
yocto-bsp mailing list
yocto-bsp@yoctoproject.org

[yocto] [rocko] python3-pycario : Waf cannot unpacked

[Geonho Kim]

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: bunzip2: not found
| Error: Waf cannot be unpacked, check that bzip2 support is preset.
..

It seems that uninstalled bzip2 to host and sysroot-native area, but bzip2
was installed to
host pc and sysroot-native location.

Do you know how to fix this?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to share buildhistory?

[Stephen Lawrence]

> -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, sometimes I need to keep on
> the development with PC2, placed in my customer's office.
> 
> But I need to continue on PC2 where I stopped with PC1
> 

It is not quite what you describe but you can use SSTATE_MIRRORS [1] to use 
cached data
objects on the other PC. So if you pointed the mirror on PC2 at PC1, PC2 would 
check
the cache on PC1 before building it locally.

[1] 
https://www.yoctoproject.org/docs/2.6/ref-manual/ref-manual.html#var-SSTATE_MIRRORS

Regards

Steve
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Firewalld failing to build

[Randy MacLeod]

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 ../html/firewall-cmd.html --nonet --xinclude  
transform-html.xsl firewall-cmd.xml
| xsltproc -o ../html/firewalld.dbus.html --nonet --xinclude  
transform-html.xsl 
../../../../../../../../workspace/sources/firewalld/doc/xml/firewalld.dbus.xml
| xsltproc -o ../html/firewalld.conf.html --nonet --xinclude  
transform-html.xsl 
../../../../../../../../workspace/sources/firewalld/doc/xml/firewalld.conf.xml
| xsltproc -o ../html/firewalld.html --nonet --xinclude  
transform-html.xsl firewalld.xml

| 134 translated messages, 281 untranslated messages.
| bn_IN: 293 translated messages, 122 untranslated messages.
| ca: 415 translated messages.
| cs: 415 translated messages.
| da: warning: failed to load external entity "authors.xml"
| firewall-cmd.xml:36: parser error : Failure to process entity authors
|     
|              ^
| firewall-cmd.xml:36: parser error : Entity 'authors' not defined
|     
|              ^
| warning: failed to load external entity "seealso.xml"
| firewall-cmd.xml:2297: parser error : Failure to process entity seealso
|   
|            ^
| firewall-cmd.xml:2297: parser error : Entity 'seealso' not defined
|   

Thanks
Sam.



Hi Sam,

Can you post your recipe?

Do you have all the dependencies listed on:
   https://github.com/firewalld/firewalld

What branch & commit are you based on?

When we looked at adding a firewalld recipe 3+ years ago
it didn't work out since the package wasn't cross-compile
friendly but things have changed since then so I'm looking
forward to see what can be achieved.


--
# Randy MacLeod
# Wind River Linux
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] How to share buildhistory?

[Mauro Ziliani]

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 PC2 I pull from git repos

- I bitbake app_1.0.bb and I would get app_1.0-r0.4_armhf.deb


Is it possible to do that?


Often I work with PC1 placed in my office, sometimes I need to keep on
the development with PC2, placed in my customer's office.

But I need to continue on PC2 where I stopped with PC1


Best regards,

 MZ
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] make-mod-scripts

[Russell Peterson]

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 artifacts
directory gets wiped out.  While the build artifacts directory does get
rebuilt, make-mod-scripts:do_configure is never triggered because it
doesn't think anything changed.  This breaks the module build because it
can't find auto.conf.

I think I can nostamp make-mod-scripts for now but is there a more elegant,
efficient solution here?  Seems like make-mod-scripts is designed to only
build once.

Regards,

Russell
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Community support for any Yocto release

[Mark Hatle]

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?

Generally it takes 6 months development between releases.  So the rough estimate
1 year of general updates from the community as a whole.  Sometimes it takes
slightly longer (or slightly less) then 6 months for the next release, and that
will then adjust the time scales for the prior version slightly as well.

One thing to keeo in mind for 'community support'.  "Support" is not intended to
be in the commercial sense, where there are specific fix time frames, etc.  It
just means there is an assigned maintainer and QA resources for that version
during that time.  It's still up to developers to send fixes for issues
encountered to the maintainers to get the issues fixed.

If you need a level of more dedicated support (time frame, resources, etc), you
should look for a commercial Yocto Project member.

--Mark

> Regards,
> Gaurang
> 
> On Wed, Jan 16, 2019 at 9:50 AM Nicolas Dechesne  > wrote:
> 
> 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
> how long this will be supported by community?
> 
> Sorry, if this information is already present on some wiki page, but I
> am not able to find it. So pointer to that wiki page will really help.
> 
> 
> This information is indeed available her:
> https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance
> 
> "Typically, alongside the latest release the previous two releases are 
> also
> maintained."
>  
> 
> 
> Regards,
> Gaurang Shastri
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org 
> https://lists.yoctoproject.org/listinfo/yocto
> 
> 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-mingw][PATCH] mingw32-common: change mingw sdk to .zip type

[Burton, Ross]

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
>> 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 use option --dereference of tar which use means:
>> "follow symlinks; archive and dump the files they point to"
>> with this option, when archive it will deal with symlink to hard link,
>> but windows not support hard link, so drop this solution,
>> and use .zip for windows.
>>
>> Signed-off-by: Changqing Li 
>> ---
>>  conf/machine-sdk/include/mingw32-common.inc | 5 +
>>  1 file changed, 5 insertions(+)
>>
>> diff --git a/conf/machine-sdk/include/mingw32-common.inc 
>> b/conf/machine-sdk/include/mingw32-common.inc
>> index 9011ded..dbad50a 100644
>> --- a/conf/machine-sdk/include/mingw32-common.inc
>> +++ b/conf/machine-sdk/include/mingw32-common.inc
>> @@ -46,3 +46,8 @@ GCCPIE_mingw32 = ""
>>  # wine and wineserver are required to test MinGW SDKs
>>  HOSTTOOLS += "${@'wine wineserver' if 
>> (bb.utils.contains_any('IMAGE_CLASSES', 'testsdk', True, False, d) or any(x 
>> in (d.getVar("BBINCLUDED") or "") for x in ["testsdk.bbclass"])) else ''}"
>>
>> +# mingw sdk use .zip type
>> +SDK_TAR_TYPE = "zip"
>> +SDK_TAR_DEPENDS = "zip-native"
>> +SDK_TAR_CMD ?= "zip -r  
>> ${SDKDEPLOYDIR}/${TOOLCHAIN_OUTPUTNAME}.${SDK_TAR_TYPE} ."
>> +
>
>
> You will also need to update the QA tests, since right now they expecting a 
> tar file (lib/oeqa/sdkmingw/testsdk.py)
>
>> --
>>
>> 2.7.4
>>
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-mingw][PATCH] mingw32-common: change mingw sdk to .zip type

[Joshua Watt]

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/
> so change to .zip type
>
> Also tried to use option --dereference of tar which use means:
> "follow symlinks; archive and dump the files they point to"
> with this option, when archive it will deal with symlink to hard link,
> but windows not support hard link, so drop this solution,
> and use .zip for windows.
>
> Signed-off-by: Changqing Li 
> ---
>  conf/machine-sdk/include/mingw32-common.inc | 5 +
>  1 file changed, 5 insertions(+)
>
> diff --git a/conf/machine-sdk/include/mingw32-common.inc
> b/conf/machine-sdk/include/mingw32-common.inc
> index 9011ded..dbad50a 100644
> --- a/conf/machine-sdk/include/mingw32-common.inc
> +++ b/conf/machine-sdk/include/mingw32-common.inc
> @@ -46,3 +46,8 @@ GCCPIE_mingw32 = ""
>  # wine and wineserver are required to test MinGW SDKs
>  HOSTTOOLS += "${@'wine wineserver' if
> (bb.utils.contains_any('IMAGE_CLASSES', 'testsdk', True, False, d) or any(x
> in (d.getVar("BBINCLUDED") or "") for x in ["testsdk.bbclass"])) else ''}"
>
> +# mingw sdk use .zip type
> +SDK_TAR_TYPE = "zip"
> +SDK_TAR_DEPENDS = "zip-native"
> +SDK_TAR_CMD ?= "zip -r
> ${SDKDEPLOYDIR}/${TOOLCHAIN_OUTPUTNAME}.${SDK_TAR_TYPE} ."
> +
>

You will also need to update the QA tests, since right now they expecting a
tar file (lib/oeqa/sdkmingw/testsdk.py)

--

2.7.4
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH] README: remove mentions of distrodata, as AUH no longer uses it

[Alexander Kanavin]

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;
it can be used as-is, or tweaked further.
 
-3. Enable distrodata and supply appropriate additional metadata. For
-   example, you could add the following to your conf/local.conf:
-
 snip ---
-INHERIT =+ "distrodata"
 snip ---
-
 WARNING: if you are using the default maintainers.inc file supplied
  with Poky (in meta-yocto) and you don't set a
  maintainers_whitelist or (global_)maintainer_override in the
@@ -57,7 +50,7 @@ BUILDHISTORY_COMMIT = "1"
 If upgrade is succesful buildhistory diff's are generated into
 $BUILDDIR/upgrade-helper/work/recipe/buildhistory-diff.txt.
 
-(Do not remove any other inherited class in the process, e.g. distrodata).
+(Do not remove any other inherited class in the process).
 
 5. If you want to enable testimage (optional) you need to enable in
 upgrade-helper.conf also add the following lines to your conf/local.conf
@@ -76,7 +69,7 @@ a vncserver example:
 $ vncserver :1
 $ export DISPLAY=:1
 
-(Do not remove any other inherited class in the process, e.g. distrodata).
+(Do not remove any other inherited class in the process).
 
 Usage
 -
-- 
2.17.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-mingw][PATCH] mingw32-common: change mingw sdk to .zip type

[changqing.li]

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 use option --dereference of tar which use means:
"follow symlinks; archive and dump the files they point to"
with this option, when archive it will deal with symlink to hard link,
but windows not support hard link, so drop this solution,
and use .zip for windows.

Signed-off-by: Changqing Li 
---
 conf/machine-sdk/include/mingw32-common.inc | 5 +
 1 file changed, 5 insertions(+)

diff --git a/conf/machine-sdk/include/mingw32-common.inc 
b/conf/machine-sdk/include/mingw32-common.inc
index 9011ded..dbad50a 100644
--- a/conf/machine-sdk/include/mingw32-common.inc
+++ b/conf/machine-sdk/include/mingw32-common.inc
@@ -46,3 +46,8 @@ GCCPIE_mingw32 = ""
 # wine and wineserver are required to test MinGW SDKs
 HOSTTOOLS += "${@'wine wineserver' if (bb.utils.contains_any('IMAGE_CLASSES', 
'testsdk', True, False, d) or any(x in (d.getVar("BBINCLUDED") or "") for x in 
["testsdk.bbclass"])) else ''}"
 
+# mingw sdk use .zip type
+SDK_TAR_TYPE = "zip"
+SDK_TAR_DEPENDS = "zip-native"
+SDK_TAR_CMD ?= "zip -r  
${SDKDEPLOYDIR}/${TOOLCHAIN_OUTPUTNAME}.${SDK_TAR_TYPE} ."
+
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Community support for any Yocto release

[Gaurang Shastri]

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 Dechesne <
nicolas.deche...@linaro.org> wrote:

> 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
>> how long this will be supported by community?
>>
>> Sorry, if this information is already present on some wiki page, but I am
>> not able to find it. So pointer to that wiki page will really help.
>>
>
> This information is indeed available her:
> https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance
>
> "Typically, alongside the latest release the previous two releases are
> also maintained."
>
>
>>
>> Regards,
>> Gaurang Shastri
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Community support for any Yocto release

[Nicolas Dechesne]

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 how
> long this will be supported by community?
>
> Sorry, if this information is already present on some wiki page, but I am
> not able to find it. So pointer to that wiki page will really help.
>

This information is indeed available her:
https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance

"Typically, alongside the latest release the previous two releases are also
maintained."


>
> Regards,
> Gaurang Shastri
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Community support for any Yocto release

[Gaurang Shastri]

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 already present on some wiki page, but I am
not able to find it. So pointer to that wiki page will really help.

Regards,
Gaurang Shastri
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto