Date   

Building zeek 3.1.1 in Sumo

Gary Huband
 

I'm trying to create a recipe in Sumo for zeek (zeek.org) which uses cmake.  I'm getting a sed not found error:

Initialising tasks: 100% |#######################################################################################################################################################| Time: 0:00:01
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: zeek-3.1.1-r0 do_configure: Function failed: do_configure (log file is located at /opt/PHYTEC_BSPs19/yocto_imx7/build-msi1/tmp/work/cortexa7hf-neon-poky-linux-gnueabi/zeek/3.1.1-r0/temp/log.do_configure.18009)
ERROR: Logfile of failure stored in: /opt/PHYTEC_BSPs19/yocto_imx7/build-msi1/tmp/work/cortexa7hf-neon-poky-linux-gnueabi/zeek/3.1.1-r0/temp/log.do_configure.18009
Log data follows:
| DEBUG: Executing shell function do_configure
| -- The C compiler identification is GNU 7.3.0
| -- The CXX compiler identification is GNU 7.3.0
| -- Check for working C compiler: /opt/PHYTEC_BSPs19/yocto_imx7/build-msi1/tmp/work/cortexa7hf-neon-poky-linux-gnueabi/zeek/3.1.1-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc
| -- Check for working C compiler: /opt/PHYTEC_BSPs19/yocto_imx7/build-msi1/tmp/work/cortexa7hf-neon-poky-linux-gnueabi/zeek/3.1.1-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc -- works
| -- Detecting C compiler ABI info
| -- Detecting C compiler ABI info - done
| -- Detecting C compile features
| -- Detecting C compile features - done
| -- Check for working CXX compiler: /opt/PHYTEC_BSPs19/yocto_imx7/build-msi1/tmp/work/cortexa7hf-neon-poky-linux-gnueabi/zeek/3.1.1-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-g++
| -- Check for working CXX compiler: /opt/PHYTEC_BSPs19/yocto_imx7/build-msi1/tmp/work/cortexa7hf-neon-poky-linux-gnueabi/zeek/3.1.1-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-g++ -- works
| -- Detecting CXX compiler ABI info
| -- Detecting CXX compiler ABI info - done
| -- Detecting CXX compile features
| -- Detecting CXX compile features - done
| CMake Error at CMakeLists.txt:170 (message):
|   Could not find required dependency: sed

I tracked this down to the cmake find_program(), here's the lines in CMakeLists.txt:

########################################################################
## Dependency Configuration
 
include(FindRequiredPackage)
 
# Check cache value first to avoid displaying "Found sed" messages everytime
if (NOT SED_EXE)
    find_program(SED_EXE sed)
    if (NOT SED_EXE)
        message(FATAL_ERROR "Could not find required dependency: sed")
    else ()
        message(STATUS "Found sed: ${SED_EXE}")
    endif ()
endif ()

Any ideas how to fix this?


Re: bootsrap

Konrad Weihmann
 

On 18.04.20 16:16, Rakesh Kumar wrote:
Hi all,
Can anyone give me any guidance in creating recipe for any application which is having bootstrap.Here i am installing my application in /var directory and this application is having bootstrap that needs to execute after creating rootfs.Here is the steps which i am following.
do_install() {
        install -m 0755 -d  ${D}/var/
        cp -rf ${S}/  ${D}/var
}
do_install_append() {
 cd  ${D}/var/my_app/
 ./bootstrap
}
::DISCLAIMER::
------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.
------------------------------------------------------------------------


bootsrap

Rakesh Kumar
 

Hi all,


Can anyone give me any guidance in creating recipe for any application which is having bootstrap.Here i am installing my application in /var directory and this application is having bootstrap that needs to execute after creating rootfs.Here is the steps which i am following.


do_install() {
        install -m 0755 -d  ${D}/var/

        cp -rf ${S}/  ${D}/var
}

do_install_append() {

 cd  ${D}/var/my_app/
 ./bootstrap

}
::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.


Re: FYI: Why people are using #hashtags in yocto email subjects. #hashtags

Randy MacLeod
 

