|
Re: How to completely uninstall a pre-installed package in Yocto
#linux
#yocto
What I did was. I ran the following:
bitbake <image> -e |grep -v ^# |grep "^DISTRO_FEATURES=\|^IMAGE_FEATURES="
Then used DISTRO_FEATURES_remove in local.conf to remove the unwanted packages.
-=Srijan
What I did was. I ran the following:
bitbake <image> -e |grep -v ^# |grep "^DISTRO_FEATURES=\|^IMAGE_FEATURES="
Then used DISTRO_FEATURES_remove in local.conf to remove the unwanted packages.
-=Srijan
|
By
srijan.nandi@...
·
#50038
·
|
|
#yocto - mongodb files missing
#yocto
Hello Everyone,
I have built mongodb on zeus. It seems the mongod.service and mongod.conf files are missing. Can anyone show me the procedure to build a .bbappend file to add those.
Thanks and
Hello Everyone,
I have built mongodb on zeus. It seems the mongod.service and mongod.conf files are missing. Can anyone show me the procedure to build a .bbappend file to add those.
Thanks and
|
By
srijan.nandi@...
·
#50037
·
|
|
Image with trustfence
Do I have to change the address of loading the image into ram when trustfence is enabled?
Because after enabling trustfence I have got error:
## Flattened Device Tree blob at 8300000
Booting
Do I have to change the address of loading the image into ram when trustfence is enabled?
Because after enabling trustfence I have got error:
## Flattened Device Tree blob at 8300000
Booting
|
By
Adrian Dusiński <dusinski.adrian@...>
·
#50036
·
|
|
Re: [meta-mingw][PATCH] expat: Switch platform to Windows in CMake toolchain file
Hello Joshua,
Do you mean "set for all CMake-based recipes by default"? Maybe this is a better
option than adding the same function manually.
But then next question appears:
Should this be done by
Hello Joshua,
Do you mean "set for all CMake-based recipes by default"? Maybe this is a better
option than adding the same function manually.
But then next question appears:
Should this be done by
|
By
Oleksandr <oleksandr.s.popovych@...>
·
#50035
·
|
|
Re: [bitbake-devel] [yocto] Stable Warrior branch
Ok. FWIW we are struggling a little with keeping the older releases
building on the autobuilder as the workers change. We do have plans for
handling this with buildtools but its not rolled out on the
Ok. FWIW we are struggling a little with keeping the older releases
building on the autobuilder as the workers change. We do have plans for
handling this with buildtools but its not rolled out on the
|
By
Richard Purdie
·
#50034
·
|
|
Re: Building of warrior branch fails when building with Ubuntu 20.04 LTS
#linux
#qemu
#yocto
You can backport https://git.openembedded.org/openembedded-core/commit/?h=dunfell&id=2cca75155baec8358939e2aae822e256bed4cfe0
You can backport https://git.openembedded.org/openembedded-core/commit/?h=dunfell&id=2cca75155baec8358939e2aae822e256bed4cfe0
|
By
Martin Jansa
·
#50033
·
|
|
Re: Building of warrior branch fails when building with Ubuntu 20.04 LTS
#linux
#qemu
#yocto
Howdy!
Am Di., 21. Juli 2020 um 09:07 Uhr schrieb Bernd <bsp@...>:
The usual approach is to build inside a defined container, like pyrex
or CROPS, for example.
Greetz
Howdy!
Am Di., 21. Juli 2020 um 09:07 Uhr schrieb Bernd <bsp@...>:
The usual approach is to build inside a defined container, like pyrex
or CROPS, for example.
Greetz
|
By
Josef Holzmayr
·
#50032
·
|
|
Building of warrior branch fails when building with Ubuntu 20.04 LTS
#linux
#qemu
#yocto
Hello,
we are using the warrior branch for our embedded Linux project. Since Ubuntu 20.04 LTS has been released we would like to switch from 18.04 to 20.04. However, Ubuntu 20.04 now uses glibc-2.31
Hello,
we are using the warrior branch for our embedded Linux project. Since Ubuntu 20.04 LTS has been released we would like to switch from 18.04 to 20.04. However, Ubuntu 20.04 now uses glibc-2.31
|
By
Bernd
·
#50031
·
|
|
[prelink-cross] prelink-cross: Add SPDX-License-Identifier: GPL-2.0-or-later to source files
Signed-off-by: Sathish V <sathish25071992@...>
---
gelf/gelf.c | 4 +++-
gelf/gelf.h | 4 +++-
gelfx/gelfx.h | 4 +++-
gelfx32/gelfx.h | 4 +++-
src/arch-alpha.c | 4
Signed-off-by: Sathish V <sathish25071992@...>
---
gelf/gelf.c | 4 +++-
gelf/gelf.h | 4 +++-
gelfx/gelfx.h | 4 +++-
gelfx32/gelfx.h | 4 +++-
src/arch-alpha.c | 4
|
By
Sathish V
·
#50030
·
|
|
Re: Offline Build
#yocto
I gave new downloads (<pwd>/downloads) path in replace of /opt/yocto_downloads. It takes the new downloads path and did the compilation, but i'm facing error in do_fetch and do_compile.
I gave new downloads (<pwd>/downloads) path in replace of /opt/yocto_downloads. It takes the new downloads path and did the compilation, but i'm facing error in do_fetch and do_compile.
|
By
Amrun Nisha.R
·
#50029
·
|
|
[meta-rockchip][PATCH v2] arm-none-eabi-gcc: remove
We already have a dependency on meta-arm/meta-arm in order to build
tf-a (there's no point carrying our own recipe when there's a common,
consolidated one to use in meta-arm).
meta-arm/meta-arm now
We already have a dependency on meta-arm/meta-arm in order to build
tf-a (there's no point carrying our own recipe when there's a common,
consolidated one to use in meta-arm).
meta-arm/meta-arm now
|
By
Trevor Woerner
·
#50028
·
|
|
Re: [PATCH][meta-rockchip] arm-none-eabi toolchain
Thanks… and I could do a better subject line as well.
Thanks… and I could do a better subject line as well.
|
By
Trevor Woerner
·
#50027
·
|
|
[PATCH][meta-rockchip] update tf-a dependency
Now that we're using meta-arm-toolchain's recipe for arm-none-eabi-gcc, we
need to specify it as a native dependency (since that recipe doesn't assume
this implicitly).
Signed-off-by: Trevor Woerner
Now that we're using meta-arm-toolchain's recipe for arm-none-eabi-gcc, we
need to specify it as a native dependency (since that recipe doesn't assume
this implicitly).
Signed-off-by: Trevor Woerner
|
By
Trevor Woerner
·
#50026
·
|
|
Re: [PATCH][meta-rockchip] arm-none-eabi toolchain
this also means you should add meta-arm-toolchain to layer dependencies.
this also means you should add meta-arm-toolchain to layer dependencies.
|
By
Khem Raj
·
#50025
·
|
|
[PATCH][meta-rockchip] arm-none-eabi toolchain
We now have a dependency on meta-arm/meta-arm in order to build tf-a (there's
no point carrying our own recipe when there's a common, consolidated one to
use in meta-arm).
meta-arm/meta-arm now has a
We now have a dependency on meta-arm/meta-arm in order to build tf-a (there's
no point carrying our own recipe when there's a common, consolidated one to
use in meta-arm).
meta-arm/meta-arm now has a
|
By
Trevor Woerner
·
#50024
·
|
|
M+ & H bugs with Milestone Movements WW29
All,
YP M+ or high bugs which moved to a new milestone in WW29 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
Medium+
13550
username/password specified to
All,
YP M+ or high bugs which moved to a new milestone in WW29 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
Medium+
13550
username/password specified to
|
By
Stephen Jolley
·
#50023
·
|
|
Enhancements/Bugs closed WW29!
All,
The below were the owners of enhancements or bugs closed during the last week!
Who
Count
richard.purdie@...
4
timothy.t.orling@...
1
ross@...
1
michael@...
1
Grand Total
7
Thanks,
All,
The below were the owners of enhancements or bugs closed during the last week!
Who
Count
richard.purdie@...
4
timothy.t.orling@...
1
ross@...
1
michael@...
1
Grand Total
7
Thanks,
|
By
Stephen Jolley
·
#50022
·
|
|
Current high bug count owners for Yocto Project 3.2
All,
Below is the list as of top 30 bug owners as of the end of WW29 of who have open medium or higher bugs and enhancements against YP 3.2. There are 72 possible work days left until the final
All,
Below is the list as of top 30 bug owners as of the end of WW29 of who have open medium or higher bugs and enhancements against YP 3.2. There are 72 possible work days left until the final
|
By
Stephen Jolley
·
#50021
·
|
|
Yocto Project Newcomer & Unassigned Bugs - Help Needed
All,
The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on
All,
The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on
|
By
Stephen Jolley
·
#50020
·
|
|
Re: Offline Build
#yocto
/opt/yocto_downloads or /opt/downloads?
/opt/yocto_downloads or /opt/downloads?
|
By
Martin Jansa
·
#50019
·
|