On Fri, 2 Sept 2022 at 02:12, Peter Kjellerstedt
wrote:
> Since the test you added previously now requires that the path contains
> "/templates/", we might as well do this for any faulty configuration. I.e.:
>
> # The path in $TEMPLATECONF must contain "/templates/". If it doesn't,
> # uns
The full path of patch may contain '/meta/' but not in oe-core, skip
patches by checking it starts with oe-core full path or not.
Signed-off-by: Yang Xu
---
meta/classes/insane.bbclass | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/classes/insane.bbclass b/meta/classe
> -Original Message-
> From: openembedded-core@lists.openembedded.org
> On Behalf Of Alexander Kanavin
> Sent: den 1 september 2022 16:23
> To: openembedded-core@lists.openembedded.org
> Cc: Alexander Kanavin
> Subject: [OE-core] [PATCH] scripts/oe-setup-builddir: migrate
> build/conf/t
There could be IMAGE_CLASSES designed to work on images which arent
necessarily compatible with baremetal-images, one example is the
license_image class which relies on the package managers functionality
during do_rootfs, for baremetal images no rootfs is created hence the
package manager shouldnt
On Thu, Sep 1, 2022 at 2:56 PM Richard Purdie
wrote:
>
> On Thu, 2022-09-01 at 13:32 -0700, Khem Raj wrote:
> > meta-clang has options when it comes to C++ runtime, default is to use
> > gnu runtime, other options are llvm runtime and android runtime. This
> > patch helps when a distro is using ll
Wind River already has a mechanism to do something like this, called templates.
https://github.com/WindRiver-Labs/wr-template/tree/WRLINUX_10_21_BASE
Each template can have (optionally):
# README - template README file
# require - list of other templates required for this one
# template.c
On Thu, 2022-09-01 at 13:32 -0700, Khem Raj wrote:
> meta-clang has options when it comes to C++ runtime, default is to use
> gnu runtime, other options are llvm runtime and android runtime. This
> patch helps when a distro is using llvm runtime for C/C++ runtime. It
> informs the rust build system
meta-clang has options when it comes to C++ runtime, default is to use
gnu runtime, other options are llvm runtime and android runtime. This
patch helps when a distro is using llvm runtime for C/C++ runtime. It
informs the rust build system about right C++ runtime to configure for
when such a setti
This is a leftover from one of the RFC iterations, where
the property contained available machines, distros and templates.
As all of those were dropped from the final version, there is no
reason to list the layers either anymore.
Normally this would be a backwards incompatible change, but as
the l
FWIW: boost can also trigger this issue now:
"x86_64-webos-linux-g++" "-m64" "-march=core2" "-mtune=core2" "-msse3"
"-mfpmath=sse" "-Wl,-O1" "-Wl,--hash-style=gnu" "-Wl,--as-needed"
"-fmacro-prefix-map=/OE/build/luneos-langdale/webos-ports/tmp-glibc/work/core2-64-webos-linux/boost/1.80.0-r0/bo
On Thu, 18 Aug 2022 at 11:27, Richard Purdie
wrote:
> The intent is the user could add something like:
>
> require conf/yocto-autobuilder/x32.inc
>
> or
>
> require conf/yocto-autobuilder/multilib-mipsn32.inc
>
> and similar to their local.conf and more easily replicate
> configurations.
This cou
On Thu, 1 Sept 2022 at 16:12, Alexander Kanavin via
lists.openembedded.org
wrote:
> > Ideally, the checks in sanity.bbclass would migrate existing builds for
> > this issue...
>
> The check and the error is in oe-init-build-env, so cannot be fixed by
> anything in meta/. But I think I can add a sp
This is done only for default oe-core/poky templates; for anything
else the locations themselves need to be migrated first, and there
is no way to tell where they would be.
Signed-off-by: Alexander Kanavin
---
scripts/oe-setup-builddir | 6 ++
1 file changed, 6 insertions(+)
diff --git a/sc
The following changes since commit a3cba15142e98177119ef36c09f553d09acf35ef:
build-appliance-image: Update to dunfell head revision (2022-08-22 16:07:02
+0100)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib stable/dunfell-next
http://cgit.ope
On Thu, 1 Sept 2022 at 15:43, Richard Purdie
wrote:
> Ideally, the checks in sanity.bbclass would migrate existing builds for
> this issue...
The check and the error is in oe-init-build-env, so cannot be fixed by
anything in meta/. But I think I can add a special case for the 'old'
values to the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *diffoscope* to *221* has
Succeeded.
Next steps:
- apply the patch: git am 0001-diffoscope-upgrade-220-221.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *lttng-modules* to *2.13.5*
has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-lttng-modules-upgrade-2.13.4-2.13
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *lttng-tools* to *2.13.8* has
Succeeded.
Next steps:
- apply the patch: git am 0001-lttng-tools-upgrade-2.13.7-2.13.8.patch
- check the changes to upstream patches and summar
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *pinentry* to *1.2.1* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe pinentry failed.
NOTE: Starting bitbake server...
NOTE: Reconnecti
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *lz4* to *1.9.4* has Succeeded.
Next steps:
- apply the patch: git am 0001-lz4-upgrade-1.9.3-1.9.4.patch
- check the changes to upstream patches and summarize them in the comm
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *nghttp2* to *1.49.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-nghttp2-upgrade-1.48.0-1.49.0.patch
- check the changes to upstream patches and summarize them
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *curl* to *7.85.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe curl failed.
NOTE: Starting bitbake server...
WARNING: Host distribut
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *spirv-tools* to *1.3.224.1*
has Succeeded.
Next steps:
- apply the patch: git am 0001-spirv-tools-upgrade-1.3.216.0-1.3.224.1.patch
- check the changes to upstream patches a
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libxslt* to *1.1.37* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-libxslt-upgrade-1.1.35-1.1.37.patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-samples* to
*8a35e1d216c064895ba2854ac368c07f6cc74ae4* has Failed(other errors).
Detailed error information:
'MACHINE=qemux86 bitbake vulkan-samples' failed
WARNING: Host di
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libjitterentropy* to *3.4.1*
has Succeeded.
Next steps:
- apply the patch: git am 0001-libjitterentropy-upgrade-3.4.0-3.4.1.patch
- check the changes to upstream patches and
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ffmpeg* to *5.1.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-ffmpeg-upgrade-5.1-5.1.1.patch
- check the changes to upstream patches and summarize them in the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-tools* to *1.3.224.1*
has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
0001-vulkan-tools-upgrade-1.3.216.0
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libwpe* to *1.12.3* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libwpe-upgrade-1.12.2-1.12.3.patch
- check the changes to upstream patches and summarize them i
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libtasn1* to *4.19.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libtasn1-upgrade-4.18.0-4.19.0.patch
- check the changes to upstream patches and summarize th
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libxfont2* to *2.0.6* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade libxfont2 -V 2.0.6
NOTE: Starting bitbake server...
WAR
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *linux-firmware* to *20220815*
has Succeeded.
Next steps:
- apply the patch: git am
0001-linux-firmware-upgrade-20220708-20220815.patch
- check the changes to upstream patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-loader* to *1.3.224.1*
has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade vulkan-loader -V 1.3.224.1 -S
09afdf64210b11ec
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-headers* to
*1.3.224.1* has Succeeded.
Next steps:
- apply the patch: git am
0001-vulkan-headers-upgrade-1.3.216.0-1.3.224.1.patch
- check the changes to upstream pa
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-setuptools* to
*65.3.0* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-setuptools-upgrade-65.0.2-65.3.0.patch
- check the changes to upstream pat
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *repo* to *2.29.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-repo-upgrade-2.28-2.29.1.patch
- check the changes to upstream patches and summarize them in the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *spirv-headers* to *1.3.224.1*
has Succeeded.
Next steps:
- apply the patch: git am
0001-spirv-headers-upgrade-1.3.216.0-1.3.224.1.patch
- check the changes to upstream patc
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *librsvg* to *2.54.5* has
Succeeded.
Next steps:
- apply the patch: git am 0001-librsvg-upgrade-2.54.4-2.54.5.patch
- check the changes to upstream patches and summarize them
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libdrm* to *2.4.113* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-libdrm-upgrade-2.4.112-2.4.113.patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-dtschema* to
*2022.8.3* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-dtschema-upgrade-2022.8.1-2022.8.3.patch
- check the changes to upstream p
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libfontenc* to *1.1.6* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade libfontenc -V 1.1.6
NOTE: Starting bitbake server...
W
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *mesa* to *22.1.7* has
Succeeded.
Next steps:
- apply the patch: git am 0001-mesa-upgrade-22.1.6-22.1.7.patch
- check the changes to upstream patches and summarize them in th
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libxau* to *1.0.10* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade libxau -V 1.0.10
NOTE: Starting bitbake server...
WARNING
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ethtool* to *5.19* has
Succeeded.
Next steps:
- apply the patch: git am 0001-ethtool-upgrade-5.18-5.19.patch
- check the changes to upstream patches and summarize them in th
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *tzdata* to *2022c* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-tzdata-upgrade-2022b-2022c.patch
- ch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *shadow* to *4.12.3* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-shadow-upgrade-4.12.1-4.12.3.patch
-
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-poetry-core* to
*1.1.0* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade python3-poetry-core -V 1.1.0
NOTE: Starting b
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libsdl2* to *2.24.0* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-libsdl2-upgrade-2.0.22-2.24.0.patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-mako* to *1.2.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-python3-mako-upgrade-1.2.1-1.2.2.patch
- check the changes to upstream patches and summari
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *base-passwd* to *3.6.0* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe base-passwd failed.
NOTE: Starting bitbake server...
WARNING: H
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *glslang* to *1.3.224.1* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe glslang failed.
NOTE: Starting bitbake server...
WARNING: Host
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-jsonschema* to
*4.15.0* has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-python3-jsonschema-upgrade-4
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-hypothesis* to
*6.54.4* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-hypothesis-upgrade-6.46.11-6.54.4.patch
- check the changes to upstream pa
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-hatchling* to *1.8.1*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-hatchling-upgrade-1.8.0-1.8.1.patch
- check the changes to upstream patches a
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *qemu* to *7.1.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe qemu failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bi
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-bcrypt* to *4.0.0*
has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-python3-bcrypt-upgrade-3.2.2-4.0.
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-pathspec* to *0.10.0*
has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-python3-pathspec-upgrade-0.9.0
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *git* to *2.37.3* has
Succeeded.
Next steps:
- apply the patch: git am 0001-git-upgrade-2.37.2-2.37.3.patch
- check the changes to upstream patches and summarize them in the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ninja* to *1.11.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-ninja-upgrade-1.11.0-1.11.1.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ccache* to *4.6.3* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe ccache failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting t
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ovmf* to *edk2-stable202208*
has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
0001-ovmf-upgrade-edk2-stable202205
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *cmake* to *3.24.1* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-cmake-upgrade-3.24.0-3.24.1.patch
- c
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *jquery* to *3.6.1* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-jquery-upgrade-3.6.0-3.6.1.patch
- ch
On Thu, 2022-09-01 at 14:14 +0200, Alexander Kanavin wrote:
> On Thu, 1 Sept 2022 at 14:11, Jacob Kroon wrote:
> >
> > On 9/1/22 13:49, Jacob Kroon via lists.openembedded.org wrote:
> > > Hi,
> > >
> > > After updating to master branches I'm getting:
> > >
> > > > Error: TEMPLATECONF value (whi
At some point this became unnecessary as llvm builds with with musl without it.
Signed-off-by: Alexander Kanavin
---
...ryInfo-Undefine-libc-functions-if-th.patch | 90 ---
meta/recipes-devtools/llvm/llvm_git.bb| 1 -
2 files changed, 91 deletions(-)
delete mode 100644
On Thu, 1 Sept 2022 at 14:11, Jacob Kroon wrote:
>
> On 9/1/22 13:49, Jacob Kroon via lists.openembedded.org wrote:
> > Hi,
> >
> > After updating to master branches I'm getting:
> >
> >> Error: TEMPLATECONF value (which is
> >> /home/jkroon/Projects/codab-linux/openembedded-core/meta/conf) must
>
On 9/1/22 13:49, Jacob Kroon via lists.openembedded.org wrote:
Hi,
After updating to master branches I'm getting:
Error: TEMPLATECONF value (which is
/home/jkroon/Projects/codab-linux/openembedded-core/meta/conf) must
point to meta-some-layer/conf/templates/template-name
What is the proper
Hi,
After updating to master branches I'm getting:
Error: TEMPLATECONF value (which is
/home/jkroon/Projects/codab-linux/openembedded-core/meta/conf) must point to
meta-some-layer/conf/templates/template-name
What is the proper solution to this ?
Jacob
-=-=-=-=-=-=-=-=-=-=-=-
Links: You r
From: LUIS ENRIQUEZ
This allows choosing padding algorithm when building fitImage. It may be
pkcs-1.5 or pss.
Signed-off-by: LUIS ENRIQUEZ
Signed-off-by: Alexandre Belloni
(cherry picked from commit 29d5336c728b28890bbaadebf0ccff00ad90a64d)
Signed-off-by: Ming Liu
---
meta/classes/kernel-fi
From: Ming Liu
Sometimes an end user might want to choose another kernel type argument
for uboot-mkimage other than "kernel", for instance: "kernel_noload".
Let's introduce a variable UBOOT_MKIMAGE_KERNEL_TYPE to support that,
and it could be used by BSP layers as well.
(From OE-Core rev: e2886
From: Ming Liu
Backport some fixes from master branch to kernel-fitimage.bbclass,
otherwise some features are incomplete.
LUIS ENRIQUEZ (1):
kernel-fitimage.bbclass: add padding algorithm property in config
nodes
Ming Liu (1):
meta: introduce UBOOT_MKIMAGE_KERNEL_TYPE
meta/classes/ke
Since "python_pep517: use installer instead of pip" pip is no longer
used in builds, and therefore doesn't need to behave reproducibly.
I have submitted the patch upstream; upstream have suggested that the
way it had been used previously is non-reproducible by design, and
if pip is again brought i
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/python/python3-pip/reproducible.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/python/python3-pip/reproducible.patch
b/meta/recipes-devtools/python/python3-pip/reproducible.patch
index 0ed
As announced here:
https://github.com/libsdl-org/SDL/releases/tag/release-2.24.0
Signed-off-by: Alexander Kanavin
---
meta/recipes-graphics/libsdl2/libsdl2_2.0.22.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-graphics/libsdl2/libsdl2_2.0.22.bb
b/meta/recipe
Signed-off-by: Alexander Kanavin
---
meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf/fatal-loader.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf/fatal-loader.patch
b/meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf/fatal-loader.patch
index dd5
Signed-off-by: Alexander Kanavin
---
.../mc/files/0001-mc-replace-perl-w-with-use-warnings.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/meta/recipes-extended/mc/files/0001-mc-replace-perl-w-with-use-warnings.patch
b/meta/recipes-extended/mc/files/0001-mc-replace
Signed-off-by: Alexander Kanavin
---
meta/recipes-core/sysvinit/sysvinit/install.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-core/sysvinit/sysvinit/install.patch
b/meta/recipes-core/sysvinit/sysvinit/install.patch
index 90563a6294..bc6d493c2b 100644
---
Signed-off-by: Alexander Kanavin
---
...Added-support-for-PPC-instructions-mfatbu-mfatbl.patch | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
a/meta/recipes-devtools/valgrind/valgrind/Added-support-for-PPC-instructions-mfatbu-mfatbl.patch
b/meta/recipes-devtools/valg
This should not be necessary, as ovmf is already marked as
COMPATIBLE_HOST:class-target='(i.86|x86_64).*'
and existing upstream code handles both.
If/when ovmf is used on other targets, the situation can be revisited.
Signed-off-by: Alexander Kanavin
---
.../ovmf/0003-ovmf-Update-to-latest.patc
Signed-off-by: Alexander Kanavin
---
...1-python3-use-cc_basename-to-replace-CC-for-checking-c.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/meta/recipes-devtools/python/python3/0001-python3-use-cc_basename-to-replace-CC-for-checking-c.patch
b/meta/recipes-devtools/
The patch has been added here
https://git.yoctoproject.org/poky/commit/?id=ca63a0158ae42010477080ad6bb776329f1230b0
and isn't necessary anymore, as cross compilation works fine
without it.
Signed-off-by: Alexander Kanavin
---
...ghostscript-9.21-prevent_recompiling.patch | 78 ---
Latest gcc no longer produces the warnings that this patch was
fixing.
Signed-off-by: Alexander Kanavin
---
...-sentinals-for-gst_structure_get-etc.patch | 86 ---
.../gstreamer1.0-plugins-bad_1.20.3.bb| 1 -
2 files changed, 87 deletions(-)
delete mode 100644
meta/rec
The patch was added in
https://git.yoctoproject.org/poky/commit/?id=f594a1145eb5b952265a3fdf6b158ef41b148b12
with no explanation for the use case or metadata.
As there are no uses of the option in poky or meta-oe, it can be removed.
In the (unlikely) event that someone is using the option private
As seen here https://repo.or.cz/syslinux.git/shortlog
Signed-off-by: Alexander Kanavin
---
.../0010-Workaround-multiple-definition-of-symbol-errors.patch | 2 +-
.../syslinux/0012-libinstaller-Fix-build-with-glibc-2.36.patch | 2 +-
.../syslinux/syslinux/0014-Fix-reproducibility-issues.patch
Signed-off-by: Alexander Kanavin
---
.../shadow/files/shadow-update-pam-conf.patch | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-extended/shadow/files/shadow-update-pam-conf.patch
b/meta/recipes-extended/shadow/files/shadow-update-pam-conf.pa
85 matches
Mail list logo