On 2020-04-17 4:09 a.m., Nicolas Dechesne wrote:
On Thu, Apr 16, 2020 at 9:36 PM Denys Dmytriyenko <denis@denix.org <mailto:denis@denix.org>> wrote:
I doubt people that actually send emails to the list use #hashtags.
But the new list server provides this posting feature for anyone to
address
the list and requests poster to add #hashtags - very annoying, indeed:
https://lists.yoctoproject.org/g/yocto/post
there is that. And looking at the history on the server, most of the existing tags came from the web. But a hashtag is created automatically when using '#' in the email subject. that's how #define was created:
https://lists.yoctoproject.org/g/yocto/message/48686
and this email created #hashtags ;-)
I haven't found a way to disable it.. from what I can see we can
1. force every message to have at least one hashtag...
2. bounce message with a new hashtag in $subject
3. remove new hashtag when used in $subject
I don't think we need to change anything.
I found it annoying at first because I didn't know about the
archive tagging feature.
I think we will need to do some tests to see what #3 does.. But in any case, I don't think we can prevent users from creating hashtags from the web..
Is that causing any issues with patches workflow?
I am not aware of any workflow problems.

../Randy
--
Denys
On Thu, Apr 16, 2020 at 03:18:34PM -0400, Randy MacLeod wrote:
> FYI:
>
> I don't know if I missed the memo/tweet about the email archive
feature
> but I just noticed that the new archive site will index emails
> by hashtag:
>
> https://lists.yoctoproject.org/g/yocto
>
> https://lists.yoctoproject.org/g/yocto/hashtags
>
> I thought it was an annoying new behaviour coming from Twitter users
> but now I understand why there are hashtags on my lawn^Hsubject
lines.
>
> ;-)
>
> --
> # Randy MacLeod
> # Wind River Linux

>

--
# Randy MacLeod
# Wind River Linux


[meta-openssl102][PATCH] conf/layer.conf: Set layer compatible with dunfell

Fabio Berton
 

Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
---
conf/layer.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/layer.conf b/conf/layer.conf
index c7dcd8a..30ef9c9 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -10,7 +10,7 @@ BBFILE_PRIORITY_meta-openssl-one-zero-two =3D "5"
=20
LAYERVERSION_meta-openssl-one-zero-two =3D "1"
=20
-LAYERSERIES_COMPAT_meta-openssl-one-zero-two =3D "thud warrior zeus"
+LAYERSERIES_COMPAT_meta-openssl-one-zero-two =3D "thud warrior zeus dunf=
ell"
=20
LAYERDEPENDS_meta-openssl-one-zero-two =3D " \
core \
--=20
2.26.1


Re: FYI: Why people are using #hashtags in yocto email subjects. #hashtags

Nicolas Dechesne
 



On Thu, Apr 16, 2020 at 9:36 PM Denys Dmytriyenko <denis@...> wrote:
I doubt people that actually send emails to the list use #hashtags.

But the new list server provides this posting feature for anyone to address
the list and requests poster to add #hashtags - very annoying, indeed:

https://lists.yoctoproject.org/g/yocto/post

there is that. And looking at the history on the server, most of the existing tags came from the web. But a hashtag is created automatically when using '#' in the email subject. that's how #define was created:

and this email created #hashtags ;-)

I haven't found a way to disable it.. from what I can see we can
1. force every message to have at least one hashtag...
2. bounce message with a new hashtag in $subject
3. remove new hashtag when used in $subject

I think we will need to do some tests to see what #3 does.. But in any case, I don't think we can prevent users from creating hashtags from the web..

Is that causing any issues with patches workflow?



--
Denys


On Thu, Apr 16, 2020 at 03:18:34PM -0400, Randy MacLeod wrote:
> FYI:
>
> I don't know if I missed the memo/tweet about the email archive feature
> but I just noticed that the new archive site will index emails
> by hashtag:
>
>    https://lists.yoctoproject.org/g/yocto
>
>    https://lists.yoctoproject.org/g/yocto/hashtags
>
> I thought it was an annoying new behaviour coming from Twitter users
> but now I understand why there are hashtags on my lawn^Hsubject lines.
>
> ;-)
>
> --
> # Randy MacLeod
> # Wind River Linux

>



Re: Guidance Downgrading Python2 in Zeus #python

MikeB
 

Thank you all.  The new layer did the trick for me also.

Regards, Mike

On Wed, Apr 15, 2020 at 12:33 PM McKay, Sean <sean.mckay@...> wrote:

FYI, we’re doing the same internally (vendor supplied FIPS supported openssl 1.0.2), and the layer Armin suggests worked for us on zeus with minimal additional tweaking.

 

Good luck!

-Sean

 

From: yocto@... <yocto@...> On Behalf Of akuster
Sent: Wednesday, April 15, 2020 9:23 AM
To: MikeB <mabnhdev@...>; yocto@...
Subject: Re: [yocto] Guidance Downgrading Python2 in Zeus #python

 

 

On 4/15/20 9:16 AM, MikeB wrote:

I'm working on a set of platforms that have a FIPs certified OpenSSL.  We are at version 1.0.2l.

I've found that the new version of python in Zeus (2.7.17) requires a newer version of OpenSSL (1.1).

We really don't want to go through a new round of certification, so we want to keep our current OpenSSL (1.0.2l).

I think the easiest solution is to downgrade python 2 back to the version used by Sumo (2.7.15).

I know how to downgrade simple recipes, but python is far from simple.

Can someone give me some guidance on how to approach the downgrade of python2 in Zeus?


Have had a chance to look at this layer?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-openssl102-fips/

- armin


Thanks, Mike

 

 


[meta-cgl][PATCH] initramfs-cgl-boot: Use common MIT license

Jeremy Puhlman
 

From: Jeremy Puhlman <jpuhlman@mvista.com>

Signed-off-by: Jeremy A. Puhlman <jpuhlman@mvista.com>
---
.../recipes-core/initrdscripts/initramfs-cgl-boot_1.0.bb | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/meta-cgl-common/recipes-core/initrdscripts/initramfs-cgl-boo=
t_1.0.bb b/meta-cgl-common/recipes-core/initrdscripts/initramfs-cgl-boot_=
1.0.bb
index 1a2dd1d..8b1768a 100644
--- a/meta-cgl-common/recipes-core/initrdscripts/initramfs-cgl-boot_1.0.b=
b
+++ b/meta-cgl-common/recipes-core/initrdscripts/initramfs-cgl-boot_1.0.b=
b
@@ -1,8 +1,7 @@
SUMMARY =3D "Support for having multipath iSCSI devices as root file sys=
tem"
LICENSE =3D "MIT"
-LIC_FILES_CHKSUM =3D "file://../COPYING.MIT;md5=3D838c366f69b72c5df05c96=
dff79b35f2"
+LIC_FILES_CHKSUM =3D "file://${COREBASE}/meta/COPYING.MIT;md5=3D3da9cfbc=
b788c80a0384361b4de20420"
SRC_URI =3D "file://init-boot.sh \
- file://COPYING.MIT \
"
=20
do_install() {
--=20
2.20.1


Re: FYI: Why people are using #hashtags in yocto email subjects. #hashtags

Denys Dmytriyenko
 

I doubt people that actually send emails to the list use #hashtags.

But the new list server provides this posting feature for anyone to address
the list and requests poster to add #hashtags - very annoying, indeed:

https://lists.yoctoproject.org/g/yocto/post

--
Denys

On Thu, Apr 16, 2020 at 03:18:34PM -0400, Randy MacLeod wrote:
FYI:

I don't know if I missed the memo/tweet about the email archive feature
but I just noticed that the new archive site will index emails
by hashtag:

https://lists.yoctoproject.org/g/yocto

https://lists.yoctoproject.org/g/yocto/hashtags

I thought it was an annoying new behaviour coming from Twitter users
but now I understand why there are hashtags on my lawn^Hsubject lines.

;-)

--
# Randy MacLeod
# Wind River Linux


FYI: Why people are using #hashtags in yocto email subjects. #hashtags

Randy MacLeod
 

FYI:

I don't know if I missed the memo/tweet about the email archive feature
but I just noticed that the new archive site will index emails
by hashtag:

https://lists.yoctoproject.org/g/yocto

https://lists.yoctoproject.org/g/yocto/hashtags

I thought it was an annoying new behaviour coming from Twitter users
but now I understand why there are hashtags on my lawn^Hsubject lines.

;-)

--
# Randy MacLeod
# Wind River Linux


Re: Building gutenprint recipe

Randy MacLeod
 

On 2018-07-07 6:02 a.m., Timm wrote:
There was a gutenprint recipe back in OE-Classic:
https://layers.openembedded.org/layerindex/oe-classic/recipe/12076/
But currently there is no gutenprint available for Yocto.
Timm,

Did you ever get the gutenprint recipe to work?
Are you able to add it to meta-oe or share
what you have done so far here?

../Randy
I tried to build my own recipe. But I got stuck at the stage where the
build process wants to call some generated binaries:
    | ./extract-strings `cat xml-stamp | sed -e
's;^;../../../gutenprint-5.2.11/src/xml/;'` > xmli18n-tmp.h.tmp
    | /lib/ld-linux-armhf.so.3: No such file or directory
So, I introduced a "native" recipe, which just compiles the
"extract-strings" for me:
----------------------------------------------------------------------------------------------------------
SECTION = "libs"
require gutenprint_${PV}.bb
DEPENDS = "gettext-native"
inherit native autotools
EXTRA_OECONG = "\
        --disable-libgutenprintui2 \
            --disable-samples \
        --without-gimp2 \
        --without-doc \
        --disable-nls \
        --disable-nls-macos \
        --without-foomatic \
        --without-foomatic3 \
        --disable-escputil \
        --disable-test \
        --disable-testpattern \
        --without-cups \
               "
do_compile() {
    oe_runmake -C src/xml/ extract-strings
}
-----------------------------------------------------------------------------------------------------------------
The next step is quite unclear for me? How can I tell the build system
not to generate the extract-strings again and use the native instead?
As reference I used the build scripts from openwrt and buildroot. But
I'm not able to translate this build steps to Yocto.
https://github.com/FranciscoBorges/openwrt-printing-packages/blob/master/net/gutenprint/Makefile
https://github.com/buildroot/buildroot/blob/master/package/gutenprint/gutenprint.mk

--
# Randy MacLeod
# Wind River Linux


[patchtest-oe][PATCH] test_mbox_mailinglist: Correct suggested mailing lists for docs and poky

Peter Kjellerstedt
 

A new mailing list was recently introduced for documentation related
discussions including patches. And the domain for Yocto mailing lists
was changed with the migration to groups.io.

Change-Id: If687dcbaef4adf128196d8c80f3ea8b1b31b7738
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
---
tests/test_mbox_mailinglist.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tests/test_mbox_mailinglist.py b/tests/test_mbox_mailinglist.py
index e5700b4..d2781af 100644
--- a/tests/test_mbox_mailinglist.py
+++ b/tests/test_mbox_mailinglist.py
@@ -38,8 +38,8 @@ class MailingList(base.Base):
Project = collections.namedtuple('Project', ['name', 'listemail', 'gitrepo', 'paths'])

bitbake = Project(name='Bitbake', listemail='bitbake-devel@lists.openembedded.org', gitrepo='http://git.openembedded.org/bitbake/', paths=paths['bitbake'])
- doc = Project(name='Documentantion', listemail='yocto@yoctoproject.org', gitrepo='http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/', paths=paths['documentation'])
- poky = Project(name='Poky', listemail='poky@yoctoproject.org', gitrepo='http://git.yoctoproject.org/cgit/cgit.cgi/poky/', paths=paths['poky'])
+ doc = Project(name='Documentantion', listemail='docs@lists.yoctoproject.org', gitrepo='http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/', paths=paths['documentation'])
+ poky = Project(name='Poky', listemail='poky@lists.yoctoproject.org', gitrepo='http://git.yoctoproject.org/cgit/cgit.cgi/poky/', paths=paths['poky'])
oe = Project(name='oe', listemail='openembedded-devel@lists.openembedded.org', gitrepo='http://git.openembedded.org/meta-openembedded/', paths=paths['oe'])


--
2.21.1


Re: QA notification for completed autobuilder build (yocto-3.1.rc2)

Richard Purdie
 

On Wed, 2020-04-15 at 16:05 -0700, akuster wrote:


On 4/15/20 3:25 PM, Paul Eggleton wrote:
Release notes draft attached, including a dedication to Scott
(wasn't sure where to put that so I've just left it at the top) and
contributors list. Let me know if you notice anything
missing/incorrect.
Thanks for pulling this together.
I've also sent out the 3.1 migration guide for the reference
manual, Richard has just merged the changes:
I see the review window is down to an hour before merging. Is code
review by twitter the next new thing ; )
It was merged on the basis it was a good starter and followup patches
are easy and very welcome.

Cheers,

Richard


Re: QA notification for completed autobuilder build (yocto-3.1.rc2)

Armin Kuster
 



On 4/15/20 3:25 PM, Paul Eggleton wrote:
Release notes draft attached, including a dedication to Scott (wasn't sure where to put that so I've just left it at the top) and contributors list. Let me know if you notice anything missing/incorrect. 
Thanks for pulling this together.

I've also sent out the 3.1 migration guide for the reference manual, Richard has just merged the changes:
I see the review window is down to an hour before merging. Is code review by twitter the next new thing ; )

 I responded the patches on the docs list.

- armin


  http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=dunfell&id=c31ddaba1f3181c577fdaa3ce519a42b6f8f2d9a

Publishing to the website is still TBD, but some review there would be great as well.

Cheers,
Paul


    


Re: QA notification for completed autobuilder build (yocto-3.1.rc2)

Paul Eggleton
 

Release notes draft attached, including a dedication to Scott (wasn't sure where to put that so I've just left it at the top) and contributors list. Let me know if you notice anything missing/incorrect.

I've also sent out the 3.1 migration guide for the reference manual, Richard has just merged the changes:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=dunfell&id=c31ddaba1f3181c577fdaa3ce519a42b6f8f2d9a

Publishing to the website is still TBD, but some review there would be great as well.

Cheers,
Paul


Re: Guidance Downgrading Python2 in Zeus #python

Sean McKay
 

FYI, we’re doing the same internally (vendor supplied FIPS supported openssl 1.0.2), and the layer Armin suggests worked for us on zeus with minimal additional tweaking.

 

Good luck!

-Sean

 

From: yocto@... <yocto@...> On Behalf Of akuster
Sent: Wednesday, April 15, 2020 9:23 AM
To: MikeB <mabnhdev@...>; yocto@...
Subject: Re: [yocto] Guidance Downgrading Python2 in Zeus #python

 

 

On 4/15/20 9:16 AM, MikeB wrote:

I'm working on a set of platforms that have a FIPs certified OpenSSL.  We are at version 1.0.2l.

I've found that the new version of python in Zeus (2.7.17) requires a newer version of OpenSSL (1.1).

We really don't want to go through a new round of certification, so we want to keep our current OpenSSL (1.0.2l).

I think the easiest solution is to downgrade python 2 back to the version used by Sumo (2.7.15).

I know how to downgrade simple recipes, but python is far from simple.

Can someone give me some guidance on how to approach the downgrade of python2 in Zeus?


Have had a chance to look at this layer?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-openssl102-fips/

- armin


Thanks, Mike

 

 


Re: Guidance Downgrading Python2 in Zeus #python

Armin Kuster
 



On 4/15/20 9:16 AM, MikeB wrote:
I'm working on a set of platforms that have a FIPs certified OpenSSL.  We are at version 1.0.2l.

I've found that the new version of python in Zeus (2.7.17) requires a newer version of OpenSSL (1.1).

We really don't want to go through a new round of certification, so we want to keep our current OpenSSL (1.0.2l).

I think the easiest solution is to downgrade python 2 back to the version used by Sumo (2.7.15).

I know how to downgrade simple recipes, but python is far from simple.

Can someone give me some guidance on how to approach the downgrade of python2 in Zeus?

Have had a chance to look at this layer?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-openssl102-fips/

- armin

Thanks, Mike

    


Re: Guidance Downgrading Python2 in Zeus #python

Alexander Kanavin
 

I think python2 *recipe* requires openssl 1.1, but python2 itself will work just fine with openssl 1.0. So you only need to adjust the dependency, there are several ways to do that.

Alex


On Wed, 15 Apr 2020 at 18:16, MikeB <mabnhdev@...> wrote:
I'm working on a set of platforms that have a FIPs certified OpenSSL.  We are at version 1.0.2l.

I've found that the new version of python in Zeus (2.7.17) requires a newer version of OpenSSL (1.1).

We really don't want to go through a new round of certification, so we want to keep our current OpenSSL (1.0.2l).

I think the easiest solution is to downgrade python 2 back to the version used by Sumo (2.7.15).

I know how to downgrade simple recipes, but python is far from simple.

Can someone give me some guidance on how to approach the downgrade of python2 in Zeus?

Thanks, Mike


Guidance Downgrading Python2 in Zeus #python

MikeB
 

I'm working on a set of platforms that have a FIPs certified OpenSSL.  We are at version 1.0.2l.

I've found that the new version of python in Zeus (2.7.17) requires a newer version of OpenSSL (1.1).

We really don't want to go through a new round of certification, so we want to keep our current OpenSSL (1.0.2l).

I think the easiest solution is to downgrade python 2 back to the version used by Sumo (2.7.15).

I know how to downgrade simple recipes, but python is far from simple.

Can someone give me some guidance on how to approach the downgrade of python2 in Zeus?

Thanks, Mike


Re: Image size reduction

Randy MacLeod
 

On 2020-04-14 11:51 a.m., Ajam Ali wrote:
Hi Randy,
In my image most of the size is consumed by heavy size packages.
So i have given this task of image size reduction to application team.
If i will remove the dependencies then may be some feature get disabled which could be needed.
Till now i am able to remove only python3 from dependencies.
Thanks for the summary Ajam.
../Randy


Thanks,
Ajam Ali
------------------------------------------------------------------------
*From:* Randy MacLeod <randy.macleod@windriver.com>
*Sent:* Monday, April 13, 2020 11:18 PM
*To:* Ajam Ali <AjamA@hcl.com>; yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org>; gley-yocto@m.gmane-mx.org <gley-yocto@m.gmane-mx.org>
*Subject:* Re: [yocto] Image size reduction
**[CAUTION: This Email is from outside the Organization. Do not click links or open attachments unless you trust the sender.]
On 2020-04-04 12:27 p.m., Ajam Ali wrote:
Hi All,

Thanks for your suggestions. I am working on your suggestions.
I will let you know if it did not work for me.
Ajam,
It would be useful if you could reply either way.
If there's still a problem then perhaps someone can help.
If you are able to resolve the issue, then a brief summary
of what you did could help the next person who has a similar
issue.
Thanks,
../Randy



Regards,
Ajam Ali


------------------------------------------------------------------------
*From:* yocto@lists.yoctoproject.org <mailto:yocto@lists.yoctoproject.org> <yocto@lists.yoctoproject.org> <mailto:yocto@lists.yoctoproject.org> on behalf of Gmane Admin via lists.yoctoproject.org <gley-yocto=m.gmane-mx.org@lists.yoctoproject.org> <mailto:gley-yocto=m.gmane-mx.org@lists.yoctoproject.org>
*Sent:* Saturday, April 4, 2020 9:36 PM
*To:* yocto@lists.yoctoproject.org <mailto:yocto@lists.yoctoproject.org> <yocto@lists.yoctoproject.org> <mailto:yocto@lists.yoctoproject.org>
*Subject:* Re: [yocto] Image size reduction
[CAUTION: This Email is from outside the Organization. Do not click links or open attachments unless you trust the sender.]

Op 29-03-2020 om 18:28 schreef Ajam Ali:
Hi All,

Actually my current image size is 3.9GB because of heavy size packages
required by my project and without project required packages my image
size in Yocto is 800MB.
So your project adds 3.1GB right

I want to reduce the image size as maximum as possible.
3.1GB is huge. Compare to f.i. Libreoffice (installed 0.5GB or so).
Either your own code has a lot of fat, or you are pulling in lots of
packages you don't really need. But is there no way to advise you
without knowing more.

Please suggest the best possible way so that I could reduce the maximum
possible size(desirable below 1.5 GB).


Thanks in advance,
Ajam Ali


Sent from Outlook Mobile <https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fblhgte&;data=02%7C01%7Cajama%40hcl.com%7Cf719cb14fe674f86f02408d7d8b236b0%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637216132261322392&amp;sdata=8in2t%2B6mXtrsRwa7GmgGQDl69uRzL7g4smj%2Ba3QG9gU%3D&amp;reserved=0
<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fblhgte&data=02%7C01%7Cajama%40hcl.com%7C128e3933213f473fc34a08d7dfd2da33%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637223969041569087&sdata=gY%2FoAEw1u9iOH8l9146xlNknKSslGAhehsRsWa83%2F10%3D&reserved=0>>
::DISCLAIMER::
------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and
intended for the named recipient(s) only. E-mail transmission is not
guaranteed to be secure or error-free as information could be
intercepted, corrupted, lost, destroyed, arrive late or incomplete, or
may contain viruses in transmission. The e mail and its contents (with
or without referred errors) shall therefore not attach any liability on
the originator or HCL or its affiliates. Views or opinions, if any,
presented in this email are solely those of the author and may not
necessarily reflect the views or opinions of HCL or its affiliates. Any
form of reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior
written consent of authorized representative of HCL is strictly
prohibited. If you have received this email in error please delete it
and notify the sender immediately. Before opening any email and/or
attachments, please check them for viruses and other defects.
------------------------------------------------------------------------




--
# Randy MacLeod
# Wind River Linux

--
# Randy MacLeod
# Wind River Linux

6241 - 6260 of 55412