Re: [OE-core] [PATCH 1/2] gdb: Upgrade to 11.1
On Fri, Nov 5, 2021 at 12:57 PM Richard Purdie
wrote:
>
> On Fri, 2021-11-05 at 09:51 -0700, Khem Raj wrote:
> > On Fri, Nov 5, 2021 at 4:19 AM Richard Purdie
> > wrote:
> > >
> > > On Wed, 2021-11-03 at 18:30 -0700, Khem Raj wrote:
> > > > Drop backported patches
> > > > Changes are here [1]
> > > >
> > > > [1] https://sourceware.org/pipermail/gdb-announce/2021/000129.html
> > > >
> > > > Signed-off-by: Khem Raj
> > > > ---
> > > > meta/conf/distro/include/tcmode-default.inc | 2 +-
> > > > .../gdb/{gdb-10.2.inc => gdb-11.1.inc}| 14 +-
> > > > ...ian_10.2.bb => gdb-cross-canadian_11.1.bb} | 0
> > > > .../{gdb-cross_10.2.bb => gdb-cross_11.1.bb} | 0
> > > > ...make-man-install-relative-to-DESTDIR.patch | 20 +-
> > > > ...ux-nat-Define-_ABIO32-if-not-defined.patch | 8 +-
> > > > ...e-pt_regs-uapi_pt_regs-on-GLIBC-syst.patch | 10 +-
> > > > ...port-for-Renesas-SH-sh4-architecture.patch | 39 +-
> > > > ...readline.a-when-using-disable-static.patch | 12 +-
> > > > .../gdb/gdb/0006-use-asm-sgidefs.h.patch | 8 +-
> > > > ...atch => 0007-Change-order-of-CFLAGS.patch} | 12 +-
> > > > ...8-resolve-restrict-keyword-conflict.patch} | 8 +-
> > > > ...> 0009-Fix-invalid-sigprocmask-call.patch} | 8 +-
> > > > ...h => 0010-gdbserver-ctrl-c-handling.patch} | 10 +-
> > > > ...-arc-Add-support-for-signal-handlers.patch | 218 -
> > > > ...-for-signal-frames-for-Linux-targets.patch | 232 --
> > > > ...count-the-REGNUM-in-supply-collect-g.patch | 104 -
> > > > ...-native-support-for-ARC-in-GNU-Linux.patch | 414 --
> > > > .../gdb/{gdb_10.2.bb => gdb_11.1.bb} | 0
> > > > 19 files changed, 74 insertions(+), 1045 deletions(-)
> > > > rename meta/recipes-devtools/gdb/{gdb-10.2.inc => gdb-11.1.inc} (56%)
> > > > rename meta/recipes-devtools/gdb/{gdb-cross-canadian_10.2.bb =>
> > > > gdb-cross-canadian_11.1.bb} (100%)
> > > > rename meta/recipes-devtools/gdb/{gdb-cross_10.2.bb =>
> > > > gdb-cross_11.1.bb} (100%)
> > > > rename
> > > > meta/recipes-devtools/gdb/gdb/{0008-Change-order-of-CFLAGS.patch =>
> > > > 0007-Change-order-of-CFLAGS.patch} (75%)
> > > > rename
> > > > meta/recipes-devtools/gdb/gdb/{0009-resolve-restrict-keyword-conflict.patch
> > > > => 0008-resolve-restrict-keyword-conflict.patch} (91%)
> > > > rename
> > > > meta/recipes-devtools/gdb/gdb/{0010-Fix-invalid-sigprocmask-call.patch
> > > > => 0009-Fix-invalid-sigprocmask-call.patch} (90%)
> > > > rename
> > > > meta/recipes-devtools/gdb/gdb/{0011-gdbserver-ctrl-c-handling.patch =>
> > > > 0010-gdbserver-ctrl-c-handling.patch} (82%)
> > > > delete mode 100644
> > > > meta/recipes-devtools/gdb/gdb/0012-arc-Add-support-for-signal-handlers.patch
> > > > delete mode 100644
> > > > meta/recipes-devtools/gdb/gdb/0013-arc-Add-support-for-signal-frames-for-Linux-targets.patch
> > > > delete mode 100644
> > > > meta/recipes-devtools/gdb/gdb/0014-arc-Take-into-account-the-REGNUM-in-supply-collect-g.patch
> > > > delete mode 100644
> > > > meta/recipes-devtools/gdb/gdb/0015-gdb-Add-native-support-for-ARC-in-GNU-Linux.patch
> > > > rename meta/recipes-devtools/gdb/{gdb_10.2.bb => gdb_11.1.bb} (100%)
> > >
> > > Breaks on mingw:
> > >
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/4299
> > >
> >
> > I see
> >
> > > sys-linux.c:140:10: fatal error: linux/ipx.h: No such file or directory
> > > 140 | #include
> > > | ^
> > > compilation terminated.
> > > make[1]: *** [: sys-linux.o] Error 1
> > > make[1]: Leaving directory
> > '/home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/core2-32-poky-linux-musl/ppp/2.4.9-r0/ppp-2.4.9/pppd'
> >
> > perhaps wrong link ?
>
> Sorry, https://autobuilder.yoctoproject.org/typhoon/#/builders/89/builds/4293
>
sent a fix to ml and also queued a build :)
https://autobuilder.yoctoproject.org/typhoon/#/buildrequests/238205
> Cheers,
>
> Richard
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157932):
https://lists.openembedded.org/g/openembedded-core/message/157932
Mute This Topic: https://lists.openembedded.org/mt/86807405/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] Depending on other package's config
On Fri, Nov 5, 2021 at 3:25 PM Maxim Sloyko via lists.openembedded.org
wrote:
>
> Hi all,
>
> Posting this to openembedded-core, as it was suggested to me.
>
> The recipe that I'm working on for our system (let's call it A) has a
> dependency on a certain feature being enabled in another package (B).
> So, in B, we have:
>
> PACKAGECONFIG[nice-feature] = "..."
>
> and my recipe (or rather, the tool built by the recipe), needs that
> feature to be enabled to work properly. What's worse, is that this is
> a runtime dependency, so if somebody just forgets to enable that
> feature, the image will build fine, but the tool won't work. I would
> like this to be a build time failure.
>
> My plan is to change recipe A, so that if the "nice-feature" is
> enabled, the package will PROVIDE one more thing:
>
> PROVIDES += "${PN}-nice-feature"
>
> and in my recipe B, I'll declare this as a dependency:
>
> RDEPENDS:${PN} += "package-a-nice-feature".
You're doing that just to generate a build time error if the two
recipe's configurations are not consistent?
The normal approach would be to define a global variable (e.g. a
distro feature) which both recipes can check and use to configure
themselves appropriately.
> Now I'm thinking, wouldn't it be great if package A could specify
> extra PROVIDES when the feature is configured? This would be similar
> to the way it's done for package's R?DEPENDS:
>
> PACKAGECONFIG ??= "f1 f2 f3 ..."
> PACKAGECONFIG[f1] = "\
> --with-f1, \
> --without-f1, \
> build-deps-for-f1, \
> runtime-deps-for-f1, \
> runtime-recommends-for-f1, \
> packageconfig-conflicts-for-f1 \
> provides-for-f1 \
> "
>
> The last line would be a change that I propose. It looks like it would
> be relatively easy to implement this in base.bbclass
>
> What do you think? Will this be useful? Did I miss an existing way to do this?
>
> Thanks,
>
> --
> -MS
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157931):
https://lists.openembedded.org/g/openembedded-core/message/157931
Mute This Topic: https://lists.openembedded.org/mt/86853514/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH v2] gdb: Add dependency on libgmp
gdb 11 has added this library as must have
Signed-off-by: Khem Raj
---
v2: Add gmp dependency for gdb-cross-canadian as well
mingw needs it.
meta/recipes-devtools/gdb/gdb-common.inc | 3 ++-
meta/recipes-devtools/gdb/gdb-cross-canadian.inc | 2 +-
2 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-devtools/gdb/gdb-common.inc
b/meta/recipes-devtools/gdb/gdb-common.inc
index 0fe7b4e5b0..f3ab3544da 100644
--- a/meta/recipes-devtools/gdb/gdb-common.inc
+++ b/meta/recipes-devtools/gdb/gdb-common.inc
@@ -2,7 +2,7 @@ SUMMARY = "GNU debugger"
HOMEPAGE = "http://www.gnu.org/software/gdb/;
DESCRIPTION = "GDB, the GNU Project debugger, allows you to see what is going
on inside another program while it executes -- or what another program was
doing at the moment it crashed."
SECTION = "devel"
-DEPENDS = "expat zlib ncurses virtual/libiconv ${LTTNGUST} bison-native"
+DEPENDS = "expat gmp zlib ncurses virtual/libiconv ${LTTNGUST} bison-native"
LTTNGUST = "lttng-ust"
LTTNGUST:arc = ""
@@ -27,6 +27,7 @@ EXTRA_OECONF = "--disable-gdbtk --disable-x --disable-werror \
--disable-gas --disable-binutils \
--disable-ld --disable-gold \
--disable-gprof \
+--with-libgmp-prefix=${STAGING_EXECPREFIXDIR} \
"
PACKAGECONFIG ??= "readline ${@bb.utils.filter('DISTRO_FEATURES',
'debuginfod', d)}"
diff --git a/meta/recipes-devtools/gdb/gdb-cross-canadian.inc
b/meta/recipes-devtools/gdb/gdb-cross-canadian.inc
index dfacba29a0..836c51a3de 100644
--- a/meta/recipes-devtools/gdb/gdb-cross-canadian.inc
+++ b/meta/recipes-devtools/gdb/gdb-cross-canadian.inc
@@ -6,7 +6,7 @@ SUMMARY = "GNU debugger (cross-canadian gdb for ${TARGET_ARCH}
target)"
PN = "gdb-cross-canadian-${TRANSLATED_TARGET_ARCH}"
BPN = "gdb"
-DEPENDS = "nativesdk-ncurses nativesdk-expat nativesdk-gettext \
+DEPENDS = "nativesdk-ncurses nativesdk-expat nativesdk-gettext nativesdk-gmp \
virtual/${HOST_PREFIX}gcc-crosssdk
virtual/${HOST_PREFIX}binutils-crosssdk virtual/nativesdk-libc"
GDBPROPREFIX = "--program-prefix='${TARGET_PREFIX}'"
--
2.33.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157930):
https://lists.openembedded.org/g/openembedded-core/message/157930
Mute This Topic: https://lists.openembedded.org/mt/86855751/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] Depending on other package's config
Hi all,
Posting this to openembedded-core, as it was suggested to me.
The recipe that I'm working on for our system (let's call it A) has a
dependency on a certain feature being enabled in another package (B).
So, in B, we have:
PACKAGECONFIG[nice-feature] = "..."
and my recipe (or rather, the tool built by the recipe), needs that
feature to be enabled to work properly. What's worse, is that this is
a runtime dependency, so if somebody just forgets to enable that
feature, the image will build fine, but the tool won't work. I would
like this to be a build time failure.
My plan is to change recipe A, so that if the "nice-feature" is
enabled, the package will PROVIDE one more thing:
PROVIDES += "${PN}-nice-feature"
and in my recipe B, I'll declare this as a dependency:
RDEPENDS:${PN} += "package-a-nice-feature".
Now I'm thinking, wouldn't it be great if package A could specify
extra PROVIDES when the feature is configured? This would be similar
to the way it's done for package's R?DEPENDS:
PACKAGECONFIG ??= "f1 f2 f3 ..."
PACKAGECONFIG[f1] = "\
--with-f1, \
--without-f1, \
build-deps-for-f1, \
runtime-deps-for-f1, \
runtime-recommends-for-f1, \
packageconfig-conflicts-for-f1 \
provides-for-f1 \
"
The last line would be a change that I propose. It looks like it would
be relatively easy to implement this in base.bbclass
What do you think? Will this be useful? Did I miss an existing way to do this?
Thanks,
--
-MS
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157929):
https://lists.openembedded.org/g/openembedded-core/message/157929
Mute This Topic: https://lists.openembedded.org/mt/86853514/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [bitbake-devel] [oe-core][PATCH 1/2] devtools: Initial recipe for repo 2.17.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Alex, we are getting a bit off topic here, but whatever... ;) > What I mean is that I would try harder to find a workable setup while > keeping the recipes for individual items that need to be built. the individual recipes don't really add that much benefit for us, mostly just maintenance overhead and complexity, as we need to constantly ensure that the various components depend on each other in the right order. The only beneficial aspect to the multitude of recipes is the sstate cache. However, as the packages heavily depend on one another, the benefit is marginal, as we have to rebuild most of the application anyways. Additionally, this is not how the developers build the application, so basically we currently have to maintain two separate build workflows. Changing to repo also improves the developer workflow outside of yocto, e.g. thanks to the notion of "topics". The "devtool" option, whilst duable I assume, would again limit the usability to within the Yocto environment. We are currently trying to get to a point, where we manage most of our (automated) workloads (e.g. testing) within Yocto but historically this was not the case and for daily development this is just not really practical. > Particularly this: > "if you want to create another version with different cmake flags, > you would have to create copies of all 50ish recipes" > looks odd. Why would you make copies? Just set the needed flags with > a variable that is set from a global config, > perhaps the distro or local.conf. As far as I understand, this is not reasonably possible (though I might be wrong. TBH, understanding variable scopes in Yocto is a nightmare). To give this some context, our current base setup looks as follows: - - We have one distro.conf - - We have three image recipes with slightly different config + featureset - - AFAIK an image recipe cannot set variables within another recipe, it just "consumes" existing recipes with their configuration. - -> Thus we have three respective recipes with slightly different configuration. If we where to use individual recipes in this setup, we'd have 50ish x 3 recipes. The approach you are describing might circumvent this particular situation but basically just moves the issue around, as you're now unabe to build all three configurations in one go, but need to start juggling your local.confs. Alternatively you might think about using multi-confs. However, each multiconf doubles the parse times for your recipes. As we already use a couple of multiconfs for different machine configs, we would basically increase the time it takes to parse the recipes by ~fifteen-fold (5 pre-existing multi-confs x 3 (or more) disto confs). Additionally, you now need to start worrying about artifact names, as by default the distro name is not included. So yeah... as far as I can tell, there are multiple ways to approach this issue, but none of them seem straight forward nor pretty. Bitbake as it is is just fundamentally not good at handling highly dynamic configurations. The combination with KAS somewhat defuses the situation, but there are still some situations where there is no easy answer. - -- With best regards Jasper Orschulko DevOps Engineer Tel. +49 30 58 58 14 265 Fax +49 30 58 58 14 999 jasper.orschu...@iris-sensing.com • • • • • • • • • • • • • • • • • • • • • • • • • • iris-GmbH infrared & intelligent sensors Schnellerstraße 1-5 | 12439 Berlin https://iris-sensing.com/ On Fri, 2021-11-05 at 19:45 +0100, Alexander Kanavin wrote: > On Fri, 5 Nov 2021 at 19:05, Jasper Orschulko > wrote: > > > > But that is exactly what we are doing, by integrating the repo > > fetcher into the yocto workflow, thus improving the yocto tooling > > :) > > Why reinvent the wheel, when you can reuse whats already there? You > > wouldn't reinvent git just for yocto, would you? > > > > > What I mean is that I would try harder to find a workable setup while > keeping the recipes for individual items that need to be built. > For instance, devtool is capable of updating source revisions in > recipes automatically, it may not work exactly as you want, but that > can be fixed. > Yes, repo itself is not proprietary, but your organizational workflow > is. > > Particularly this: > "if you want to create another version with different cmake flags, > you would have to create copies of all 50ish recipes" > looks odd. Why would you make copies? Just set the needed flags with > a variable that is set from a global config, > perhaps the distro or local.conf. > > Alex -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE4WyPMIC5Ap4+Ooo1Ygqew07VMNUFAmGFlPMACgkQYgqew07V MNXoCAf/fN4gi1dfx7r4acfbu7kaw9+3rjdMu34J6SX/ahGjCfbTZAg1Twf8N6RZ LBuOpDkXPU77iJuJixZySve5EZc4A2/NS0hqXEpD0aWf8AXaZzxq0UbEBM78oTgH Hk1zVEFxwLwEHpVIQyvwx5rFz/JvZ2EN4aH576ciPaw5n+bHIZBevUfhssPrjQWX yUTuWyeUoMJlXz41E+JfSd1VIQOC3hdWKF26er152zSyhYvhCagBMsHZMTKdrahn
Re: [OE-core] [PATCH 1/2] gdb: Upgrade to 11.1
On Fri, 2021-11-05 at 09:51 -0700, Khem Raj wrote:
> On Fri, Nov 5, 2021 at 4:19 AM Richard Purdie
> wrote:
> >
> > On Wed, 2021-11-03 at 18:30 -0700, Khem Raj wrote:
> > > Drop backported patches
> > > Changes are here [1]
> > >
> > > [1] https://sourceware.org/pipermail/gdb-announce/2021/000129.html
> > >
> > > Signed-off-by: Khem Raj
> > > ---
> > > meta/conf/distro/include/tcmode-default.inc | 2 +-
> > > .../gdb/{gdb-10.2.inc => gdb-11.1.inc}| 14 +-
> > > ...ian_10.2.bb => gdb-cross-canadian_11.1.bb} | 0
> > > .../{gdb-cross_10.2.bb => gdb-cross_11.1.bb} | 0
> > > ...make-man-install-relative-to-DESTDIR.patch | 20 +-
> > > ...ux-nat-Define-_ABIO32-if-not-defined.patch | 8 +-
> > > ...e-pt_regs-uapi_pt_regs-on-GLIBC-syst.patch | 10 +-
> > > ...port-for-Renesas-SH-sh4-architecture.patch | 39 +-
> > > ...readline.a-when-using-disable-static.patch | 12 +-
> > > .../gdb/gdb/0006-use-asm-sgidefs.h.patch | 8 +-
> > > ...atch => 0007-Change-order-of-CFLAGS.patch} | 12 +-
> > > ...8-resolve-restrict-keyword-conflict.patch} | 8 +-
> > > ...> 0009-Fix-invalid-sigprocmask-call.patch} | 8 +-
> > > ...h => 0010-gdbserver-ctrl-c-handling.patch} | 10 +-
> > > ...-arc-Add-support-for-signal-handlers.patch | 218 -
> > > ...-for-signal-frames-for-Linux-targets.patch | 232 --
> > > ...count-the-REGNUM-in-supply-collect-g.patch | 104 -
> > > ...-native-support-for-ARC-in-GNU-Linux.patch | 414 --
> > > .../gdb/{gdb_10.2.bb => gdb_11.1.bb} | 0
> > > 19 files changed, 74 insertions(+), 1045 deletions(-)
> > > rename meta/recipes-devtools/gdb/{gdb-10.2.inc => gdb-11.1.inc} (56%)
> > > rename meta/recipes-devtools/gdb/{gdb-cross-canadian_10.2.bb =>
> > > gdb-cross-canadian_11.1.bb} (100%)
> > > rename meta/recipes-devtools/gdb/{gdb-cross_10.2.bb =>
> > > gdb-cross_11.1.bb} (100%)
> > > rename meta/recipes-devtools/gdb/gdb/{0008-Change-order-of-CFLAGS.patch
> > > => 0007-Change-order-of-CFLAGS.patch} (75%)
> > > rename
> > > meta/recipes-devtools/gdb/gdb/{0009-resolve-restrict-keyword-conflict.patch
> > > => 0008-resolve-restrict-keyword-conflict.patch} (91%)
> > > rename
> > > meta/recipes-devtools/gdb/gdb/{0010-Fix-invalid-sigprocmask-call.patch =>
> > > 0009-Fix-invalid-sigprocmask-call.patch} (90%)
> > > rename
> > > meta/recipes-devtools/gdb/gdb/{0011-gdbserver-ctrl-c-handling.patch =>
> > > 0010-gdbserver-ctrl-c-handling.patch} (82%)
> > > delete mode 100644
> > > meta/recipes-devtools/gdb/gdb/0012-arc-Add-support-for-signal-handlers.patch
> > > delete mode 100644
> > > meta/recipes-devtools/gdb/gdb/0013-arc-Add-support-for-signal-frames-for-Linux-targets.patch
> > > delete mode 100644
> > > meta/recipes-devtools/gdb/gdb/0014-arc-Take-into-account-the-REGNUM-in-supply-collect-g.patch
> > > delete mode 100644
> > > meta/recipes-devtools/gdb/gdb/0015-gdb-Add-native-support-for-ARC-in-GNU-Linux.patch
> > > rename meta/recipes-devtools/gdb/{gdb_10.2.bb => gdb_11.1.bb} (100%)
> >
> > Breaks on mingw:
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/4299
> >
>
> I see
>
> > sys-linux.c:140:10: fatal error: linux/ipx.h: No such file or directory
> > 140 | #include
> > | ^
> > compilation terminated.
> > make[1]: *** [: sys-linux.o] Error 1
> > make[1]: Leaving directory
> '/home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/core2-32-poky-linux-musl/ppp/2.4.9-r0/ppp-2.4.9/pppd'
>
> perhaps wrong link ?
Sorry, https://autobuilder.yoctoproject.org/typhoon/#/builders/89/builds/4293
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157927):
https://lists.openembedded.org/g/openembedded-core/message/157927
Mute This Topic: https://lists.openembedded.org/mt/86807405/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 1/2] libx11: Update LICENSE to better reflect reality
There are no traces of neither the BSD-2-Clause license nor the BSD-4-Clause license being used in the code. There is one occurrence of the BSD-1-Clause license. On the other hand, HPND and HPND-sell-variant are all over the place. Signed-off-by: Peter Kjellerstedt --- meta/recipes-graphics/xorg-lib/libx11_1.7.2.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-graphics/xorg-lib/libx11_1.7.2.bb b/meta/recipes-graphics/xorg-lib/libx11_1.7.2.bb index 7ee2a9c16a..f429daaf47 100644 --- a/meta/recipes-graphics/xorg-lib/libx11_1.7.2.bb +++ b/meta/recipes-graphics/xorg-lib/libx11_1.7.2.bb @@ -20,7 +20,7 @@ SRC_URI[sha256sum] = "1cfa35e37aaabbe4792e9bb690468efefbfbf6b147d9c69d6f90d13c30 PROVIDES = "virtual/libx11" XORG_PN = "libX11" -LICENSE = "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause" +LICENSE = "MIT & MIT-style & BSD-1-Clause & HPND & HPND-sell-variant" LIC_FILES_CHKSUM = "file://COPYING;md5=172255dee66bb0151435b2d5d709fcf7" DEPENDS += "xorgproto xtrans libxcb" -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#157925): https://lists.openembedded.org/g/openembedded-core/message/157925 Mute This Topic: https://lists.openembedded.org/mt/86848638/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 2/2] libx11-compose-data: Update LICENSE to better reflect reality
There are no traces of neither the BSD-2-Clause license nor the
BSD-4-Clause license being used in the code. There is one occurrence
of the BSD-1-Clause license. On the other hand, HPND and
HPND-sell-variant are all over the place.
Signed-off-by: Peter Kjellerstedt
---
meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb
b/meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb
index e53ccc6aea..796980b7ca 100644
--- a/meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb
+++ b/meta/recipes-graphics/xorg-lib/libx11-compose-data_1.6.8.bb
@@ -8,7 +8,7 @@ python () {
require xorg-lib-common.inc
-LICENSE = "MIT & MIT-style & BSD-4-Clause & BSD-2-Clause"
+LICENSE = "MIT & MIT-style & BSD-1-Clause & HPND & HPND-sell-variant"
LIC_FILES_CHKSUM = "file://COPYING;md5=172255dee66bb0151435b2d5d709fcf7"
SRC_URI[md5sum] = "c5fa5a86a20e3591bed6c046498d4b8f"
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157926):
https://lists.openembedded.org/g/openembedded-core/message/157926
Mute This Topic: https://lists.openembedded.org/mt/86848639/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [bitbake-devel] [oe-core][PATCH 1/2] devtools: Initial recipe for repo 2.17.3
On Fri, 5 Nov 2021 at 19:05, Jasper Orschulko wrote: > > But that is exactly what we are doing, by integrating the repo fetcher > into the yocto workflow, thus improving the yocto tooling :) > Why reinvent the wheel, when you can reuse whats already there? You > wouldn't reinvent git just for yocto, would you? > What I mean is that I would try harder to find a workable setup while keeping the recipes for individual items that need to be built. For instance, devtool is capable of updating source revisions in recipes automatically, it may not work exactly as you want, but that can be fixed. Yes, repo itself is not proprietary, but your organizational workflow is. Particularly this: "if you want to create another version with different cmake flags, you would have to create copies of all 50ish recipes" looks odd. Why would you make copies? Just set the needed flags with a variable that is set from a global config, perhaps the distro or local.conf. Alex -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#157924): https://lists.openembedded.org/g/openembedded-core/message/157924 Mute This Topic: https://lists.openembedded.org/mt/86841424/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [bitbake-devel] [oe-core][PATCH 1/2] devtools: Initial recipe for repo 2.17.3
Hi Alex, > that you invented a custom, proprietary > workflow that you have to support entirely by > yourselves We are not though. We are integrating an established tool for multi-repository management into yocto. Google repo is not proprietary by the way, it is permissive licensed. It is just a little "special" in it's modus operandi. > instead of finding ways to do what you need > with standard yocto tooling, improving the > tooling where/if necessary. But that is exactly what we are doing, by integrating the repo fetcher into the yocto workflow, thus improving the yocto tooling :) Why reinvent the wheel, when you can reuse whats already there? You wouldn't reinvent git just for yocto, would you? Best regards, Jasper On 5 November 2021 18:46:27 CET, Alexander Kanavin wrote: >On Fri, 5 Nov 2021 at 16:24, Jasper Orschulko < >jasper.orschu...@iris-sensing.com> wrote: > >> >> In our case some binary which is made up from some 50ish separately >> versioned sub-components. We used to have separate recipes for each of >> this components and static link them using DEPENDS. However, this does >> not scale well. E.g. if you want to create another version with >> different cmake flags, you would have to create copies of all 50ish >> recipes. You could move all the components into a single recipe and do >> 50x git fetcher, but keeping this versioned is still painful. >> Especially since the developers mainly don't use yocto but use the SDK >> for cross-compiling. As such this used to mean, that versioning in the >> development workflow and the release workflow worked differently -> >> more maintenance work. >> >> With repo fetcher we can streamline the versioning within the yocto >> build process and the daily developer workflow, as both can fetch the >> repo manifest from a central stored git repo. The idea is, that the >> repo manifest defaults to develop branch for all component repos and if >> we want to create a release we can use repos own tooling to >> automatically create fixed refspecs from the development manifest. >> something like `repo manifest -r -o release-1.0.0.xml`, push that as a >> release to the manifest repo, set this release as refspec in the recipe >> within the meta layer and proceed with the release process. So no more >> manually maintaining the component versioning within the yocto recipes. >> > >I see. I don't particularly endorse that you invented a custom, proprietary >workflow that you have to support entirely by yourselves - instead of >finding ways to do what you need with standard yocto tooling, improving the >tooling where/if necessary. But if that works out ok for you, then fine :) > >Alex -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#157923): https://lists.openembedded.org/g/openembedded-core/message/157923 Mute This Topic: https://lists.openembedded.org/mt/86841424/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [bitbake-devel] [oe-core][PATCH 1/2] devtools: Initial recipe for repo 2.17.3
On Fri, 5 Nov 2021 at 16:24, Jasper Orschulko < jasper.orschu...@iris-sensing.com> wrote: > > In our case some binary which is made up from some 50ish separately > versioned sub-components. We used to have separate recipes for each of > this components and static link them using DEPENDS. However, this does > not scale well. E.g. if you want to create another version with > different cmake flags, you would have to create copies of all 50ish > recipes. You could move all the components into a single recipe and do > 50x git fetcher, but keeping this versioned is still painful. > Especially since the developers mainly don't use yocto but use the SDK > for cross-compiling. As such this used to mean, that versioning in the > development workflow and the release workflow worked differently -> > more maintenance work. > > With repo fetcher we can streamline the versioning within the yocto > build process and the daily developer workflow, as both can fetch the > repo manifest from a central stored git repo. The idea is, that the > repo manifest defaults to develop branch for all component repos and if > we want to create a release we can use repos own tooling to > automatically create fixed refspecs from the development manifest. > something like `repo manifest -r -o release-1.0.0.xml`, push that as a > release to the manifest repo, set this release as refspec in the recipe > within the meta layer and proceed with the release process. So no more > manually maintaining the component versioning within the yocto recipes. > I see. I don't particularly endorse that you invented a custom, proprietary workflow that you have to support entirely by yourselves - instead of finding ways to do what you need with standard yocto tooling, improving the tooling where/if necessary. But if that works out ok for you, then fine :) Alex -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#157922): https://lists.openembedded.org/g/openembedded-core/message/157922 Mute This Topic: https://lists.openembedded.org/mt/86841424/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH 3/6] linux-libc-headers: update to v5.15
On Fri, Nov 5, 2021 at 1:38 PM Khem Raj wrote:
>
>
>
> On 11/5/21 10:37 AM, Bruce Ashfield wrote:
> > On Fri, Nov 5, 2021 at 1:08 PM Khem Raj wrote:
> >>
> >> Couple of failures in meta-openembedded not too bad
> >>
> >> https://errors.yoctoproject.org/Errors/Build/135189/
> >
> > I'll have a look!
> >
> > Doesn't look ipx related, so another removal perhaps.
> >
> > Let me know if you are fixing it, just to save duplicated effort.
>
> I am looking at mctp you can look into sdbus-c++
Sounds good. likely the same root cause (I see mctp in the sdbus one
as well), they unified the structures in the kernel ... hopefully the
upstream for the packages have updated.
Bruce
>
> >
> > Bruce
> >
> >>
> >> On Fri, Nov 5, 2021 at 5:46 AM Bruce Ashfield
> >> wrote:
> >>>
> >>> On Fri, Nov 5, 2021 at 7:18 AM Richard Purdie
> >>> wrote:
>
> On Thu, 2021-11-04 at 15:48 -0400, bruce.ashfi...@gmail.com wrote:
> > From: Bruce Ashfield
> >
> > No patches needed refreshing or removal, so we just update the
> > SRC_URI and pick up the latest uapi / kernel headers.
> >
> > Signed-off-by: Bruce Ashfield
> > ---
> > meta/conf/distro/include/tcmode-default.inc | 2 +-
> > ...{linux-libc-headers_5.14.bb => linux-libc-headers_5.15.bb} | 4 ++--
> > 2 files changed, 3 insertions(+), 3 deletions(-)
> > rename
> > meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_5.14.bb =>
> > linux-libc-headers_5.15.bb} (81%)
> >
> > diff --git a/meta/conf/distro/include/tcmode-default.inc
> > b/meta/conf/distro/include/tcmode-default.inc
> > index 58f49800c4..86a6b50433 100644
> > --- a/meta/conf/distro/include/tcmode-default.inc
> > +++ b/meta/conf/distro/include/tcmode-default.inc
> > @@ -21,7 +21,7 @@ SDKGCCVERSION ?= "${GCCVERSION}"
> > BINUVERSION ?= "2.37%"
> > GDBVERSION ?= "10.%"
> > GLIBCVERSION ?= "2.34"
> > -LINUXLIBCVERSION ?= "5.14%"
> > +LINUXLIBCVERSION ?= "5.15%"
> > QEMUVERSION ?= "6.1%"
> > GOVERSION ?= "1.16%"
> > # This can not use wildcards like 8.0.% since it is also used in mesa
> > to denote
> > diff --git
> > a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.14.bb
> > b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.15.bb
> > similarity index 81%
> > rename from
> > meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.14.bb
> > rename to
> > meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.15.bb
> > index 282c04d79c..588cc3acd1 100644
> > --- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.14.bb
> > +++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.15.bb
> > @@ -14,7 +14,7 @@ SRC_URI:append = "\
> >
> > LIC_FILES_CHKSUM =
> > "file://COPYING;md5=6bc538ed5bd9a7fc9398086aedcd7e46"
> >
> > -SRC_URI[md5sum] = "a082ef5748b813abca0649dab8be5f52"
> > -SRC_URI[sha256sum] =
> > "7e068b5e0d26a62b10e5320b25dce57588cbbc6f781c090442138c9c9c3271b2"
> > +SRC_URI[md5sum] = "071d49ff4e020d58c04f9f3f76d3b594"
> > +SRC_URI[sha256sum] =
> > "57b2cf6991910e3b67a1b3490022e8a0674b6965c74c12da1e99d138d1991ee8"
> >
> >
>
> Looks like there is a musl issue with the ipx.h header in ppp:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/4299
> https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/4313
> >>>
> >>> ahah. Something my a-quick build didn't hit.
> >>>
> >>> I'll fire up a build here and see how we work around ipx.h going away.
> >>>
> >>> Bruce
> >>>
>
> Cheers,
>
> Richard
>
>
>
>
> >>>
> >>>
> >>> --
> >>> - Thou shalt not follow the NULL pointer, for chaos and madness await
> >>> thee at its end
> >>> - "Use the force Harry" - Gandalf, Star Trek II
> >
> >
> >
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157921):
https://lists.openembedded.org/g/openembedded-core/message/157921
Mute This Topic: https://lists.openembedded.org/mt/86824895/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH 3/6] linux-libc-headers: update to v5.15
On 11/5/21 10:37 AM, Bruce Ashfield wrote:
On Fri, Nov 5, 2021 at 1:08 PM Khem Raj wrote:
Couple of failures in meta-openembedded not too bad
https://errors.yoctoproject.org/Errors/Build/135189/
I'll have a look!
Doesn't look ipx related, so another removal perhaps.
Let me know if you are fixing it, just to save duplicated effort.
I am looking at mctp you can look into sdbus-c++
Bruce
On Fri, Nov 5, 2021 at 5:46 AM Bruce Ashfield wrote:
On Fri, Nov 5, 2021 at 7:18 AM Richard Purdie
wrote:
On Thu, 2021-11-04 at 15:48 -0400, bruce.ashfi...@gmail.com wrote:
From: Bruce Ashfield
No patches needed refreshing or removal, so we just update the
SRC_URI and pick up the latest uapi / kernel headers.
Signed-off-by: Bruce Ashfield
---
meta/conf/distro/include/tcmode-default.inc | 2 +-
...{linux-libc-headers_5.14.bb => linux-libc-headers_5.15.bb} | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_5.14.bb =>
linux-libc-headers_5.15.bb} (81%)
diff --git a/meta/conf/distro/include/tcmode-default.inc
b/meta/conf/distro/include/tcmode-default.inc
index 58f49800c4..86a6b50433 100644
--- a/meta/conf/distro/include/tcmode-default.inc
+++ b/meta/conf/distro/include/tcmode-default.inc
@@ -21,7 +21,7 @@ SDKGCCVERSION ?= "${GCCVERSION}"
BINUVERSION ?= "2.37%"
GDBVERSION ?= "10.%"
GLIBCVERSION ?= "2.34"
-LINUXLIBCVERSION ?= "5.14%"
+LINUXLIBCVERSION ?= "5.15%"
QEMUVERSION ?= "6.1%"
GOVERSION ?= "1.16%"
# This can not use wildcards like 8.0.% since it is also used in mesa to
denote
diff --git a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.14.bb
b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.15.bb
similarity index 81%
rename from meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.14.bb
rename to meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.15.bb
index 282c04d79c..588cc3acd1 100644
--- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.14.bb
+++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.15.bb
@@ -14,7 +14,7 @@ SRC_URI:append = "\
LIC_FILES_CHKSUM = "file://COPYING;md5=6bc538ed5bd9a7fc9398086aedcd7e46"
-SRC_URI[md5sum] = "a082ef5748b813abca0649dab8be5f52"
-SRC_URI[sha256sum] =
"7e068b5e0d26a62b10e5320b25dce57588cbbc6f781c090442138c9c9c3271b2"
+SRC_URI[md5sum] = "071d49ff4e020d58c04f9f3f76d3b594"
+SRC_URI[sha256sum] =
"57b2cf6991910e3b67a1b3490022e8a0674b6965c74c12da1e99d138d1991ee8"
Looks like there is a musl issue with the ipx.h header in ppp:
https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/4299
https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/4313
ahah. Something my a-quick build didn't hit.
I'll fire up a build here and see how we work around ipx.h going away.
Bruce
Cheers,
Richard
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157920):
https://lists.openembedded.org/g/openembedded-core/message/157920
Mute This Topic: https://lists.openembedded.org/mt/86824895/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH 3/6] linux-libc-headers: update to v5.15
On Fri, Nov 5, 2021 at 1:08 PM Khem Raj wrote:
>
> Couple of failures in meta-openembedded not too bad
>
> https://errors.yoctoproject.org/Errors/Build/135189/
I'll have a look!
Doesn't look ipx related, so another removal perhaps.
Let me know if you are fixing it, just to save duplicated effort.
Bruce
>
> On Fri, Nov 5, 2021 at 5:46 AM Bruce Ashfield
> wrote:
> >
> > On Fri, Nov 5, 2021 at 7:18 AM Richard Purdie
> > wrote:
> > >
> > > On Thu, 2021-11-04 at 15:48 -0400, bruce.ashfi...@gmail.com wrote:
> > > > From: Bruce Ashfield
> > > >
> > > > No patches needed refreshing or removal, so we just update the
> > > > SRC_URI and pick up the latest uapi / kernel headers.
> > > >
> > > > Signed-off-by: Bruce Ashfield
> > > > ---
> > > > meta/conf/distro/include/tcmode-default.inc | 2 +-
> > > > ...{linux-libc-headers_5.14.bb => linux-libc-headers_5.15.bb} | 4 ++--
> > > > 2 files changed, 3 insertions(+), 3 deletions(-)
> > > > rename
> > > > meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_5.14.bb =>
> > > > linux-libc-headers_5.15.bb} (81%)
> > > >
> > > > diff --git a/meta/conf/distro/include/tcmode-default.inc
> > > > b/meta/conf/distro/include/tcmode-default.inc
> > > > index 58f49800c4..86a6b50433 100644
> > > > --- a/meta/conf/distro/include/tcmode-default.inc
> > > > +++ b/meta/conf/distro/include/tcmode-default.inc
> > > > @@ -21,7 +21,7 @@ SDKGCCVERSION ?= "${GCCVERSION}"
> > > > BINUVERSION ?= "2.37%"
> > > > GDBVERSION ?= "10.%"
> > > > GLIBCVERSION ?= "2.34"
> > > > -LINUXLIBCVERSION ?= "5.14%"
> > > > +LINUXLIBCVERSION ?= "5.15%"
> > > > QEMUVERSION ?= "6.1%"
> > > > GOVERSION ?= "1.16%"
> > > > # This can not use wildcards like 8.0.% since it is also used in mesa
> > > > to denote
> > > > diff --git
> > > > a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.14.bb
> > > > b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.15.bb
> > > > similarity index 81%
> > > > rename from
> > > > meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.14.bb
> > > > rename to
> > > > meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.15.bb
> > > > index 282c04d79c..588cc3acd1 100644
> > > > --- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.14.bb
> > > > +++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.15.bb
> > > > @@ -14,7 +14,7 @@ SRC_URI:append = "\
> > > >
> > > > LIC_FILES_CHKSUM =
> > > > "file://COPYING;md5=6bc538ed5bd9a7fc9398086aedcd7e46"
> > > >
> > > > -SRC_URI[md5sum] = "a082ef5748b813abca0649dab8be5f52"
> > > > -SRC_URI[sha256sum] =
> > > > "7e068b5e0d26a62b10e5320b25dce57588cbbc6f781c090442138c9c9c3271b2"
> > > > +SRC_URI[md5sum] = "071d49ff4e020d58c04f9f3f76d3b594"
> > > > +SRC_URI[sha256sum] =
> > > > "57b2cf6991910e3b67a1b3490022e8a0674b6965c74c12da1e99d138d1991ee8"
> > > >
> > > >
> > >
> > > Looks like there is a musl issue with the ipx.h header in ppp:
> > >
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/4299
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/4313
> >
> > ahah. Something my a-quick build didn't hit.
> >
> > I'll fire up a build here and see how we work around ipx.h going away.
> >
> > Bruce
> >
> > >
> > > Cheers,
> > >
> > > Richard
> > >
> > >
> > >
> > >
> >
> >
> > --
> > - Thou shalt not follow the NULL pointer, for chaos and madness await
> > thee at its end
> > - "Use the force Harry" - Gandalf, Star Trek II
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157919):
https://lists.openembedded.org/g/openembedded-core/message/157919
Mute This Topic: https://lists.openembedded.org/mt/86824895/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH] ppp: fix build against 5.15 headers
On Fri, Nov 5, 2021 at 1:32 PM Khem Raj wrote:
>
>
>
> On 11/5/21 10:19 AM, Bruce Ashfield wrote:
> > From: Bruce Ashfield
> >
> > The 5.15 kernel has removed ipx support, along with the userspace
> > visible header.
> >
> > The build error was found for muslc, since it doesn't have a
> > fallback header, we disable it for both glibc/muslc.
> >
> > This support wasn't used previously (as it hasn't been very well
> > maintained in the kernel for several years), so we can simply
> > disable it in our build and wait for upstream to do a release that
> > drops the support.
> >
> > Although the tarball we use for our build (versus git), doesn't
> > use the autoconf disable flag to turn off the support, it is included
> > in this patch in case someone is building via git source base.
> >
> > Upstream-Status: Inappropriate [OE-specific configuration/headers]
> >
> > Signed-off-by: Bruce Ashfield
> > ---
> > ...1-ppp-fix-build-against-5.15-headers.patch | 36 +++
> > meta/recipes-connectivity/ppp/ppp_2.4.9.bb| 3 ++
> > 2 files changed, 39 insertions(+)
> > create mode 100644
> > meta/recipes-connectivity/ppp/ppp/0001-ppp-fix-build-against-5.15-headers.patch
> >
> > diff --git
> > a/meta/recipes-connectivity/ppp/ppp/0001-ppp-fix-build-against-5.15-headers.patch
> >
> > b/meta/recipes-connectivity/ppp/ppp/0001-ppp-fix-build-against-5.15-headers.patch
> > new file mode 100644
> > index 00..c91246dbf5
> > --- /dev/null
> > +++
> > b/meta/recipes-connectivity/ppp/ppp/0001-ppp-fix-build-against-5.15-headers.patch
> > @@ -0,0 +1,36 @@
> > +From aba3273273e826c6dc90f197ca9a3e800e826891 Mon Sep 17 00:00:00 2001
> > +From: Bruce Ashfield
> > +Date: Fri, 5 Nov 2021 12:41:35 -0400
> > +Subject: [PATCH] ppp: fix build against 5.15 headers
> > +
> > +The 5.15 kernel has removed ipx support, along with the userspace
> > +visible header.
> > +
> > +This support wasn't used previously (as it hasn't been very well
> > +maintained in the kernel for several years), so we can simply
> > +disable it in our build and wait for upstream to do a release that
> > +drops the support.
> > +
> > +Upstream-Status: Inappropriate [OE-specific configuration/headers]
> > +
> > +Signed-off-by: Bruce Ashfield
> > +---
> > + pppd/Makefile.linux | 2 +-
> > + 1 file changed, 1 insertion(+), 1 deletion(-)
> > +
> > +diff --git a/pppd/Makefile.linux b/pppd/Makefile.linux
> > +index 22837c5..23b9b22 100644
> > +--- a/pppd/Makefile.linux
> > b/pppd/Makefile.linux
> > +@@ -91,7 +91,7 @@ MAXOCTETS=y
> > +
> > + INCLUDE_DIRS= -I../include
> > +
> > +-COMPILE_FLAGS= -DHAVE_PATHS_H -DIPX_CHANGE -DHAVE_MMAP -pipe
> > ++COMPILE_FLAGS= -DHAVE_PATHS_H -DHAVE_MMAP -pipe
> > +
> > + CFLAGS= $(COPTS) $(COMPILE_FLAGS) $(INCLUDE_DIRS) '-DDESTDIR="@DESTDIR@"'
> > +
> > +--
> > +2.25.1
> > +
> > diff --git a/meta/recipes-connectivity/ppp/ppp_2.4.9.bb
> > b/meta/recipes-connectivity/ppp/ppp_2.4.9.bb
> > index 235595ff76..bd6435e69c 100644
> > --- a/meta/recipes-connectivity/ppp/ppp_2.4.9.bb
> > +++ b/meta/recipes-connectivity/ppp/ppp_2.4.9.bb
> > @@ -24,6 +24,7 @@ SRC_URI =
> > "https://download.samba.org/pub/${BPN}/${BP}.tar.gz \
> > file://ppp_on_boot \
> > file://provider \
> > file://ppp@.service \
> > + file://0001-ppp-fix-build-against-5.15-headers.patch \
> > "
> >
> > SRC_URI[sha256sum] =
> > "f938b35eccde533ea800b15a7445b2f1137da7f88e32a16898d02dee8adc058d"
> > @@ -39,6 +40,8 @@ EXTRA_OECONF = "--disable-strip"
> > #
> > EXTRA_OEMAKE += ' COPTS="${CFLAGS} -I${STAGING_INCDIR}/openssl
> > -I${S}/include"'
> >
> > +EXTRA_OECONF:append:libc-musl = " --disable-ipxcp"
>
> does this have to be musl specific ? given that kernel is dropping ipx
> support I think this should be disabled unconditionally isnt it ?
I covered that in my commit message :)
Bruce
>
> > +
> > do_configure () {
> > oe_runconf
> > }
> >
> >
> >
> >
> >
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157918):
https://lists.openembedded.org/g/openembedded-core/message/157918
Mute This Topic: https://lists.openembedded.org/mt/86846153/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH] ppp: fix build against 5.15 headers
On 11/5/21 10:19 AM, Bruce Ashfield wrote:
From: Bruce Ashfield
The 5.15 kernel has removed ipx support, along with the userspace
visible header.
The build error was found for muslc, since it doesn't have a
fallback header, we disable it for both glibc/muslc.
This support wasn't used previously (as it hasn't been very well
maintained in the kernel for several years), so we can simply
disable it in our build and wait for upstream to do a release that
drops the support.
Although the tarball we use for our build (versus git), doesn't
use the autoconf disable flag to turn off the support, it is included
in this patch in case someone is building via git source base.
Upstream-Status: Inappropriate [OE-specific configuration/headers]
Signed-off-by: Bruce Ashfield
---
...1-ppp-fix-build-against-5.15-headers.patch | 36 +++
meta/recipes-connectivity/ppp/ppp_2.4.9.bb| 3 ++
2 files changed, 39 insertions(+)
create mode 100644
meta/recipes-connectivity/ppp/ppp/0001-ppp-fix-build-against-5.15-headers.patch
diff --git
a/meta/recipes-connectivity/ppp/ppp/0001-ppp-fix-build-against-5.15-headers.patch
b/meta/recipes-connectivity/ppp/ppp/0001-ppp-fix-build-against-5.15-headers.patch
new file mode 100644
index 00..c91246dbf5
--- /dev/null
+++
b/meta/recipes-connectivity/ppp/ppp/0001-ppp-fix-build-against-5.15-headers.patch
@@ -0,0 +1,36 @@
+From aba3273273e826c6dc90f197ca9a3e800e826891 Mon Sep 17 00:00:00 2001
+From: Bruce Ashfield
+Date: Fri, 5 Nov 2021 12:41:35 -0400
+Subject: [PATCH] ppp: fix build against 5.15 headers
+
+The 5.15 kernel has removed ipx support, along with the userspace
+visible header.
+
+This support wasn't used previously (as it hasn't been very well
+maintained in the kernel for several years), so we can simply
+disable it in our build and wait for upstream to do a release that
+drops the support.
+
+Upstream-Status: Inappropriate [OE-specific configuration/headers]
+
+Signed-off-by: Bruce Ashfield
+---
+ pppd/Makefile.linux | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/pppd/Makefile.linux b/pppd/Makefile.linux
+index 22837c5..23b9b22 100644
+--- a/pppd/Makefile.linux
b/pppd/Makefile.linux
+@@ -91,7 +91,7 @@ MAXOCTETS=y
+
+ INCLUDE_DIRS= -I../include
+
+-COMPILE_FLAGS= -DHAVE_PATHS_H -DIPX_CHANGE -DHAVE_MMAP -pipe
++COMPILE_FLAGS= -DHAVE_PATHS_H -DHAVE_MMAP -pipe
+
+ CFLAGS= $(COPTS) $(COMPILE_FLAGS) $(INCLUDE_DIRS) '-DDESTDIR="@DESTDIR@"'
+
+--
+2.25.1
+
diff --git a/meta/recipes-connectivity/ppp/ppp_2.4.9.bb
b/meta/recipes-connectivity/ppp/ppp_2.4.9.bb
index 235595ff76..bd6435e69c 100644
--- a/meta/recipes-connectivity/ppp/ppp_2.4.9.bb
+++ b/meta/recipes-connectivity/ppp/ppp_2.4.9.bb
@@ -24,6 +24,7 @@ SRC_URI = "https://download.samba.org/pub/${BPN}/${BP}.tar.gz
\
file://ppp_on_boot \
file://provider \
file://ppp@.service \
+ file://0001-ppp-fix-build-against-5.15-headers.patch \
"
SRC_URI[sha256sum] = "f938b35eccde533ea800b15a7445b2f1137da7f88e32a16898d02dee8adc058d"
@@ -39,6 +40,8 @@ EXTRA_OECONF = "--disable-strip"
#
EXTRA_OEMAKE += ' COPTS="${CFLAGS} -I${STAGING_INCDIR}/openssl
-I${S}/include"'
+EXTRA_OECONF:append:libc-musl = " --disable-ipxcp"
does this have to be musl specific ? given that kernel is dropping ipx
support I think this should be disabled unconditionally isnt it ?
+
do_configure () {
oe_runconf
}
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157917):
https://lists.openembedded.org/g/openembedded-core/message/157917
Mute This Topic: https://lists.openembedded.org/mt/86846153/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH 5/7] librsvg: set the needed atomic configuration flags directly per-target
On 11/5/21 1:48 AM, Alexander Kanavin wrote:
Do not try to mangle the upstream list of targets;
after discussion with upstream it turns out it's neither
necessary nor upstreamable:
https://github.com/crossbeam-rs/crossbeam/pull/751
right, I had my reservations about this patch as well. We should try to
play with rust's target detection as much as we can.
Signed-off-by: Alexander Kanavin
---
...check-only-the-architecture-not-the-.patch | 143 --
meta/recipes-gnome/librsvg/librsvg_2.52.3.bb | 4 +-
2 files changed, 3 insertions(+), 144 deletions(-)
delete mode 100644
meta/recipes-gnome/librsvg/librsvg/0001-crossbeam-utils-check-only-the-architecture-not-the-.patch
diff --git
a/meta/recipes-gnome/librsvg/librsvg/0001-crossbeam-utils-check-only-the-architecture-not-the-.patch
b/meta/recipes-gnome/librsvg/librsvg/0001-crossbeam-utils-check-only-the-architecture-not-the-.patch
deleted file mode 100644
index 0c1cf59eff..00
---
a/meta/recipes-gnome/librsvg/librsvg/0001-crossbeam-utils-check-only-the-architecture-not-the-.patch
+++ /dev/null
@@ -1,143 +0,0 @@
-From 70557b217644901daaf9d8ef793f5e84c937762e Mon Sep 17 00:00:00 2001
-From: Alexander Kanavin
-Date: Tue, 5 Oct 2021 23:41:59 +0200
-Subject: [PATCH] crossbeam-utils: check only the architecture, not the whole
- target string
-
-There can be custom targets in use, and it's not possible to make a list
-of them; for the check only the first item in the target string is actually
-relevant (the architecture of the target).
-
-Upstream-Status: Pending [needs an upstream ticket and possibly a rework of
list generator script]
-Signed-off-by: Alexander Kanavin
- vendor/crossbeam-utils/.cargo-checksum.json | 4 +-
- vendor/crossbeam-utils/build.rs | 8 ++-
- vendor/crossbeam-utils/no_atomic.rs | 78 -
- 3 files changed, 38 insertions(+), 52 deletions(-)
-
a/vendor/crossbeam-utils/.cargo-checksum.json
-+++ b/vendor/crossbeam-utils/.cargo-checksum.json
-@@ -1 +1,3 @@
--{"files":{"CHANGELOG.md":"5242f1740c65509c465c9a36326d344722facff5f5e58dd064f7b77806b83a46","Cargo.toml":"ac35a7b8ccb16f1ab256951576537aa4179a316c068929c2acef89e0adc12319","LICENSE-APACHE":"a60eea817514531668d7e00765731449fe14d059d3249e0bc93b36de45f759f2","LICENSE-MIT":"5734ed989dfca1f625b40281ee9f4530f91b2411ec01cb748223e7eb87e201ab","README.md":"dfa9fbed47c344c134a63c84b7c0e4651baeac1554b7b3266d0e38643743fc33","benches/atomic_cell.rs":"c927eb3cd1e5ecc4b91adbc3bde98af15ffab4086190792ba64d5cde0e24df3d","build.rs":"68cfc4be02429834a19411fba29cb1cb52c841f03ac8104d1bae59a8b2184f9c","no_atomic.rs":"a2621c1b029c614fb0ab8e3f5cda2e839df88d90d26133181c1b901965f7eec4","src/atomic/atomic_cell.rs":"1a3a1e073340317b5ce7a94e29c6a87db89ff7e00da6b92cb3c0339364c3b084","src/atomic/consume.rs":"7a7736fcd64f6473dfea7653559ffc5e1a2a234df43835f8aa8734862145ac15","src/atomic/mod.rs":"7f6afd5bd0da1f7b51765ab04da4e5f683588ac2d23506e61bf7007bb1e61ba2","src/atomic/seq_lock.rs":"27182e6b87a9db73c5f6831759f8625f9fcdec3c2828204c444aef04f427735a","src/atomic/seq_lock_wide.rs":"9888dd03116bb89ca36d4ab8d5a0b5032107a2983a7eb8024454263b09080088","src/backoff.rs":"7cc7754e15f69b52e92a70d4f49d1bc274693455a0933a2d7eb0605806566af3","src/cache_padded.rs":"6a512698115ad0d5a5b163dbd7a83247e1f1c146c4a30f3fc74b952e3b767b59","src/lib.rs":"6f1bcf157abe06ad8458a53e865bf8efab9fad4a9424790147cee8fefb3795d8","src/sync/mod.rs":"59986f559a8f170a4b3247ab2eea2460b09809d87c8110ed88e4e7103d3519dc","src/sync/parker.rs":"ba8f75bff31b8be9275808e8f393e71cc682dfc1109ceccb12f69a3700cff5be","src/sync/sharded_lock.rs":"14be659744918d0b27db24c56b41c618b0f0484b6761da46561023d96c4c120f","src/sync/wait_group.rs":"32e946a7581c55f8aa9904527b92b177c538fa0cf7cbcfa1d1f25990582cb6ea","src/thread.rs":"0eb5ec1d3c1b40600d88eb70539d14276e32307f5bed2b679f50f6a20777a01e","tests/atomic_cell.rs":"6c9453384ecbbe76f8b97b62f022d478d3a76b4eae1e960f49790970f5d52158","tests/cache_padded.rs":"1bfaff8354c8184e1ee1f902881ca9400b60effb273b0d3f752801a483d2b66d","tests/parker.rs":"6def4721287d9d70b1cfd63ebb34e1c83fbb3376edbad2bc8aac6ef69dd99d20","tests/sharded_lock.rs":"726025ce6351fb56ed629d5a56bdf6e833b7afc5dedfa08de0b056c726b6c26d","tests/thread.rs":"9a7d7d3028c552fd834c68598b04a1cc252a816bc20ab62cec060d6cd09cab10","tests/wait_group.rs":"ad8f0cdfed31f9594a2e0737234d418f8b924d784a4db8d7e469deab8c95f5f8"},"package":"d82cfc11ce7f2c3faef78d8a684447b40d503d9681acebed6cb728d45940c4db"}
-\ No newline at end of file
[OE-core] [PATCH] ppp: fix build against 5.15 headers
From: Bruce Ashfield
The 5.15 kernel has removed ipx support, along with the userspace
visible header.
The build error was found for muslc, since it doesn't have a
fallback header, we disable it for both glibc/muslc.
This support wasn't used previously (as it hasn't been very well
maintained in the kernel for several years), so we can simply
disable it in our build and wait for upstream to do a release that
drops the support.
Although the tarball we use for our build (versus git), doesn't
use the autoconf disable flag to turn off the support, it is included
in this patch in case someone is building via git source base.
Upstream-Status: Inappropriate [OE-specific configuration/headers]
Signed-off-by: Bruce Ashfield
---
...1-ppp-fix-build-against-5.15-headers.patch | 36 +++
meta/recipes-connectivity/ppp/ppp_2.4.9.bb| 3 ++
2 files changed, 39 insertions(+)
create mode 100644
meta/recipes-connectivity/ppp/ppp/0001-ppp-fix-build-against-5.15-headers.patch
diff --git
a/meta/recipes-connectivity/ppp/ppp/0001-ppp-fix-build-against-5.15-headers.patch
b/meta/recipes-connectivity/ppp/ppp/0001-ppp-fix-build-against-5.15-headers.patch
new file mode 100644
index 00..c91246dbf5
--- /dev/null
+++
b/meta/recipes-connectivity/ppp/ppp/0001-ppp-fix-build-against-5.15-headers.patch
@@ -0,0 +1,36 @@
+From aba3273273e826c6dc90f197ca9a3e800e826891 Mon Sep 17 00:00:00 2001
+From: Bruce Ashfield
+Date: Fri, 5 Nov 2021 12:41:35 -0400
+Subject: [PATCH] ppp: fix build against 5.15 headers
+
+The 5.15 kernel has removed ipx support, along with the userspace
+visible header.
+
+This support wasn't used previously (as it hasn't been very well
+maintained in the kernel for several years), so we can simply
+disable it in our build and wait for upstream to do a release that
+drops the support.
+
+Upstream-Status: Inappropriate [OE-specific configuration/headers]
+
+Signed-off-by: Bruce Ashfield
+---
+ pppd/Makefile.linux | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/pppd/Makefile.linux b/pppd/Makefile.linux
+index 22837c5..23b9b22 100644
+--- a/pppd/Makefile.linux
b/pppd/Makefile.linux
+@@ -91,7 +91,7 @@ MAXOCTETS=y
+
+ INCLUDE_DIRS= -I../include
+
+-COMPILE_FLAGS= -DHAVE_PATHS_H -DIPX_CHANGE -DHAVE_MMAP -pipe
++COMPILE_FLAGS= -DHAVE_PATHS_H -DHAVE_MMAP -pipe
+
+ CFLAGS= $(COPTS) $(COMPILE_FLAGS) $(INCLUDE_DIRS) '-DDESTDIR="@DESTDIR@"'
+
+--
+2.25.1
+
diff --git a/meta/recipes-connectivity/ppp/ppp_2.4.9.bb
b/meta/recipes-connectivity/ppp/ppp_2.4.9.bb
index 235595ff76..bd6435e69c 100644
--- a/meta/recipes-connectivity/ppp/ppp_2.4.9.bb
+++ b/meta/recipes-connectivity/ppp/ppp_2.4.9.bb
@@ -24,6 +24,7 @@ SRC_URI = "https://download.samba.org/pub/${BPN}/${BP}.tar.gz
\
file://ppp_on_boot \
file://provider \
file://ppp@.service \
+ file://0001-ppp-fix-build-against-5.15-headers.patch \
"
SRC_URI[sha256sum] =
"f938b35eccde533ea800b15a7445b2f1137da7f88e32a16898d02dee8adc058d"
@@ -39,6 +40,8 @@ EXTRA_OECONF = "--disable-strip"
#
EXTRA_OEMAKE += ' COPTS="${CFLAGS} -I${STAGING_INCDIR}/openssl -I${S}/include"'
+EXTRA_OECONF:append:libc-musl = " --disable-ipxcp"
+
do_configure () {
oe_runconf
}
--
2.19.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157915):
https://lists.openembedded.org/g/openembedded-core/message/157915
Mute This Topic: https://lists.openembedded.org/mt/86846153/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH 3/6] linux-libc-headers: update to v5.15
Couple of failures in meta-openembedded not too bad
https://errors.yoctoproject.org/Errors/Build/135189/
On Fri, Nov 5, 2021 at 5:46 AM Bruce Ashfield wrote:
>
> On Fri, Nov 5, 2021 at 7:18 AM Richard Purdie
> wrote:
> >
> > On Thu, 2021-11-04 at 15:48 -0400, bruce.ashfi...@gmail.com wrote:
> > > From: Bruce Ashfield
> > >
> > > No patches needed refreshing or removal, so we just update the
> > > SRC_URI and pick up the latest uapi / kernel headers.
> > >
> > > Signed-off-by: Bruce Ashfield
> > > ---
> > > meta/conf/distro/include/tcmode-default.inc | 2 +-
> > > ...{linux-libc-headers_5.14.bb => linux-libc-headers_5.15.bb} | 4 ++--
> > > 2 files changed, 3 insertions(+), 3 deletions(-)
> > > rename
> > > meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_5.14.bb =>
> > > linux-libc-headers_5.15.bb} (81%)
> > >
> > > diff --git a/meta/conf/distro/include/tcmode-default.inc
> > > b/meta/conf/distro/include/tcmode-default.inc
> > > index 58f49800c4..86a6b50433 100644
> > > --- a/meta/conf/distro/include/tcmode-default.inc
> > > +++ b/meta/conf/distro/include/tcmode-default.inc
> > > @@ -21,7 +21,7 @@ SDKGCCVERSION ?= "${GCCVERSION}"
> > > BINUVERSION ?= "2.37%"
> > > GDBVERSION ?= "10.%"
> > > GLIBCVERSION ?= "2.34"
> > > -LINUXLIBCVERSION ?= "5.14%"
> > > +LINUXLIBCVERSION ?= "5.15%"
> > > QEMUVERSION ?= "6.1%"
> > > GOVERSION ?= "1.16%"
> > > # This can not use wildcards like 8.0.% since it is also used in mesa to
> > > denote
> > > diff --git
> > > a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.14.bb
> > > b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.15.bb
> > > similarity index 81%
> > > rename from
> > > meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.14.bb
> > > rename to
> > > meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.15.bb
> > > index 282c04d79c..588cc3acd1 100644
> > > --- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.14.bb
> > > +++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.15.bb
> > > @@ -14,7 +14,7 @@ SRC_URI:append = "\
> > >
> > > LIC_FILES_CHKSUM = "file://COPYING;md5=6bc538ed5bd9a7fc9398086aedcd7e46"
> > >
> > > -SRC_URI[md5sum] = "a082ef5748b813abca0649dab8be5f52"
> > > -SRC_URI[sha256sum] =
> > > "7e068b5e0d26a62b10e5320b25dce57588cbbc6f781c090442138c9c9c3271b2"
> > > +SRC_URI[md5sum] = "071d49ff4e020d58c04f9f3f76d3b594"
> > > +SRC_URI[sha256sum] =
> > > "57b2cf6991910e3b67a1b3490022e8a0674b6965c74c12da1e99d138d1991ee8"
> > >
> > >
> >
> > Looks like there is a musl issue with the ipx.h header in ppp:
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/4299
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/4313
>
> ahah. Something my a-quick build didn't hit.
>
> I'll fire up a build here and see how we work around ipx.h going away.
>
> Bruce
>
> >
> > Cheers,
> >
> > Richard
> >
> >
> >
> >
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157914):
https://lists.openembedded.org/g/openembedded-core/message/157914
Mute This Topic: https://lists.openembedded.org/mt/86824895/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [bitbake-devel] [oe-core][PATCH v2 1/2] devtools: Initial recipe for repo 2.17.3
> -Original Message-
> From: Jasper Orschulko
> Sent: den 5 november 2021 17:32
> To: openembedded-core@lists.openembedded.org; Peter Kjellerstedt
> ; jas...@fancydomain.eu
> Cc: mar...@mko.dev; Daniel Baumgart ;
> bitbake-de...@lists.openembedded.org
> Subject: Re: [bitbake-devel] [oe-core][PATCH v2 1/2] devtools: Initial
> recipe for repo 2.17.3
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi Peter,
>
> > Change to RDEPENDS:${PN} and move it to between do_install() and
> > BBCLASSEXTEND.
>
> What does this do? The Yocto manual only mentions RDEPENDS_${PN}.
The syntax for bitbake variable overrides were changed with the
Honister release, see:
https://docs.yoctoproject.org/3.4/migration-guides/migration-3.4.html#override-syntax-changes
//Peter
>
> ack to the rest.
>
> - --
> With best regards
>
> Jasper Orschulko
> DevOps Engineer
>
> Tel. +49 30 58 58 14 265
> Fax +49 30 58 58 14 999
> jasper.orschu...@iris-sensing.com
>
> • • • • • • • • • • • • • • • • • • • • • • • • • •
>
> iris-GmbH
> infrared & intelligent sensors
> Schnellerstraße 1-5 | 12439 Berlin
>
> https://iris-sensing.com/
>
>
>
>
>
> On Fri, 2021-11-05 at 16:11 +, Peter Kjellerstedt wrote:
> > > -Original Message-
> > > From:
> > > bitbake-de...@lists.openembedded.org de...@lists.openembedded.org
> > > > On Behalf Of Jasper Orschulko via lists.openembedded.org
> > > Sent: den 5 november 2021 16:32
> > > To: openembedded-core@lists.openembedded.org
> > > Cc: mar...@mko.dev; daniel.baumg...@iris-sensing.com;
> > > bitbake-de...@lists.openembedded.org; Jasper Orschulko
> > >
> > > Subject: [bitbake-devel] [oe-core][PATCH v2 1/2] devtools: Initial
> > > recipe for repo 2.17.3
> >
> > Change the Git subject to:
> >
> > repo: Add recipe for 2.17.3
> >
> > >
> > > From: Jasper Orschulko
> > >
> > > Add a recipe for repo, prerequisite for the repo fetcher.
> > >
> > > Signed-off-by: Jasper Orschulko
> > > ---
> > > .../repo/files/0001-python3-shebang.patch | 21
> > > .../0001-Set-REPO_REV-to-v2.17.3.patch | 33
> > > +++
> > > meta/recipes-devtools/repo/repo.inc | 25 ++
> > > meta/recipes-devtools/repo/repo_2.17.3.bb | 7
> > > 4 files changed, 86 insertions(+)
> > > create mode 100644 meta/recipes-devtools/repo/files/0001-python3-
> > > shebang.patch
> > > create mode 100644 meta/recipes-devtools/repo/repo-2.17.3/0001-Set-
> > > REPO_REV-to-v2.17.3.patch
> > > create mode 100644 meta/recipes-devtools/repo/repo.inc
> > > create mode 100644 meta/recipes-devtools/repo/repo_2.17.3.bb
> > >
> > > diff --git a/meta/recipes-devtools/repo/files/0001-python3-
> > > shebang.patch > b/meta/recipes-devtools/repo/files/0001-python3-
> > > shebang.patch
> > > new file mode 100644
> > > index 00..09ccf58264
> > > --- /dev/null
> > > +++ b/meta/recipes-devtools/repo/files/0001-python3-shebang.patch
> > > @@ -0,0 +1,21 @@
> > > +From b8e84b202cd302a7c99288d3835dc9c63071f8f2 Mon Sep 17 00:00:00
> > > 2001
> > > +From: Jasper Orschulko
> > > +Date: Tue, 14 Sep 2021 16:46:51 +0200
> > > +Subject: [PATCH] python3 shebang
> > > +
> > > +---
> > > + repo | 2 +-
> > > + 1 file changed, 1 insertion(+), 1 deletion(-)
> > > +
> > > +diff --git a/repo b/repo
> > > +index b13e34c..205e0e5 100755
> > > +--- a/repo
> > > b/repo
> > > +@@ -1,4 +1,4 @@
> > > +-#!/usr/bin/env python
> > > ++#!/usr/bin/env python3
> > > + # -*- coding:utf-8 -*-
> > > + #
> > > + # Copyright (C) 2008 The Android Open Source Project
> > > +--
> > > +2.33.0
> > > diff --git a/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-
> > > REPO_REV-to-v2.17.3.patch b/meta/recipes-devtools/repo/repo-
> > > 2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
> > > new file mode 100644
> > > index 00..4d76bfc5d2
> > > --- /dev/null
> > > +++ b/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-
> > > v2.17.3.patch
> > > @@ -0,0 +1,33 @@
> > > +From bdd2a528da59c28db8ae2986834926de7cebf3ab Mon Sep 17 00:00:00
> > > 2001
> > > +From: Jasper Orschulko
> > > +Date: Thu, 4 Nov 2021 16:55:12 +0100
> > > +Subject: [PATCH] Set REPO_REV to v2.17.3
> > > +
> > > +repo is an unusual tool because it downloads all of its own Python
> > > modules
> > > +using GPG-signed git tags, and stores those files as part of the
> > > project
> > > +that it is working with.
> > > +
> > > +So in order to have a reproducible repo installation within the
> > > project
> > > +folders, we hardcode the REPO_REV variable to this recipes PV.
> >
> > Change "this recipes PV" to "a SHA1 that corresponds to the version
> > of the recipe."
> >
> > > +
> > > +Upstream-Status: Inappropriate [configuration]
> > > +Signed-off-by: Jasper Orschulko
> > > +---
> > > + repo | 2 +-
> > > + 1 file changed, 1 insertion(+), 1 deletion(-)
> > > +
> > > +diff --git a/repo b/repo
> > > +index 4cddbf1..cf5f6b1 100755
> > > +--- a/repo
> > > b/repo
> > > +@@ -142,7 +142,7 @@ if __name__ == '__main__':
>
[OE-core] [PATCH] scons: support out-of-tree builds
SCons has a slightly unusual implementation of out-of-tree builds where
there is no standard way of doing it. However, if a recipe sets B to
the idiomatic ${WORKDIR}/build and passes the right arguments so that this
is used then scons will fail as it is trying to find the SConstruct file
in ${B} not ${S}.
Always pass --directory=${S} to scons so that the SConstruct file can be
found, and don't call --clean if out-of-tree builds are being used as
we would have just deleted the entire build tree already.
Signed-off-by: Ross Burton
---
meta/classes/scons.bbclass | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/meta/classes/scons.bbclass b/meta/classes/scons.bbclass
index 4f3ae502ef..80f8382107 100644
--- a/meta/classes/scons.bbclass
+++ b/meta/classes/scons.bbclass
@@ -5,9 +5,9 @@ DEPENDS += "python3-scons-native"
EXTRA_OESCONS ?= ""
do_configure() {
- if [ -n "${CONFIGURESTAMPFILE}" ]; then
+ if [ -n "${CONFIGURESTAMPFILE}" -a "${S}" = "${B}" ]; then
if [ -e "${CONFIGURESTAMPFILE}" -a "`cat
${CONFIGURESTAMPFILE}`" != "${BB_TASKHASH}" -a "${CLEANBROKEN}" != "1" ]; then
- ${STAGING_BINDIR_NATIVE}/scons --clean PREFIX=${prefix}
prefix=${prefix} ${EXTRA_OESCONS}
+ ${STAGING_BINDIR_NATIVE}/scons --directory=${S} --clean
PREFIX=${prefix} prefix=${prefix} ${EXTRA_OESCONS}
fi
mkdir -p `dirname ${CONFIGURESTAMPFILE}`
@@ -16,12 +16,12 @@ do_configure() {
}
scons_do_compile() {
- ${STAGING_BINDIR_NATIVE}/scons ${PARALLEL_MAKE} PREFIX=${prefix}
prefix=${prefix} ${EXTRA_OESCONS} || \
+ ${STAGING_BINDIR_NATIVE}/scons --directory=${S} ${PARALLEL_MAKE}
PREFIX=${prefix} prefix=${prefix} ${EXTRA_OESCONS} || \
die "scons build execution failed."
}
scons_do_install() {
- ${STAGING_BINDIR_NATIVE}/scons install_root=${D}${prefix}
PREFIX=${prefix} prefix=${prefix} ${EXTRA_OESCONS} install || \
+ ${STAGING_BINDIR_NATIVE}/scons --directory=${S}
install_root=${D}${prefix} PREFIX=${prefix} prefix=${prefix} ${EXTRA_OESCONS}
install || \
die "scons install execution failed."
}
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157912):
https://lists.openembedded.org/g/openembedded-core/message/157912
Mute This Topic: https://lists.openembedded.org/mt/86845618/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH 1/2] gdb: Upgrade to 11.1
On Fri, Nov 5, 2021 at 4:19 AM Richard Purdie
wrote:
>
> On Wed, 2021-11-03 at 18:30 -0700, Khem Raj wrote:
> > Drop backported patches
> > Changes are here [1]
> >
> > [1] https://sourceware.org/pipermail/gdb-announce/2021/000129.html
> >
> > Signed-off-by: Khem Raj
> > ---
> > meta/conf/distro/include/tcmode-default.inc | 2 +-
> > .../gdb/{gdb-10.2.inc => gdb-11.1.inc}| 14 +-
> > ...ian_10.2.bb => gdb-cross-canadian_11.1.bb} | 0
> > .../{gdb-cross_10.2.bb => gdb-cross_11.1.bb} | 0
> > ...make-man-install-relative-to-DESTDIR.patch | 20 +-
> > ...ux-nat-Define-_ABIO32-if-not-defined.patch | 8 +-
> > ...e-pt_regs-uapi_pt_regs-on-GLIBC-syst.patch | 10 +-
> > ...port-for-Renesas-SH-sh4-architecture.patch | 39 +-
> > ...readline.a-when-using-disable-static.patch | 12 +-
> > .../gdb/gdb/0006-use-asm-sgidefs.h.patch | 8 +-
> > ...atch => 0007-Change-order-of-CFLAGS.patch} | 12 +-
> > ...8-resolve-restrict-keyword-conflict.patch} | 8 +-
> > ...> 0009-Fix-invalid-sigprocmask-call.patch} | 8 +-
> > ...h => 0010-gdbserver-ctrl-c-handling.patch} | 10 +-
> > ...-arc-Add-support-for-signal-handlers.patch | 218 -
> > ...-for-signal-frames-for-Linux-targets.patch | 232 --
> > ...count-the-REGNUM-in-supply-collect-g.patch | 104 -
> > ...-native-support-for-ARC-in-GNU-Linux.patch | 414 --
> > .../gdb/{gdb_10.2.bb => gdb_11.1.bb} | 0
> > 19 files changed, 74 insertions(+), 1045 deletions(-)
> > rename meta/recipes-devtools/gdb/{gdb-10.2.inc => gdb-11.1.inc} (56%)
> > rename meta/recipes-devtools/gdb/{gdb-cross-canadian_10.2.bb =>
> > gdb-cross-canadian_11.1.bb} (100%)
> > rename meta/recipes-devtools/gdb/{gdb-cross_10.2.bb => gdb-cross_11.1.bb}
> > (100%)
> > rename meta/recipes-devtools/gdb/gdb/{0008-Change-order-of-CFLAGS.patch =>
> > 0007-Change-order-of-CFLAGS.patch} (75%)
> > rename
> > meta/recipes-devtools/gdb/gdb/{0009-resolve-restrict-keyword-conflict.patch
> > => 0008-resolve-restrict-keyword-conflict.patch} (91%)
> > rename
> > meta/recipes-devtools/gdb/gdb/{0010-Fix-invalid-sigprocmask-call.patch =>
> > 0009-Fix-invalid-sigprocmask-call.patch} (90%)
> > rename meta/recipes-devtools/gdb/gdb/{0011-gdbserver-ctrl-c-handling.patch
> > => 0010-gdbserver-ctrl-c-handling.patch} (82%)
> > delete mode 100644
> > meta/recipes-devtools/gdb/gdb/0012-arc-Add-support-for-signal-handlers.patch
> > delete mode 100644
> > meta/recipes-devtools/gdb/gdb/0013-arc-Add-support-for-signal-frames-for-Linux-targets.patch
> > delete mode 100644
> > meta/recipes-devtools/gdb/gdb/0014-arc-Take-into-account-the-REGNUM-in-supply-collect-g.patch
> > delete mode 100644
> > meta/recipes-devtools/gdb/gdb/0015-gdb-Add-native-support-for-ARC-in-GNU-Linux.patch
> > rename meta/recipes-devtools/gdb/{gdb_10.2.bb => gdb_11.1.bb} (100%)
>
> Breaks on mingw:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/4299
>
I see
| sys-linux.c:140:10: fatal error: linux/ipx.h: No such file or directory
| 140 | #include
| | ^
| compilation terminated.
| make[1]: *** [: sys-linux.o] Error 1
| make[1]: Leaving directory
'/home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/core2-32-poky-linux-musl/ppp/2.4.9-r0/ppp-2.4.9/pppd'
perhaps wrong link ?
> Cheers,
>
> Richard
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157911):
https://lists.openembedded.org/g/openembedded-core/message/157911
Mute This Topic: https://lists.openembedded.org/mt/86807405/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [bitbake-devel] [oe-core][PATCH v2 1/2] devtools: Initial recipe for repo 2.17.3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Peter,
> Change to RDEPENDS:${PN} and move it to between do_install() and
> BBCLASSEXTEND.
What does this do? The Yocto manual only mentions RDEPENDS_${PN}.
ack to the rest.
- --
With best regards
Jasper Orschulko
DevOps Engineer
Tel. +49 30 58 58 14 265
Fax +49 30 58 58 14 999
jasper.orschu...@iris-sensing.com
• • • • • • • • • • • • • • • • • • • • • • • • • •
iris-GmbH
infrared & intelligent sensors
Schnellerstraße 1-5 | 12439 Berlin
https://iris-sensing.com/
On Fri, 2021-11-05 at 16:11 +, Peter Kjellerstedt wrote:
> > -Original Message-
> > From:
> > bitbake-de...@lists.openembedded.org > > On Behalf Of Jasper Orschulko via lists.openembedded.org
> > Sent: den 5 november 2021 16:32
> > To: openembedded-core@lists.openembedded.org
> > Cc: mar...@mko.dev; daniel.baumg...@iris-sensing.com;
> > bitbake-de...@lists.openembedded.org; Jasper Orschulko
> >
> > Subject: [bitbake-devel] [oe-core][PATCH v2 1/2] devtools: Initial
> > recipe for repo 2.17.3
>
> Change the Git subject to:
>
> repo: Add recipe for 2.17.3
>
> >
> > From: Jasper Orschulko
> >
> > Add a recipe for repo, prerequisite for the repo fetcher.
> >
> > Signed-off-by: Jasper Orschulko
> > ---
> > .../repo/files/0001-python3-shebang.patch | 21
> > .../0001-Set-REPO_REV-to-v2.17.3.patch | 33
> > +++
> > meta/recipes-devtools/repo/repo.inc | 25 ++
> > meta/recipes-devtools/repo/repo_2.17.3.bb | 7
> > 4 files changed, 86 insertions(+)
> > create mode 100644 meta/recipes-devtools/repo/files/0001-python3-
> > shebang.patch
> > create mode 100644 meta/recipes-devtools/repo/repo-2.17.3/0001-Set-
> > REPO_REV-to-v2.17.3.patch
> > create mode 100644 meta/recipes-devtools/repo/repo.inc
> > create mode 100644 meta/recipes-devtools/repo/repo_2.17.3.bb
> >
> > diff --git a/meta/recipes-devtools/repo/files/0001-python3-
> > shebang.patch > b/meta/recipes-devtools/repo/files/0001-python3-
> > shebang.patch
> > new file mode 100644
> > index 00..09ccf58264
> > --- /dev/null
> > +++ b/meta/recipes-devtools/repo/files/0001-python3-shebang.patch
> > @@ -0,0 +1,21 @@
> > +From b8e84b202cd302a7c99288d3835dc9c63071f8f2 Mon Sep 17 00:00:00
> > 2001
> > +From: Jasper Orschulko
> > +Date: Tue, 14 Sep 2021 16:46:51 +0200
> > +Subject: [PATCH] python3 shebang
> > +
> > +---
> > + repo | 2 +-
> > + 1 file changed, 1 insertion(+), 1 deletion(-)
> > +
> > +diff --git a/repo b/repo
> > +index b13e34c..205e0e5 100755
> > +--- a/repo
> > b/repo
> > +@@ -1,4 +1,4 @@
> > +-#!/usr/bin/env python
> > ++#!/usr/bin/env python3
> > + # -*- coding:utf-8 -*-
> > + #
> > + # Copyright (C) 2008 The Android Open Source Project
> > +--
> > +2.33.0
> > diff --git a/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-
> > REPO_REV-to-v2.17.3.patch b/meta/recipes-devtools/repo/repo-
> > 2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
> > new file mode 100644
> > index 00..4d76bfc5d2
> > --- /dev/null
> > +++ b/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-
> > v2.17.3.patch
> > @@ -0,0 +1,33 @@
> > +From bdd2a528da59c28db8ae2986834926de7cebf3ab Mon Sep 17 00:00:00
> > 2001
> > +From: Jasper Orschulko
> > +Date: Thu, 4 Nov 2021 16:55:12 +0100
> > +Subject: [PATCH] Set REPO_REV to v2.17.3
> > +
> > +repo is an unusual tool because it downloads all of its own Python
> > modules
> > +using GPG-signed git tags, and stores those files as part of the
> > project
> > +that it is working with.
> > +
> > +So in order to have a reproducible repo installation within the
> > project
> > +folders, we hardcode the REPO_REV variable to this recipes PV.
>
> Change "this recipes PV" to "a SHA1 that corresponds to the version
> of the recipe."
>
> > +
> > +Upstream-Status: Inappropriate [configuration]
> > +Signed-off-by: Jasper Orschulko
> > +---
> > + repo | 2 +-
> > + 1 file changed, 1 insertion(+), 1 deletion(-)
> > +
> > +diff --git a/repo b/repo
> > +index 4cddbf1..cf5f6b1 100755
> > +--- a/repo
> > b/repo
> > +@@ -142,7 +142,7 @@ if __name__ == '__main__':
> > + REPO_URL = os.environ.get('REPO_URL', None)
> > + if not REPO_URL:
> > + REPO_URL = 'https://gerrit.googlesource.com/git-repo'
> > +-REPO_REV = os.environ.get('REPO_REV')
> > ++REPO_REV = '11b30b91df1f0e03b53da970ec2588e85817bacc'
> > + if not REPO_REV:
> > + REPO_REV = 'stable'
> > + # URL to file bug reports for repo tool issues.
> > +--
> > +2.33.1
> > diff --git a/meta/recipes-devtools/repo/repo.inc b/meta/recipes-
> > devtools/repo/repo.inc
> > new file mode 100644
> > index 00..60b32e4d74
> > --- /dev/null
> > +++ b/meta/recipes-devtools/repo/repo.inc
> > @@ -0,0 +1,25 @@
> > +# SPDX-License-Identifier: MIT
> > +# Copyright (C) 2021 iris-GmbH infrared & intelligent sensors
> > +
> > +SUMMARY = "Tool for managing many Git repositories"
> > +DESCRIPTION = "Repo is a tool built on top of Git. Repo helps manage
> > many Git
Re: [bitbake-devel] [oe-core][PATCH v2 1/2] devtools: Initial recipe for repo 2.17.3
> -Original Message-
> From: bitbake-de...@lists.openembedded.org
> On Behalf Of Jasper Orschulko via
> lists.openembedded.org
> Sent: den 5 november 2021 16:32
> To: openembedded-core@lists.openembedded.org
> Cc: mar...@mko.dev; daniel.baumg...@iris-sensing.com;
> bitbake-de...@lists.openembedded.org; Jasper Orschulko
>
> Subject: [bitbake-devel] [oe-core][PATCH v2 1/2] devtools: Initial recipe for
> repo 2.17.3
Change the Git subject to:
repo: Add recipe for 2.17.3
>
> From: Jasper Orschulko
>
> Add a recipe for repo, prerequisite for the repo fetcher.
>
> Signed-off-by: Jasper Orschulko
> ---
> .../repo/files/0001-python3-shebang.patch | 21
> .../0001-Set-REPO_REV-to-v2.17.3.patch| 33 +++
> meta/recipes-devtools/repo/repo.inc | 25 ++
> meta/recipes-devtools/repo/repo_2.17.3.bb | 7
> 4 files changed, 86 insertions(+)
> create mode 100644
> meta/recipes-devtools/repo/files/0001-python3-shebang.patch
> create mode 100644
> meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
> create mode 100644 meta/recipes-devtools/repo/repo.inc
> create mode 100644 meta/recipes-devtools/repo/repo_2.17.3.bb
>
> diff --git a/meta/recipes-devtools/repo/files/0001-python3-shebang.patch >
> b/meta/recipes-devtools/repo/files/0001-python3-shebang.patch
> new file mode 100644
> index 00..09ccf58264
> --- /dev/null
> +++ b/meta/recipes-devtools/repo/files/0001-python3-shebang.patch
> @@ -0,0 +1,21 @@
> +From b8e84b202cd302a7c99288d3835dc9c63071f8f2 Mon Sep 17 00:00:00 2001
> +From: Jasper Orschulko
> +Date: Tue, 14 Sep 2021 16:46:51 +0200
> +Subject: [PATCH] python3 shebang
> +
> +---
> + repo | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +diff --git a/repo b/repo
> +index b13e34c..205e0e5 100755
> +--- a/repo
> b/repo
> +@@ -1,4 +1,4 @@
> +-#!/usr/bin/env python
> ++#!/usr/bin/env python3
> + # -*- coding:utf-8 -*-
> + #
> + # Copyright (C) 2008 The Android Open Source Project
> +--
> +2.33.0
> diff --git
> a/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
> b/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
> new file mode 100644
> index 00..4d76bfc5d2
> --- /dev/null
> +++
> b/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
> @@ -0,0 +1,33 @@
> +From bdd2a528da59c28db8ae2986834926de7cebf3ab Mon Sep 17 00:00:00 2001
> +From: Jasper Orschulko
> +Date: Thu, 4 Nov 2021 16:55:12 +0100
> +Subject: [PATCH] Set REPO_REV to v2.17.3
> +
> +repo is an unusual tool because it downloads all of its own Python modules
> +using GPG-signed git tags, and stores those files as part of the project
> +that it is working with.
> +
> +So in order to have a reproducible repo installation within the project
> +folders, we hardcode the REPO_REV variable to this recipes PV.
Change "this recipes PV" to "a SHA1 that corresponds to the version
of the recipe."
> +
> +Upstream-Status: Inappropriate [configuration]
> +Signed-off-by: Jasper Orschulko
> +---
> + repo | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +diff --git a/repo b/repo
> +index 4cddbf1..cf5f6b1 100755
> +--- a/repo
> b/repo
> +@@ -142,7 +142,7 @@ if __name__ == '__main__':
> + REPO_URL = os.environ.get('REPO_URL', None)
> + if not REPO_URL:
> + REPO_URL = 'https://gerrit.googlesource.com/git-repo'
> +-REPO_REV = os.environ.get('REPO_REV')
> ++REPO_REV = '11b30b91df1f0e03b53da970ec2588e85817bacc'
> + if not REPO_REV:
> + REPO_REV = 'stable'
> + # URL to file bug reports for repo tool issues.
> +--
> +2.33.1
> diff --git a/meta/recipes-devtools/repo/repo.inc
> b/meta/recipes-devtools/repo/repo.inc
> new file mode 100644
> index 00..60b32e4d74
> --- /dev/null
> +++ b/meta/recipes-devtools/repo/repo.inc
> @@ -0,0 +1,25 @@
> +# SPDX-License-Identifier: MIT
> +# Copyright (C) 2021 iris-GmbH infrared & intelligent sensors
> +
> +SUMMARY = "Tool for managing many Git repositories"
> +DESCRIPTION = "Repo is a tool built on top of Git. Repo helps manage many
> Git repositories, does the uploads to revision control systems, and automates
> parts of the development workflow."
> +HOMEPAGE = "https://android.googlesource.com/tools/repo;
> +SECTION = "console/utils"
> +
> +LICENSE = "Apache-2.0"
> +
> +SRC_URI =
> "git://g...@gerrit.googlesource.com/git-repo.git;protocol=https;branch=main"
I do not think you need to specify "git@" for this URL.
> +MIRRORS = "git://g...@gerrit.googlesource.com/git-repo.git
> git://github.com/GerritCodeReview/git-repo.git \n"
It is probably better to use += and add to MIRRORS.
> +
> +SRC_URI += "file://0001-python3-shebang.patch"
I would rewrite the above lines as:
SRC_URI =
"git://gerrit.googlesource.com/git-repo.git;protocol=https;branch=main"
SRC_URI += "file://0001-python3-shebang.patch"
MIRRORS += "git://gerrit.googlesource.com/git-repo.git
[OE-core] [honister][PATCH 00/24] Pull request (cover letter only)
Please merge these changes. Thanks, Anuj The following changes since commit 6ca6c9c12c93c6df7b18f49ebdbfb69433ff5158: bootchart2: Don't compile python modules (2021-10-26 21:42:27 +0800) are available in the Git repository at: git://push.openembedded.org/openembedded-core-contrib stable/honister-next Ahmed Hossam (1): go.bbclass: Allow adding parameters to go ldflags Alexander Kanavin (4): waffle: convert to git, website is down stress-ng: convert to git, website is down tzdata: upgrade 2021a -> 2021d tzdata: update 2021d -> 2021e Bruce Ashfield (7): linux-yocto/5.10: update to v5.10.73 linux-yocto/5.14: update to v5.14.12 linux-yocto/5.14: update to v5.14.13 linux-yocto/5.10: update to v5.10.74 linux-yocto/5.14: common-pc: enable CONFIG_ATA_PIIX as built-in linux-yocto/5.14: update to v5.14.14 linux-yocto/5.10: update to v5.10.75 Hsia-Jun(Randy) Li (1): meson: install native file in sdk Joshua Watt (1): classes/populate_sdk_base: Add setscene tasks Peter Kjellerstedt (2): meson.bblcass: Remove empty egg-info directories before running meson qemu.inc: Remove empty egg-info directories before running meson Randy Li (1): meson: move lang args to the right section Richard Purdie (1): staging: Fix autoconf-native rebuild failure Ross Burton (1): strace: show test suite log on failure Saul Wold (3): spdx.py: Add annotation to relationship create-spdx: add create_annotation function create-spdx: cross recipes are native also Teoh Jay Shen (1): oeqa/runtime/parselogs: modified drm error in common errors list Tim Orling (1): python3-setuptools: _distutils/sysconfig fix meta/classes/create-spdx.bbclass | 22 +--- meta/classes/go.bbclass | 3 +- meta/classes/meson.bbclass| 10 meta/classes/populate_sdk_base.bbclass| 4 ++ meta/classes/staging.bbclass | 2 +- meta/lib/oe/spdx.py | 6 ++- meta/lib/oeqa/runtime/cases/parselogs.py | 2 +- .../meson/meson/meson-setup.py| 8 +++ .../meson/meson/meson-wrapper | 1 + .../meson/nativesdk-meson_0.58.1.bb | 52 ++- ...nfig-append-STAGING_LIBDIR-python-sy.patch | 34 .../python/python3-setuptools_57.4.0.bb | 5 +- meta/recipes-devtools/qemu/qemu.inc | 8 ++- meta/recipes-devtools/strace/strace/run-ptest | 9 ...write-the-timestamp-into-compressed-.patch | 26 ++ .../stress-ng/stress-ng_0.13.00.bb| 8 +-- meta/recipes-extended/timezone/timezone.inc | 7 +-- meta/recipes-graphics/waffle/waffle_1.6.1.bb | 10 ++-- .../linux/linux-yocto-rt_5.10.bb | 6 +-- .../linux/linux-yocto-rt_5.14.bb | 6 +-- .../linux/linux-yocto-tiny_5.10.bb| 8 +-- .../linux/linux-yocto-tiny_5.14.bb| 8 +-- meta/recipes-kernel/linux/linux-yocto_5.10.bb | 24 - meta/recipes-kernel/linux/linux-yocto_5.14.bb | 26 +- 24 files changed, 227 insertions(+), 68 deletions(-) create mode 100644 meta/recipes-devtools/python/python3-setuptools/0001-_distutils-sysconfig-append-STAGING_LIBDIR-python-sy.patch create mode 100644 meta/recipes-extended/stress-ng/stress-ng/0001-Makefile-do-not-write-the-timestamp-into-compressed-.patch -- 2.31.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#157908): https://lists.openembedded.org/g/openembedded-core/message/157908 Mute This Topic: https://lists.openembedded.org/mt/86844132/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [bitbake-devel] [oe-core][PATCH 1/2] devtools: Initial recipe for repo 2.17.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 SHA rev set in v2 of the patch series :) - -- With best regards Jasper Orschulko DevOps Engineer Tel. +49 30 58 58 14 265 Fax +49 30 58 58 14 999 jasper.orschu...@iris-sensing.com • • • • • • • • • • • • • • • • • • • • • • • • • • iris-GmbH infrared & intelligent sensors Schnellerstraße 1-5 | 12439 Berlin https://iris-sensing.com/ On Fri, 2021-11-05 at 15:20 +0100, Konrad Weihmann wrote: > > > On 05.11.21 15:09, Jasper Orschulko wrote: > > Actually, I don't believe this to be an issue for the following > > reasons: > > > > 1. The recipe does nothing more than taking the wrapper script as > > is > > and copying it to the sysroot. As the repo binary is never called > > when > > building, it does not have the "chance" to look for an update > > during > > the yocto offline build process. The outcome of an offline build is > > therefore predictable. > > > > 2. When using repo within the yocto build itself (with the repo > > fetcher), the repo binary is only ever called during the do_fetch > > step, > > which obviously has no issues with any network access. > > > > > > Okay fine that makes sense, even if it is still phoning home. > Another thing, could you please exchange "+REPO_REV = 'v2.17.3'" for > a > SHA revision, as I wouldn't bet my life on google not > deleting/removing > tags from their repos - and unpleasantly we wouldn't even notice that > easily -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE4WyPMIC5Ap4+Ooo1Ygqew07VMNUFAmGFTxsACgkQYgqew07V MNW2ugf/RS4zCitkPe9ZEDJvApdZGie1dJmc3gGvcweNv6d6kd1bFd2bS4BYdbiK BOhHF3kMtdznaJNyQlAHBSmysfvTUWymqUahRT3f7+kEuHqrwQcYJFoDqM3tXR4s 4VKYpbRo8klw62XjuBHdwJ8LxJiz5EWQdQF8gdQTl3Tiojp6y2KGDrjo3j/MYjAk 6KfwP0bAca6o/vMF7Jjhbs9sIlCqOkUXrNRbktEonO7hPZxdpgiEC6QPHCq9ONiN 3hHPhV13gd+BTa/7k1GNPSLW4XV6ye7qc26CpqMDing8dxz4RJnzpk2IxTNFHQ0m 95mLdHAygo7o9RJYdz8NIO4hXVqb7Q== =nQVK -END PGP SIGNATURE- -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#157907): https://lists.openembedded.org/g/openembedded-core/message/157907 Mute This Topic: https://lists.openembedded.org/mt/86840389/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[oe-core][PATCH v2 2/2] base.bbclass: Add sysroot deps for repo fetcher
From: Jasper Orschulko
Add git-native and repo-native as prerequisite for the repo fetcher.
Signed-off-by: Jasper Orschulko
---
meta/classes/base.bbclass | 5 +
1 file changed, 5 insertions(+)
diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
index a65fcc6c1d..3298bd1952 100644
--- a/meta/classes/base.bbclass
+++ b/meta/classes/base.bbclass
@@ -665,6 +665,11 @@ python () {
elif uri.scheme == "npm":
d.appendVarFlag('do_fetch', 'depends', '
nodejs-native:do_populate_sysroot')
+elif uri.scheme == "repo":
+needsrcrev = True
+d.appendVarFlag('do_fetch', 'depends', '
repo-native:do_populate_sysroot')
+d.appendVarFlag('do_fetch', 'depends', '
git-native:do_populate_sysroot')
+
# *.lz4 should DEPEND on lz4-native for unpacking
if path.endswith('.lz4'):
d.appendVarFlag('do_unpack', 'depends', '
lz4-native:do_populate_sysroot')
--
2.33.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157906):
https://lists.openembedded.org/g/openembedded-core/message/157906
Mute This Topic: https://lists.openembedded.org/mt/86843544/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[oe-core][PATCH v2 1/2] devtools: Initial recipe for repo 2.17.3
From: Jasper Orschulko
Add a recipe for repo, prerequisite for the repo fetcher.
Signed-off-by: Jasper Orschulko
---
.../repo/files/0001-python3-shebang.patch | 21
.../0001-Set-REPO_REV-to-v2.17.3.patch| 33 +++
meta/recipes-devtools/repo/repo.inc | 25 ++
meta/recipes-devtools/repo/repo_2.17.3.bb | 7
4 files changed, 86 insertions(+)
create mode 100644 meta/recipes-devtools/repo/files/0001-python3-shebang.patch
create mode 100644
meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
create mode 100644 meta/recipes-devtools/repo/repo.inc
create mode 100644 meta/recipes-devtools/repo/repo_2.17.3.bb
diff --git a/meta/recipes-devtools/repo/files/0001-python3-shebang.patch
b/meta/recipes-devtools/repo/files/0001-python3-shebang.patch
new file mode 100644
index 00..09ccf58264
--- /dev/null
+++ b/meta/recipes-devtools/repo/files/0001-python3-shebang.patch
@@ -0,0 +1,21 @@
+From b8e84b202cd302a7c99288d3835dc9c63071f8f2 Mon Sep 17 00:00:00 2001
+From: Jasper Orschulko
+Date: Tue, 14 Sep 2021 16:46:51 +0200
+Subject: [PATCH] python3 shebang
+
+---
+ repo | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/repo b/repo
+index b13e34c..205e0e5 100755
+--- a/repo
b/repo
+@@ -1,4 +1,4 @@
+-#!/usr/bin/env python
++#!/usr/bin/env python3
+ # -*- coding:utf-8 -*-
+ #
+ # Copyright (C) 2008 The Android Open Source Project
+--
+2.33.0
diff --git
a/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
b/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
new file mode 100644
index 00..4d76bfc5d2
--- /dev/null
+++ b/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
@@ -0,0 +1,33 @@
+From bdd2a528da59c28db8ae2986834926de7cebf3ab Mon Sep 17 00:00:00 2001
+From: Jasper Orschulko
+Date: Thu, 4 Nov 2021 16:55:12 +0100
+Subject: [PATCH] Set REPO_REV to v2.17.3
+
+repo is an unusual tool because it downloads all of its own Python modules
+using GPG-signed git tags, and stores those files as part of the project
+that it is working with.
+
+So in order to have a reproducible repo installation within the project
+folders, we hardcode the REPO_REV variable to this recipes PV.
+
+Upstream-Status: Inappropriate [configuration]
+Signed-off-by: Jasper Orschulko
+---
+ repo | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/repo b/repo
+index 4cddbf1..cf5f6b1 100755
+--- a/repo
b/repo
+@@ -142,7 +142,7 @@ if __name__ == '__main__':
+ REPO_URL = os.environ.get('REPO_URL', None)
+ if not REPO_URL:
+ REPO_URL = 'https://gerrit.googlesource.com/git-repo'
+-REPO_REV = os.environ.get('REPO_REV')
++REPO_REV = '11b30b91df1f0e03b53da970ec2588e85817bacc'
+ if not REPO_REV:
+ REPO_REV = 'stable'
+ # URL to file bug reports for repo tool issues.
+--
+2.33.1
diff --git a/meta/recipes-devtools/repo/repo.inc
b/meta/recipes-devtools/repo/repo.inc
new file mode 100644
index 00..60b32e4d74
--- /dev/null
+++ b/meta/recipes-devtools/repo/repo.inc
@@ -0,0 +1,25 @@
+# SPDX-License-Identifier: MIT
+# Copyright (C) 2021 iris-GmbH infrared & intelligent sensors
+
+SUMMARY = "Tool for managing many Git repositories"
+DESCRIPTION = "Repo is a tool built on top of Git. Repo helps manage many Git
repositories, does the uploads to revision control systems, and automates parts
of the development workflow."
+HOMEPAGE = "https://android.googlesource.com/tools/repo;
+SECTION = "console/utils"
+
+LICENSE = "Apache-2.0"
+
+SRC_URI =
"git://g...@gerrit.googlesource.com/git-repo.git;protocol=https;branch=main"
+MIRRORS = "git://g...@gerrit.googlesource.com/git-repo.git
git://github.com/GerritCodeReview/git-repo.git \n"
+
+SRC_URI += "file://0001-python3-shebang.patch"
+
+S = "${WORKDIR}/git"
+
+RDEPENDS_${PN} = "python3"
+
+do_install() {
+install -d ${D}${bindir}
+install -m 755 ${WORKDIR}/git/repo ${D}${bindir}
+}
+
+BBCLASSEXTEND = "native nativesdk"
diff --git a/meta/recipes-devtools/repo/repo_2.17.3.bb
b/meta/recipes-devtools/repo/repo_2.17.3.bb
new file mode 100644
index 00..c26264b9e9
--- /dev/null
+++ b/meta/recipes-devtools/repo/repo_2.17.3.bb
@@ -0,0 +1,7 @@
+# SPDX-License-Identifier: MIT
+# Copyright (C) 2021 iris-GmbH infrared & intelligent sensors
+
+require recipes-devtools/repo/repo.inc
+
+SRCREV = "11b30b91df1f0e03b53da970ec2588e85817bacc"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=3b83ef96387f14655fc854ddc3c6bd57"
--
2.33.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157905):
https://lists.openembedded.org/g/openembedded-core/message/157905
Mute This Topic: https://lists.openembedded.org/mt/86843542/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [bitbake-devel] [oe-core][PATCH 1/2] devtools: Initial recipe for repo 2.17.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Yeah. Unfortunately the current repo fetcher is pretty much broken, this patch is more or less a requirement for changes to the repo fetcher we proposed in the bitbake mailinglist. In our case some binary which is made up from some 50ish separately versioned sub-components. We used to have separate recipes for each of this components and static link them using DEPENDS. However, this does not scale well. E.g. if you want to create another version with different cmake flags, you would have to create copies of all 50ish recipes. You could move all the components into a single recipe and do 50x git fetcher, but keeping this versioned is still painful. Especially since the developers mainly don't use yocto but use the SDK for cross-compiling. As such this used to mean, that versioning in the development workflow and the release workflow worked differently -> more maintenance work. With repo fetcher we can streamline the versioning within the yocto build process and the daily developer workflow, as both can fetch the repo manifest from a central stored git repo. The idea is, that the repo manifest defaults to develop branch for all component repos and if we want to create a release we can use repos own tooling to automatically create fixed refspecs from the development manifest. something like `repo manifest -r -o release-1.0.0.xml`, push that as a release to the manifest repo, set this release as refspec in the recipe within the meta layer and proceed with the release process. So no more manually maintaining the component versioning within the yocto recipes. - -- With best regards Jasper Orschulko DevOps Engineer Tel. +49 30 58 58 14 265 Fax +49 30 58 58 14 999 jasper.orschu...@iris-sensing.com • • • • • • • • • • • • • • • • • • • • • • • • • • iris-GmbH infrared & intelligent sensors Schnellerstraße 1-5 | 12439 Berlin https://iris-sensing.com/ On Fri, 2021-11-05 at 15:20 +0100, Alexander Kanavin wrote: > Wait, what is the use case for the repo fetcher? > > Alex > > On Fri, 5 Nov 2021 at 14:31, Jasper Orschulko via > lists.openembedded.org > wrote: > > From: Jasper Orschulko > > > > Add a recipe for repo, prerequisite for the repo fetcher. > > > > Signed-off-by: Jasper Orschulko > > --- > > .../repo/files/0001-python3-shebang.patch | 21 > > .../0001-Set-REPO_REV-to-v2.17.3.patch | 33 > > +++ > > meta/recipes-devtools/repo/repo.inc | 25 ++ > > meta/recipes-devtools/repo/repo_2.17.3.bb | 7 > > 4 files changed, 86 insertions(+) > > create mode 100644 meta/recipes-devtools/repo/files/0001-python3- > > shebang.patch > > create mode 100644 meta/recipes-devtools/repo/repo-2.17.3/0001- > > Set- > > REPO_REV-to-v2.17.3.patch > > create mode 100644 meta/recipes-devtools/repo/repo.inc > > create mode 100644 meta/recipes-devtools/repo/repo_2.17.3.bb > > > > diff --git a/meta/recipes-devtools/repo/files/0001-python3- > > shebang.patch b/meta/recipes-devtools/repo/files/0001-python3- > > shebang.patch > > new file mode 100644 > > index 00..09ccf58264 > > --- /dev/null > > +++ b/meta/recipes-devtools/repo/files/0001-python3-shebang.patch > > @@ -0,0 +1,21 @@ > > +From b8e84b202cd302a7c99288d3835dc9c63071f8f2 Mon Sep 17 00:00:00 > > 2001 > > +From: Jasper Orschulko > > +Date: Tue, 14 Sep 2021 16:46:51 +0200 > > +Subject: [PATCH] python3 shebang > > + > > +--- > > + repo | 2 +- > > + 1 file changed, 1 insertion(+), 1 deletion(-) > > + > > +diff --git a/repo b/repo > > +index b13e34c..205e0e5 100755 > > +--- a/repo > > b/repo > > +@@ -1,4 +1,4 @@ > > +-#!/usr/bin/env python > > ++#!/usr/bin/env python3 > > + # -*- coding:utf-8 -*- > > + # > > + # Copyright (C) 2008 The Android Open Source Project > > +-- > > +2.33.0 > > diff --git a/meta/recipes-devtools/repo/repo-2.17.3/0001-Set- > > REPO_REV-to-v2.17.3.patch b/meta/recipes-devtools/repo/repo- > > 2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch > > new file mode 100644 > > index 00..294a3af53a > > --- /dev/null > > +++ b/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to- > > v2.17.3.patch > > @@ -0,0 +1,33 @@ > > +From bdd2a528da59c28db8ae2986834926de7cebf3ab Mon Sep 17 00:00:00 > > 2001 > > +From: Jasper Orschulko > > +Date: Thu, 4 Nov 2021 16:55:12 +0100 > > +Subject: [PATCH] Set REPO_REV to v2.17.3 > > + > > +repo is an unusual tool because it downloads all of its own Python > > modules > > +using GPG-signed git tags, and stores those files as part of the > > project > > +that it is working with. > > + > > +So in order to have a reproducible repo installation within the > > project > > +folders, we hardcode the REPO_REV variable to this recipes PV. > > + > > +Upstream-Status: Inappropriate [configuration] > > +Signed-off-by: Jasper Orschulko > > > > +--- > > + repo | 2 +- > > + 1 file changed, 1 insertion(+), 1 deletion(-) > > + > > +diff --git a/repo b/repo > > +index 4cddbf1..cf5f6b1 100755 >
Re: [bitbake-devel] [oe-core][PATCH 1/2] devtools: Initial recipe for repo 2.17.3
Ah I didn't notice it's something that already exists. Still, I'm curious
for which items is it used, and why repo over other options?
Alex
On Fri, 5 Nov 2021 at 15:20, Alexander Kanavin
wrote:
> Wait, what is the use case for the repo fetcher?
>
> Alex
>
> On Fri, 5 Nov 2021 at 14:31, Jasper Orschulko via lists.openembedded.org
> wrote:
>
>> From: Jasper Orschulko
>>
>> Add a recipe for repo, prerequisite for the repo fetcher.
>>
>> Signed-off-by: Jasper Orschulko
>> ---
>> .../repo/files/0001-python3-shebang.patch | 21
>> .../0001-Set-REPO_REV-to-v2.17.3.patch| 33 +++
>> meta/recipes-devtools/repo/repo.inc | 25 ++
>> meta/recipes-devtools/repo/repo_2.17.3.bb | 7
>> 4 files changed, 86 insertions(+)
>> create mode 100644
>> meta/recipes-devtools/repo/files/0001-python3-shebang.patch
>> create mode 100644
>> meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
>> create mode 100644 meta/recipes-devtools/repo/repo.inc
>> create mode 100644 meta/recipes-devtools/repo/repo_2.17.3.bb
>>
>> diff --git a/meta/recipes-devtools/repo/files/0001-python3-shebang.patch
>> b/meta/recipes-devtools/repo/files/0001-python3-shebang.patch
>> new file mode 100644
>> index 00..09ccf58264
>> --- /dev/null
>> +++ b/meta/recipes-devtools/repo/files/0001-python3-shebang.patch
>> @@ -0,0 +1,21 @@
>> +From b8e84b202cd302a7c99288d3835dc9c63071f8f2 Mon Sep 17 00:00:00 2001
>> +From: Jasper Orschulko
>> +Date: Tue, 14 Sep 2021 16:46:51 +0200
>> +Subject: [PATCH] python3 shebang
>> +
>> +---
>> + repo | 2 +-
>> + 1 file changed, 1 insertion(+), 1 deletion(-)
>> +
>> +diff --git a/repo b/repo
>> +index b13e34c..205e0e5 100755
>> +--- a/repo
>> b/repo
>> +@@ -1,4 +1,4 @@
>> +-#!/usr/bin/env python
>> ++#!/usr/bin/env python3
>> + # -*- coding:utf-8 -*-
>> + #
>> + # Copyright (C) 2008 The Android Open Source Project
>> +--
>> +2.33.0
>> diff --git
>> a/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
>> b/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
>> new file mode 100644
>> index 00..294a3af53a
>> --- /dev/null
>> +++
>> b/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
>> @@ -0,0 +1,33 @@
>> +From bdd2a528da59c28db8ae2986834926de7cebf3ab Mon Sep 17 00:00:00 2001
>> +From: Jasper Orschulko
>> +Date: Thu, 4 Nov 2021 16:55:12 +0100
>> +Subject: [PATCH] Set REPO_REV to v2.17.3
>> +
>> +repo is an unusual tool because it downloads all of its own Python
>> modules
>> +using GPG-signed git tags, and stores those files as part of the project
>> +that it is working with.
>> +
>> +So in order to have a reproducible repo installation within the project
>> +folders, we hardcode the REPO_REV variable to this recipes PV.
>> +
>> +Upstream-Status: Inappropriate [configuration]
>> +Signed-off-by: Jasper Orschulko
>> +---
>> + repo | 2 +-
>> + 1 file changed, 1 insertion(+), 1 deletion(-)
>> +
>> +diff --git a/repo b/repo
>> +index 4cddbf1..cf5f6b1 100755
>> +--- a/repo
>> b/repo
>> +@@ -142,7 +142,7 @@ if __name__ == '__main__':
>> + REPO_URL = os.environ.get('REPO_URL', None)
>> + if not REPO_URL:
>> + REPO_URL = 'https://gerrit.googlesource.com/git-repo'
>> +-REPO_REV = os.environ.get('REPO_REV')
>> ++REPO_REV = 'v2.17.3'
>> + if not REPO_REV:
>> + REPO_REV = 'stable'
>> + # URL to file bug reports for repo tool issues.
>> +--
>> +2.33.1
>> diff --git a/meta/recipes-devtools/repo/repo.inc
>> b/meta/recipes-devtools/repo/repo.inc
>> new file mode 100644
>> index 00..60b32e4d74
>> --- /dev/null
>> +++ b/meta/recipes-devtools/repo/repo.inc
>> @@ -0,0 +1,25 @@
>> +# SPDX-License-Identifier: MIT
>> +# Copyright (C) 2021 iris-GmbH infrared & intelligent sensors
>> +
>> +SUMMARY = "Tool for managing many Git repositories"
>> +DESCRIPTION = "Repo is a tool built on top of Git. Repo helps manage
>> many Git repositories, does the uploads to revision control systems, and
>> automates parts of the development workflow."
>> +HOMEPAGE = "https://android.googlesource.com/tools/repo;
>> +SECTION = "console/utils"
>> +
>> +LICENSE = "Apache-2.0"
>> +
>> +SRC_URI = "git://
>> g...@gerrit.googlesource.com/git-repo.git;protocol=https;branch=main"
>> +MIRRORS = "git://g...@gerrit.googlesource.com/git-repo.git git://
>> github.com/GerritCodeReview/git-repo.git \n"
>> +
>> +SRC_URI += "file://0001-python3-shebang.patch"
>> +
>> +S = "${WORKDIR}/git"
>> +
>> +RDEPENDS_${PN} = "python3"
>> +
>> +do_install() {
>> +install -d ${D}${bindir}
>> +install -m 755 ${WORKDIR}/git/repo ${D}${bindir}
>> +}
>> +
>> +BBCLASSEXTEND = "native nativesdk"
>> diff --git a/meta/recipes-devtools/repo/repo_2.17.3.bb
>> b/meta/recipes-devtools/repo/repo_2.17.3.bb
>> new file mode 100644
>> index 00..c26264b9e9
>> --- /dev/null
>> +++ b/meta/recipes-devtools/repo/repo_2.17.3.bb
>> @@ -0,0 +1,7 @@
>> +# SPDX-License-Identifier: MIT
>> +# Copyright (C)
Re: [bitbake-devel] [oe-core][PATCH 1/2] devtools: Initial recipe for repo 2.17.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 > Okay fine that makes sense, even if it is still phoning home. True. Bad software design at best. But luckily not an issue from a build system perspective. :) > Another thing, could you please exchange "+REPO_REV = 'v2.17.3'" for > a > SHA revision, as I wouldn't bet my life on google not > deleting/removing > tags from their repos - and unpleasantly we wouldn't even notice that > easily Fair point, will do! - -- With best regards Jasper Orschulko DevOps Engineer Tel. +49 30 58 58 14 265 Fax +49 30 58 58 14 999 jasper.orschu...@iris-sensing.com • • • • • • • • • • • • • • • • • • • • • • • • • • iris-GmbH infrared & intelligent sensors Schnellerstraße 1-5 | 12439 Berlin https://iris-sensing.com/ On Fri, 2021-11-05 at 15:20 +0100, Konrad Weihmann wrote: > > > On 05.11.21 15:09, Jasper Orschulko wrote: > > Actually, I don't believe this to be an issue for the following > > reasons: > > > > 1. The recipe does nothing more than taking the wrapper script as is > > and copying it to the sysroot. As the repo binary is never called > > when > > building, it does not have the "chance" to look for an update during > > the yocto offline build process. The outcome of an offline build is > > therefore predictable. > > > > 2. When using repo within the yocto build itself (with the repo > > fetcher), the repo binary is only ever called during the do_fetch > > step, > > which obviously has no issues with any network access. > > > > > > Okay fine that makes sense, even if it is still phoning home. > Another thing, could you please exchange "+REPO_REV = 'v2.17.3'" for a > SHA revision, as I wouldn't bet my life on google not deleting/removing > tags from their repos - and unpleasantly we wouldn't even notice that > easily -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE4WyPMIC5Ap4+Ooo1Ygqew07VMNUFAmGFRU4ACgkQYgqew07V MNX3ywf+MQAwmH9TVF0izfVVIYhwiTASgZLlG0pwMBXfQw6iIeWAXmO8LccJNrwb fceVMFFXPi1/2SjAdjhOzzh5X7uSGbcVT0G13RpeuYfsnu7HyJ3n6TAdzoXiQtNa PqJqPVsZBEIpHilTYEZqPu/ENHNq74Sj/sQXqM0XjNMTaJKKW7Syc9jbGdEdn+MV gU9iNIQmYWEPSUS2Tp+lgFh9xC3qQOQJZPpcJ5V3hWfAIibaRMed4kGdd3mlJsYj /Aoq+7gXe1iZOXB7OxXX+bk7ueoHCnp7QUPyWFVxslKx/r/faH+f+PwHmJHZp0VD gOrzbjaIK2E2CVnRobaOkSknIffJzQ== =Tfz+ -END PGP SIGNATURE- -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#157902): https://lists.openembedded.org/g/openembedded-core/message/157902 Mute This Topic: https://lists.openembedded.org/mt/86840389/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH] python3-magic: add missing DEPENDS
Since file-native is ASSUME_PROVIDED magic.mgc is not being staged. As
a result diffoscope-native is failing with:
magic.MagicException: b'could not find any valid magic files!
Fix this by adding dependency on file-replacement-native
Signed-off-by: Steve Sakoman
---
meta/recipes-devtools/python/python3-magic_0.4.24.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-devtools/python/python3-magic_0.4.24.bb
b/meta/recipes-devtools/python/python3-magic_0.4.24.bb
index ae895fbd53..fd5825dbd1 100644
--- a/meta/recipes-devtools/python/python3-magic_0.4.24.bb
+++ b/meta/recipes-devtools/python/python3-magic_0.4.24.bb
@@ -13,6 +13,8 @@ inherit pypi setuptools3
SRC_URI[sha256sum] =
"de800df9fb50f8ec5974761054a708af6e4246b03b4bdaee993f948947b0ebcf"
+DEPENDS:append:class-native = " file-replacement-native"
+
RDEPENDS:${PN} += "file \
${PYTHON_PN}-ctypes \
${PYTHON_PN}-io \
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157901):
https://lists.openembedded.org/g/openembedded-core/message/157901
Mute This Topic: https://lists.openembedded.org/mt/86841899/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [bitbake-devel] [oe-core][PATCH 1/2] devtools: Initial recipe for repo 2.17.3
On 05.11.21 15:09, Jasper Orschulko wrote: Actually, I don't believe this to be an issue for the following reasons: 1. The recipe does nothing more than taking the wrapper script as is and copying it to the sysroot. As the repo binary is never called when building, it does not have the "chance" to look for an update during the yocto offline build process. The outcome of an offline build is therefore predictable. 2. When using repo within the yocto build itself (with the repo fetcher), the repo binary is only ever called during the do_fetch step, which obviously has no issues with any network access. > Okay fine that makes sense, even if it is still phoning home. Another thing, could you please exchange "+REPO_REV = 'v2.17.3'" for a SHA revision, as I wouldn't bet my life on google not deleting/removing tags from their repos - and unpleasantly we wouldn't even notice that easily -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#157900): https://lists.openembedded.org/g/openembedded-core/message/157900 Mute This Topic: https://lists.openembedded.org/mt/86840389/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [bitbake-devel] [oe-core][PATCH 1/2] devtools: Initial recipe for repo 2.17.3
Wait, what is the use case for the repo fetcher?
Alex
On Fri, 5 Nov 2021 at 14:31, Jasper Orschulko via lists.openembedded.org
wrote:
> From: Jasper Orschulko
>
> Add a recipe for repo, prerequisite for the repo fetcher.
>
> Signed-off-by: Jasper Orschulko
> ---
> .../repo/files/0001-python3-shebang.patch | 21
> .../0001-Set-REPO_REV-to-v2.17.3.patch| 33 +++
> meta/recipes-devtools/repo/repo.inc | 25 ++
> meta/recipes-devtools/repo/repo_2.17.3.bb | 7
> 4 files changed, 86 insertions(+)
> create mode 100644
> meta/recipes-devtools/repo/files/0001-python3-shebang.patch
> create mode 100644
> meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
> create mode 100644 meta/recipes-devtools/repo/repo.inc
> create mode 100644 meta/recipes-devtools/repo/repo_2.17.3.bb
>
> diff --git a/meta/recipes-devtools/repo/files/0001-python3-shebang.patch
> b/meta/recipes-devtools/repo/files/0001-python3-shebang.patch
> new file mode 100644
> index 00..09ccf58264
> --- /dev/null
> +++ b/meta/recipes-devtools/repo/files/0001-python3-shebang.patch
> @@ -0,0 +1,21 @@
> +From b8e84b202cd302a7c99288d3835dc9c63071f8f2 Mon Sep 17 00:00:00 2001
> +From: Jasper Orschulko
> +Date: Tue, 14 Sep 2021 16:46:51 +0200
> +Subject: [PATCH] python3 shebang
> +
> +---
> + repo | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +diff --git a/repo b/repo
> +index b13e34c..205e0e5 100755
> +--- a/repo
> b/repo
> +@@ -1,4 +1,4 @@
> +-#!/usr/bin/env python
> ++#!/usr/bin/env python3
> + # -*- coding:utf-8 -*-
> + #
> + # Copyright (C) 2008 The Android Open Source Project
> +--
> +2.33.0
> diff --git
> a/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
> b/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
> new file mode 100644
> index 00..294a3af53a
> --- /dev/null
> +++
> b/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
> @@ -0,0 +1,33 @@
> +From bdd2a528da59c28db8ae2986834926de7cebf3ab Mon Sep 17 00:00:00 2001
> +From: Jasper Orschulko
> +Date: Thu, 4 Nov 2021 16:55:12 +0100
> +Subject: [PATCH] Set REPO_REV to v2.17.3
> +
> +repo is an unusual tool because it downloads all of its own Python modules
> +using GPG-signed git tags, and stores those files as part of the project
> +that it is working with.
> +
> +So in order to have a reproducible repo installation within the project
> +folders, we hardcode the REPO_REV variable to this recipes PV.
> +
> +Upstream-Status: Inappropriate [configuration]
> +Signed-off-by: Jasper Orschulko
> +---
> + repo | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +diff --git a/repo b/repo
> +index 4cddbf1..cf5f6b1 100755
> +--- a/repo
> b/repo
> +@@ -142,7 +142,7 @@ if __name__ == '__main__':
> + REPO_URL = os.environ.get('REPO_URL', None)
> + if not REPO_URL:
> + REPO_URL = 'https://gerrit.googlesource.com/git-repo'
> +-REPO_REV = os.environ.get('REPO_REV')
> ++REPO_REV = 'v2.17.3'
> + if not REPO_REV:
> + REPO_REV = 'stable'
> + # URL to file bug reports for repo tool issues.
> +--
> +2.33.1
> diff --git a/meta/recipes-devtools/repo/repo.inc
> b/meta/recipes-devtools/repo/repo.inc
> new file mode 100644
> index 00..60b32e4d74
> --- /dev/null
> +++ b/meta/recipes-devtools/repo/repo.inc
> @@ -0,0 +1,25 @@
> +# SPDX-License-Identifier: MIT
> +# Copyright (C) 2021 iris-GmbH infrared & intelligent sensors
> +
> +SUMMARY = "Tool for managing many Git repositories"
> +DESCRIPTION = "Repo is a tool built on top of Git. Repo helps manage many
> Git repositories, does the uploads to revision control systems, and
> automates parts of the development workflow."
> +HOMEPAGE = "https://android.googlesource.com/tools/repo;
> +SECTION = "console/utils"
> +
> +LICENSE = "Apache-2.0"
> +
> +SRC_URI = "git://
> g...@gerrit.googlesource.com/git-repo.git;protocol=https;branch=main"
> +MIRRORS = "git://g...@gerrit.googlesource.com/git-repo.git git://
> github.com/GerritCodeReview/git-repo.git \n"
> +
> +SRC_URI += "file://0001-python3-shebang.patch"
> +
> +S = "${WORKDIR}/git"
> +
> +RDEPENDS_${PN} = "python3"
> +
> +do_install() {
> +install -d ${D}${bindir}
> +install -m 755 ${WORKDIR}/git/repo ${D}${bindir}
> +}
> +
> +BBCLASSEXTEND = "native nativesdk"
> diff --git a/meta/recipes-devtools/repo/repo_2.17.3.bb
> b/meta/recipes-devtools/repo/repo_2.17.3.bb
> new file mode 100644
> index 00..c26264b9e9
> --- /dev/null
> +++ b/meta/recipes-devtools/repo/repo_2.17.3.bb
> @@ -0,0 +1,7 @@
> +# SPDX-License-Identifier: MIT
> +# Copyright (C) 2021 iris-GmbH infrared & intelligent sensors
> +
> +require recipes-devtools/repo/repo.inc
> +
> +SRCREV = "11b30b91df1f0e03b53da970ec2588e85817bacc"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=3b83ef96387f14655fc854ddc3c6bd57"
> --
> 2.33.1
>
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply
Re: [bitbake-devel] [oe-core][PATCH 1/2] devtools: Initial recipe for repo 2.17.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Actually, I don't believe this to be an issue for the following reasons: 1. The recipe does nothing more than taking the wrapper script as is and copying it to the sysroot. As the repo binary is never called when building, it does not have the "chance" to look for an update during the yocto offline build process. The outcome of an offline build is therefore predictable. 2. When using repo within the yocto build itself (with the repo fetcher), the repo binary is only ever called during the do_fetch step, which obviously has no issues with any network access. - -- With best regards Jasper Orschulko DevOps Engineer Tel. +49 30 58 58 14 265 Fax +49 30 58 58 14 999 jasper.orschu...@iris-sensing.com • • • • • • • • • • • • • • • • • • • • • • • • • • iris-GmbH infrared & intelligent sensors Schnellerstraße 1-5 | 12439 Berlin https://iris-sensing.com/ On Fri, 2021-11-05 at 14:47 +0100, Jasper Orschulko wrote: > Hi Konrad, > > that might be a good point. I patched the REPO_REV to a fixed refspec > within the wrapper tool, as to stop repo from using the latest stable > release. But you are right, and this might not be enough. Will do > some > more digging on this. > -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE4WyPMIC5Ap4+Ooo1Ygqew07VMNUFAmGFOvsACgkQYgqew07V MNVfxQf/VZLnjKv7To1VaqM6dMIX/R3P9cWQtuTxOg6G05Ziooizao5VgQDUXEIy Zs3h5lCFMuXdJlEZc9q2AJQC55BIGqtW8Njo6lNQDPI0Iz51HpXhNgsWdoC3E7qB tphfw+H0WNnIhtDMkK/+hUAZWAsHHUb7I3rAyruE34GKqvEmbBwHo45B0NpgeCqF rNPH7FeI9VvehloZB/5+jnJbrnmyWWogXCNx3PXPlgyrnxyRDuibOUivW6R/MRGd RkSdYvllMgS9ajBLyK/PEyeA6rupEVQquKv0n9ghxZDOzVm6mboCvBMcjxsaSCpR UlFP+h+4sYw0DTfAN9J4UIGWq4VmJA== =P/xG -END PGP SIGNATURE- -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#157898): https://lists.openembedded.org/g/openembedded-core/message/157898 Mute This Topic: https://lists.openembedded.org/mt/86840389/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [bitbake-devel] [oe-core][PATCH 1/2] devtools: Initial recipe for repo 2.17.3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Konrad,
that might be a good point. I patched the REPO_REV to a fixed refspec
within the wrapper tool, as to stop repo from using the latest stable
release. But you are right, and this might not be enough. Will do some
more digging on this.
- --
With best regards
Jasper Orschulko
DevOps Engineer
Tel. +49 30 58 58 14 265
Fax +49 30 58 58 14 999
jasper.orschu...@iris-sensing.com
• • • • • • • • • • • • • • • • • • • • • • • • • •
iris-GmbH
infrared & intelligent sensors
Schnellerstraße 1-5 | 12439 Berlin
https://iris-sensing.com/
On Fri, 2021-11-05 at 14:35 +0100, Konrad Weihmann wrote:
> Is this implementation of repo being patched against phoning home to
> google everytime and trying to do that pesky auto-update of the tool?
>
> Otherwise this will become an issue when at one point in time an
> (then)
> outdated version of the tool is used in a BB_NO_NETWORK build.
>
> On 05.11.21 14:31, Jasper Orschulko via lists.openembedded.org wrote:
> > From: Jasper Orschulko
> >
> > Add a recipe for repo, prerequisite for the repo fetcher.
> >
> > Signed-off-by: Jasper Orschulko
> > ---
> > .../repo/files/0001-python3-shebang.patch | 21
> > .../0001-Set-REPO_REV-to-v2.17.3.patch | 33
> > +++
> > meta/recipes-devtools/repo/repo.inc | 25 ++
> > meta/recipes-devtools/repo/repo_2.17.3.bb | 7
> > 4 files changed, 86 insertions(+)
> > create mode 100644 meta/recipes-devtools/repo/files/0001-python3-
> > shebang.patch
> > create mode 100644 meta/recipes-devtools/repo/repo-2.17.3/0001-
> > Set-REPO_REV-to-v2.17.3.patch
> > create mode 100644 meta/recipes-devtools/repo/repo.inc
> > create mode 100644 meta/recipes-devtools/repo/repo_2.17.3.bb
> >
> > diff --git a/meta/recipes-devtools/repo/files/0001-python3-
> > shebang.patch b/meta/recipes-devtools/repo/files/0001-python3-
> > shebang.patch
> > new file mode 100644
> > index 00..09ccf58264
> > --- /dev/null
> > +++ b/meta/recipes-devtools/repo/files/0001-python3-shebang.patch
> > @@ -0,0 +1,21 @@
> > +From b8e84b202cd302a7c99288d3835dc9c63071f8f2 Mon Sep 17 00:00:00
> > 2001
> > +From: Jasper Orschulko
> > +Date: Tue, 14 Sep 2021 16:46:51 +0200
> > +Subject: [PATCH] python3 shebang
> > +
> > +---
> > + repo | 2 +-
> > + 1 file changed, 1 insertion(+), 1 deletion(-)
> > +
> > +diff --git a/repo b/repo
> > +index b13e34c..205e0e5 100755
> > +--- a/repo
> > b/repo
> > +@@ -1,4 +1,4 @@
> > +-#!/usr/bin/env python
> > ++#!/usr/bin/env python3
> > + # -*- coding:utf-8 -*-
> > + #
> > + # Copyright (C) 2008 The Android Open Source Project
> > +--
> > +2.33.0
> > diff --git a/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-
> > REPO_REV-to-v2.17.3.patch b/meta/recipes-devtools/repo/repo-
> > 2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
> > new file mode 100644
> > index 00..294a3af53a
> > --- /dev/null
> > +++ b/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-
> > v2.17.3.patch
> > @@ -0,0 +1,33 @@
> > +From bdd2a528da59c28db8ae2986834926de7cebf3ab Mon Sep 17 00:00:00
> > 2001
> > +From: Jasper Orschulko
> > +Date: Thu, 4 Nov 2021 16:55:12 +0100
> > +Subject: [PATCH] Set REPO_REV to v2.17.3
> > +
> > +repo is an unusual tool because it downloads all of its own Python
> > modules
> > +using GPG-signed git tags, and stores those files as part of the
> > project
> > +that it is working with.
> > +
> > +So in order to have a reproducible repo installation within the
> > project
> > +folders, we hardcode the REPO_REV variable to this recipes PV.
> > +
> > +Upstream-Status: Inappropriate [configuration]
> > +Signed-off-by: Jasper Orschulko
> >
> > +---
> > + repo | 2 +-
> > + 1 file changed, 1 insertion(+), 1 deletion(-)
> > +
> > +diff --git a/repo b/repo
> > +index 4cddbf1..cf5f6b1 100755
> > +--- a/repo
> > b/repo
> > +@@ -142,7 +142,7 @@ if __name__ == '__main__':
> > + REPO_URL = os.environ.get('REPO_URL', None)
> > + if not REPO_URL:
> > + REPO_URL = 'https://gerrit.googlesource.com/git-repo'
> > +-REPO_REV = os.environ.get('REPO_REV')
> > ++REPO_REV = 'v2.17.3'
> > + if not REPO_REV:
> > + REPO_REV = 'stable'
> > + # URL to file bug reports for repo tool issues.
> > +--
> > +2.33.1
> > diff --git a/meta/recipes-devtools/repo/repo.inc b/meta/recipes-
> > devtools/repo/repo.inc
> > new file mode 100644
> > index 00..60b32e4d74
> > --- /dev/null
> > +++ b/meta/recipes-devtools/repo/repo.inc
> > @@ -0,0 +1,25 @@
> > +# SPDX-License-Identifier: MIT
> > +# Copyright (C) 2021 iris-GmbH infrared & intelligent sensors
> > +
> > +SUMMARY = "Tool for managing many Git repositories"
> > +DESCRIPTION = "Repo is a tool built on top of Git. Repo helps
> > manage many Git repositories, does the uploads to revision control
> > systems, and automates parts of the development workflow."
> > +HOMEPAGE = "https://android.googlesource.com/tools/repo;
> > +SECTION = "console/utils"
> > +
> >
Re: [bitbake-devel] [oe-core][PATCH 1/2] devtools: Initial recipe for repo 2.17.3
Is this implementation of repo being patched against phoning home to
google everytime and trying to do that pesky auto-update of the tool?
Otherwise this will become an issue when at one point in time an (then)
outdated version of the tool is used in a BB_NO_NETWORK build.
On 05.11.21 14:31, Jasper Orschulko via lists.openembedded.org wrote:
From: Jasper Orschulko
Add a recipe for repo, prerequisite for the repo fetcher.
Signed-off-by: Jasper Orschulko
---
.../repo/files/0001-python3-shebang.patch | 21
.../0001-Set-REPO_REV-to-v2.17.3.patch| 33 +++
meta/recipes-devtools/repo/repo.inc | 25 ++
meta/recipes-devtools/repo/repo_2.17.3.bb | 7
4 files changed, 86 insertions(+)
create mode 100644 meta/recipes-devtools/repo/files/0001-python3-shebang.patch
create mode 100644
meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
create mode 100644 meta/recipes-devtools/repo/repo.inc
create mode 100644 meta/recipes-devtools/repo/repo_2.17.3.bb
diff --git a/meta/recipes-devtools/repo/files/0001-python3-shebang.patch
b/meta/recipes-devtools/repo/files/0001-python3-shebang.patch
new file mode 100644
index 00..09ccf58264
--- /dev/null
+++ b/meta/recipes-devtools/repo/files/0001-python3-shebang.patch
@@ -0,0 +1,21 @@
+From b8e84b202cd302a7c99288d3835dc9c63071f8f2 Mon Sep 17 00:00:00 2001
+From: Jasper Orschulko
+Date: Tue, 14 Sep 2021 16:46:51 +0200
+Subject: [PATCH] python3 shebang
+
+---
+ repo | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/repo b/repo
+index b13e34c..205e0e5 100755
+--- a/repo
b/repo
+@@ -1,4 +1,4 @@
+-#!/usr/bin/env python
++#!/usr/bin/env python3
+ # -*- coding:utf-8 -*-
+ #
+ # Copyright (C) 2008 The Android Open Source Project
+--
+2.33.0
diff --git
a/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
b/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
new file mode 100644
index 00..294a3af53a
--- /dev/null
+++ b/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
@@ -0,0 +1,33 @@
+From bdd2a528da59c28db8ae2986834926de7cebf3ab Mon Sep 17 00:00:00 2001
+From: Jasper Orschulko
+Date: Thu, 4 Nov 2021 16:55:12 +0100
+Subject: [PATCH] Set REPO_REV to v2.17.3
+
+repo is an unusual tool because it downloads all of its own Python modules
+using GPG-signed git tags, and stores those files as part of the project
+that it is working with.
+
+So in order to have a reproducible repo installation within the project
+folders, we hardcode the REPO_REV variable to this recipes PV.
+
+Upstream-Status: Inappropriate [configuration]
+Signed-off-by: Jasper Orschulko
+---
+ repo | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/repo b/repo
+index 4cddbf1..cf5f6b1 100755
+--- a/repo
b/repo
+@@ -142,7 +142,7 @@ if __name__ == '__main__':
+ REPO_URL = os.environ.get('REPO_URL', None)
+ if not REPO_URL:
+ REPO_URL = 'https://gerrit.googlesource.com/git-repo'
+-REPO_REV = os.environ.get('REPO_REV')
++REPO_REV = 'v2.17.3'
+ if not REPO_REV:
+ REPO_REV = 'stable'
+ # URL to file bug reports for repo tool issues.
+--
+2.33.1
diff --git a/meta/recipes-devtools/repo/repo.inc
b/meta/recipes-devtools/repo/repo.inc
new file mode 100644
index 00..60b32e4d74
--- /dev/null
+++ b/meta/recipes-devtools/repo/repo.inc
@@ -0,0 +1,25 @@
+# SPDX-License-Identifier: MIT
+# Copyright (C) 2021 iris-GmbH infrared & intelligent sensors
+
+SUMMARY = "Tool for managing many Git repositories"
+DESCRIPTION = "Repo is a tool built on top of Git. Repo helps manage many Git
repositories, does the uploads to revision control systems, and automates parts of the
development workflow."
+HOMEPAGE = "https://android.googlesource.com/tools/repo;
+SECTION = "console/utils"
+
+LICENSE = "Apache-2.0"
+
+SRC_URI =
"git://g...@gerrit.googlesource.com/git-repo.git;protocol=https;branch=main"
+MIRRORS = "git://g...@gerrit.googlesource.com/git-repo.git
git://github.com/GerritCodeReview/git-repo.git \n"
+
+SRC_URI += "file://0001-python3-shebang.patch"
+
+S = "${WORKDIR}/git"
+
+RDEPENDS_${PN} = "python3"
+
+do_install() {
+install -d ${D}${bindir}
+install -m 755 ${WORKDIR}/git/repo ${D}${bindir}
+}
+
+BBCLASSEXTEND = "native nativesdk"
diff --git a/meta/recipes-devtools/repo/repo_2.17.3.bb
b/meta/recipes-devtools/repo/repo_2.17.3.bb
new file mode 100644
index 00..c26264b9e9
--- /dev/null
+++ b/meta/recipes-devtools/repo/repo_2.17.3.bb
@@ -0,0 +1,7 @@
+# SPDX-License-Identifier: MIT
+# Copyright (C) 2021 iris-GmbH infrared & intelligent sensors
+
+require recipes-devtools/repo/repo.inc
+
+SRCREV = "11b30b91df1f0e03b53da970ec2588e85817bacc"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=3b83ef96387f14655fc854ddc3c6bd57"
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157896):
[oe-core][PATCH 2/2] base.bbclass: Add sysroot deps for repo fetcher
From: Jasper Orschulko
Add git-native and repo-native as prerequisite for the repo fetcher.
Signed-off-by: Jasper Orschulko
---
meta/classes/base.bbclass | 5 +
1 file changed, 5 insertions(+)
diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
index a65fcc6c1d..3298bd1952 100644
--- a/meta/classes/base.bbclass
+++ b/meta/classes/base.bbclass
@@ -665,6 +665,11 @@ python () {
elif uri.scheme == "npm":
d.appendVarFlag('do_fetch', 'depends', '
nodejs-native:do_populate_sysroot')
+elif uri.scheme == "repo":
+needsrcrev = True
+d.appendVarFlag('do_fetch', 'depends', '
repo-native:do_populate_sysroot')
+d.appendVarFlag('do_fetch', 'depends', '
git-native:do_populate_sysroot')
+
# *.lz4 should DEPEND on lz4-native for unpacking
if path.endswith('.lz4'):
d.appendVarFlag('do_unpack', 'depends', '
lz4-native:do_populate_sysroot')
--
2.33.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157895):
https://lists.openembedded.org/g/openembedded-core/message/157895
Mute This Topic: https://lists.openembedded.org/mt/86840280/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[oe-core][PATCH 1/2] devtools: Initial recipe for repo 2.17.3
From: Jasper Orschulko
Add a recipe for repo, prerequisite for the repo fetcher.
Signed-off-by: Jasper Orschulko
---
.../repo/files/0001-python3-shebang.patch | 21
.../0001-Set-REPO_REV-to-v2.17.3.patch| 33 +++
meta/recipes-devtools/repo/repo.inc | 25 ++
meta/recipes-devtools/repo/repo_2.17.3.bb | 7
4 files changed, 86 insertions(+)
create mode 100644 meta/recipes-devtools/repo/files/0001-python3-shebang.patch
create mode 100644
meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
create mode 100644 meta/recipes-devtools/repo/repo.inc
create mode 100644 meta/recipes-devtools/repo/repo_2.17.3.bb
diff --git a/meta/recipes-devtools/repo/files/0001-python3-shebang.patch
b/meta/recipes-devtools/repo/files/0001-python3-shebang.patch
new file mode 100644
index 00..09ccf58264
--- /dev/null
+++ b/meta/recipes-devtools/repo/files/0001-python3-shebang.patch
@@ -0,0 +1,21 @@
+From b8e84b202cd302a7c99288d3835dc9c63071f8f2 Mon Sep 17 00:00:00 2001
+From: Jasper Orschulko
+Date: Tue, 14 Sep 2021 16:46:51 +0200
+Subject: [PATCH] python3 shebang
+
+---
+ repo | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/repo b/repo
+index b13e34c..205e0e5 100755
+--- a/repo
b/repo
+@@ -1,4 +1,4 @@
+-#!/usr/bin/env python
++#!/usr/bin/env python3
+ # -*- coding:utf-8 -*-
+ #
+ # Copyright (C) 2008 The Android Open Source Project
+--
+2.33.0
diff --git
a/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
b/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
new file mode 100644
index 00..294a3af53a
--- /dev/null
+++ b/meta/recipes-devtools/repo/repo-2.17.3/0001-Set-REPO_REV-to-v2.17.3.patch
@@ -0,0 +1,33 @@
+From bdd2a528da59c28db8ae2986834926de7cebf3ab Mon Sep 17 00:00:00 2001
+From: Jasper Orschulko
+Date: Thu, 4 Nov 2021 16:55:12 +0100
+Subject: [PATCH] Set REPO_REV to v2.17.3
+
+repo is an unusual tool because it downloads all of its own Python modules
+using GPG-signed git tags, and stores those files as part of the project
+that it is working with.
+
+So in order to have a reproducible repo installation within the project
+folders, we hardcode the REPO_REV variable to this recipes PV.
+
+Upstream-Status: Inappropriate [configuration]
+Signed-off-by: Jasper Orschulko
+---
+ repo | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/repo b/repo
+index 4cddbf1..cf5f6b1 100755
+--- a/repo
b/repo
+@@ -142,7 +142,7 @@ if __name__ == '__main__':
+ REPO_URL = os.environ.get('REPO_URL', None)
+ if not REPO_URL:
+ REPO_URL = 'https://gerrit.googlesource.com/git-repo'
+-REPO_REV = os.environ.get('REPO_REV')
++REPO_REV = 'v2.17.3'
+ if not REPO_REV:
+ REPO_REV = 'stable'
+ # URL to file bug reports for repo tool issues.
+--
+2.33.1
diff --git a/meta/recipes-devtools/repo/repo.inc
b/meta/recipes-devtools/repo/repo.inc
new file mode 100644
index 00..60b32e4d74
--- /dev/null
+++ b/meta/recipes-devtools/repo/repo.inc
@@ -0,0 +1,25 @@
+# SPDX-License-Identifier: MIT
+# Copyright (C) 2021 iris-GmbH infrared & intelligent sensors
+
+SUMMARY = "Tool for managing many Git repositories"
+DESCRIPTION = "Repo is a tool built on top of Git. Repo helps manage many Git
repositories, does the uploads to revision control systems, and automates parts
of the development workflow."
+HOMEPAGE = "https://android.googlesource.com/tools/repo;
+SECTION = "console/utils"
+
+LICENSE = "Apache-2.0"
+
+SRC_URI =
"git://g...@gerrit.googlesource.com/git-repo.git;protocol=https;branch=main"
+MIRRORS = "git://g...@gerrit.googlesource.com/git-repo.git
git://github.com/GerritCodeReview/git-repo.git \n"
+
+SRC_URI += "file://0001-python3-shebang.patch"
+
+S = "${WORKDIR}/git"
+
+RDEPENDS_${PN} = "python3"
+
+do_install() {
+install -d ${D}${bindir}
+install -m 755 ${WORKDIR}/git/repo ${D}${bindir}
+}
+
+BBCLASSEXTEND = "native nativesdk"
diff --git a/meta/recipes-devtools/repo/repo_2.17.3.bb
b/meta/recipes-devtools/repo/repo_2.17.3.bb
new file mode 100644
index 00..c26264b9e9
--- /dev/null
+++ b/meta/recipes-devtools/repo/repo_2.17.3.bb
@@ -0,0 +1,7 @@
+# SPDX-License-Identifier: MIT
+# Copyright (C) 2021 iris-GmbH infrared & intelligent sensors
+
+require recipes-devtools/repo/repo.inc
+
+SRCREV = "11b30b91df1f0e03b53da970ec2588e85817bacc"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=3b83ef96387f14655fc854ddc3c6bd57"
--
2.33.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157894):
https://lists.openembedded.org/g/openembedded-core/message/157894
Mute This Topic: https://lists.openembedded.org/mt/86840272/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 2/2] fetch2: Fix race condition in latest_revision
From: Martin Koppehel Setting latest_revision contained a race condition, where it would be set to an empty string, if the hash calculation function would take to long. Signed-off-by: Jasper Orschulko --- lib/bb/fetch2/__init__.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/lib/bb/fetch2/__init__.py b/lib/bb/fetch2/__init__.py index 6a38cb09..9dc23d05 100644 --- a/lib/bb/fetch2/__init__.py +++ b/lib/bb/fetch2/__init__.py @@ -1602,7 +1602,9 @@ class FetchMethod(object): try: return revs[key] except KeyError: -revs[key] = rev = self._latest_revision(ud, d, name) +rev = self._latest_revision(ud, d, name) +if rev != '': +revs[key] = rev return rev def sortable_revision(self, ud, d, name): -- 2.33.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#157893): https://lists.openembedded.org/g/openembedded-core/message/157893 Mute This Topic: https://lists.openembedded.org/mt/86840266/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 1/2] fetch2/repo: Implement AUTOREV for repo fetcher
From: Martin Koppehel
- Implement AUTOINC and submodule support for REPO provider
- Implement full srcrev support
- Add comments and fixup empty DL_DIR initialization
- Distinguish between artificial and plain rev
- Comments/documentation
The previous implementation of the repo fetcher could not handle updates
to the repo manifest file, nor deal with dynamic refspecs within this
manifest.
This patch fixes these shortcomings as follows:
During the recipe parsing phase, the repository containing the repo
manifest is cloned. This is done, as we need to parse the XML file
contained within, in order to discover all involved git repositories. A
combined hash is then calculated from the manifest repo, as well as any
git repo specified in the manifest. This hash is used for determining the
necessity of an update.
Additionally, the recipe will throw an error if the repo source is set to
a fixed revision but one or more repositories within the manifest
reference a dynamic refspec. This is done to ensure the reproducibility
of a version-pinned recipe.
Signed-off-by: Jasper Orschulko
---
lib/bb/fetch2/repo.py | 226 --
1 file changed, 198 insertions(+), 28 deletions(-)
diff --git a/lib/bb/fetch2/repo.py b/lib/bb/fetch2/repo.py
index fa4cb814..22ee5b80 100644
--- a/lib/bb/fetch2/repo.py
+++ b/lib/bb/fetch2/repo.py
@@ -3,6 +3,7 @@ BitBake "Fetch" repo (git) implementation
"""
+# Copyright (C) 2021 Martin Koppehel , iris-GmbH infrared &
intelligent sensors
# Copyright (C) 2009 Tom Rini
#
# Based on git.py which is:
@@ -13,10 +14,13 @@ BitBake "Fetch" repo (git) implementation
import os
import bb
+import hashlib
+import xml.etree.ElementTree as ET
from bb.fetch2 import FetchMethod
from bb.fetch2 import runfetchcmd
from bb.fetch2 import logger
+
class Repo(FetchMethod):
"""Class to fetch a module or modules from repo (git) repositories"""
def supports(self, ud, d):
@@ -27,46 +31,74 @@ class Repo(FetchMethod):
def urldata_init(self, ud, d):
"""
-We don"t care about the git rev of the manifests repository, but
-we do care about the manifest to use. The default is "default".
-We also care about the branch or tag to be used. The default is
-"master".
+We do care about the rev of the manifests repository, as well as the
+manifest file. However, when SRCREV=AUTOINC, then we use the specified
+branch in SRC_URI, with a fallback to master.
+use sm=fetch to fetch possibly referenced submodules in repositories.
"""
ud.basecmd = d.getVar("FETCHCMD_repo") or "/usr/bin/env repo"
+ud.gitcmd = d.getVar("FETCHCMD_git") or "git -c
core.fsyncobjectfiles=0"
ud.proto = ud.parm.get('protocol', 'git')
ud.branch = ud.parm.get('branch', 'master')
+
+ud.submodules = ud.parm.get('sm', 'fetch')
ud.manifest = ud.parm.get('manifest', 'default.xml')
if not ud.manifest.endswith('.xml'):
ud.manifest += '.xml'
-ud.localfile = d.expand("repo_%s%s_%s_%s.tar.gz" % (ud.host,
ud.path.replace("/", "."), ud.manifest, ud.branch))
+repodir = d.getVar("REPODIR") or (d.getVar("DL_DIR") + "/repo")
+gitsrcname = "%s%s.%s" % (ud.host, ud.path.replace("/", "."),
ud.manifest)
+ud.codir = os.path.join(repodir, d.getVar("BPN"), gitsrcname)
+
+if ud.user:
+ud.username = ud.user + "@"
+else:
+ud.username = ""
+ud.remoteRepo = "%s://%s%s%s" % (ud.proto, ud.username, ud.host,
ud.path)
+
+ud.repodir = os.path.join(ud.codir, "repo")
+# a temporary directory to compute _latest_revision
+ud.tempdir = os.path.join(ud.codir, "temp")
+ud.stampfile = os.path.join(ud.codir, "__hash.txt")
+ud.setup_revisions(d)
+
+# ud.localfile is used to fill localpath, where the downloaded tarball
is stored.
+# in our case, we want something like repo_$GIT_URL_$MANIFEST_$SRCREV
+# todo: do we want the packagename?
+ud.localfile = "repo_%s%s_%s_%s.tar.gz" % (ud.host,
ud.path.replace("/", "."), ud.manifest, d.getVar("SRCREV"))
+
+def need_update(self, ud, d):
+if d.getVar("SRCREV") == "AUTOINC":
+return True
+return os.path.exists(ud.localfile)
def download(self, ud, d):
"""Fetch url"""
-if os.access(os.path.join(d.getVar("DL_DIR"), ud.localfile), os.R_OK):
-logger.debug("%s already exists (or was stashed). Skipping repo
init / sync.", ud.localpath)
-return
-
-repodir = d.getVar("REPODIR") or (d.getVar("DL_DIR") + "/repo")
-gitsrcname = "%s%s" % (ud.host, ud.path.replace("/", "."))
-codir = os.path.join(repodir, gitsrcname, ud.manifest)
+bb.utils.mkdirhier(ud.repodir)
-if ud.user:
-username = ud.user + "@"
+# we want to run a repo init *always* in case
Re: [OE-core] [PATCH 3/6] linux-libc-headers: update to v5.15
On Fri, Nov 5, 2021 at 7:18 AM Richard Purdie
wrote:
>
> On Thu, 2021-11-04 at 15:48 -0400, bruce.ashfi...@gmail.com wrote:
> > From: Bruce Ashfield
> >
> > No patches needed refreshing or removal, so we just update the
> > SRC_URI and pick up the latest uapi / kernel headers.
> >
> > Signed-off-by: Bruce Ashfield
> > ---
> > meta/conf/distro/include/tcmode-default.inc | 2 +-
> > ...{linux-libc-headers_5.14.bb => linux-libc-headers_5.15.bb} | 4 ++--
> > 2 files changed, 3 insertions(+), 3 deletions(-)
> > rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_5.14.bb
> > => linux-libc-headers_5.15.bb} (81%)
> >
> > diff --git a/meta/conf/distro/include/tcmode-default.inc
> > b/meta/conf/distro/include/tcmode-default.inc
> > index 58f49800c4..86a6b50433 100644
> > --- a/meta/conf/distro/include/tcmode-default.inc
> > +++ b/meta/conf/distro/include/tcmode-default.inc
> > @@ -21,7 +21,7 @@ SDKGCCVERSION ?= "${GCCVERSION}"
> > BINUVERSION ?= "2.37%"
> > GDBVERSION ?= "10.%"
> > GLIBCVERSION ?= "2.34"
> > -LINUXLIBCVERSION ?= "5.14%"
> > +LINUXLIBCVERSION ?= "5.15%"
> > QEMUVERSION ?= "6.1%"
> > GOVERSION ?= "1.16%"
> > # This can not use wildcards like 8.0.% since it is also used in mesa to
> > denote
> > diff --git
> > a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.14.bb
> > b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.15.bb
> > similarity index 81%
> > rename from
> > meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.14.bb
> > rename to meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.15.bb
> > index 282c04d79c..588cc3acd1 100644
> > --- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.14.bb
> > +++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.15.bb
> > @@ -14,7 +14,7 @@ SRC_URI:append = "\
> >
> > LIC_FILES_CHKSUM = "file://COPYING;md5=6bc538ed5bd9a7fc9398086aedcd7e46"
> >
> > -SRC_URI[md5sum] = "a082ef5748b813abca0649dab8be5f52"
> > -SRC_URI[sha256sum] =
> > "7e068b5e0d26a62b10e5320b25dce57588cbbc6f781c090442138c9c9c3271b2"
> > +SRC_URI[md5sum] = "071d49ff4e020d58c04f9f3f76d3b594"
> > +SRC_URI[sha256sum] =
> > "57b2cf6991910e3b67a1b3490022e8a0674b6965c74c12da1e99d138d1991ee8"
> >
> >
>
> Looks like there is a musl issue with the ipx.h header in ppp:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/4299
> https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/4313
ahah. Something my a-quick build didn't hit.
I'll fire up a build here and see how we work around ipx.h going away.
Bruce
>
> Cheers,
>
> Richard
>
>
>
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157891):
https://lists.openembedded.org/g/openembedded-core/message/157891
Mute This Topic: https://lists.openembedded.org/mt/86824895/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH 1/2] gdb: Upgrade to 11.1
On Wed, 2021-11-03 at 18:30 -0700, Khem Raj wrote:
> Drop backported patches
> Changes are here [1]
>
> [1] https://sourceware.org/pipermail/gdb-announce/2021/000129.html
>
> Signed-off-by: Khem Raj
> ---
> meta/conf/distro/include/tcmode-default.inc | 2 +-
> .../gdb/{gdb-10.2.inc => gdb-11.1.inc}| 14 +-
> ...ian_10.2.bb => gdb-cross-canadian_11.1.bb} | 0
> .../{gdb-cross_10.2.bb => gdb-cross_11.1.bb} | 0
> ...make-man-install-relative-to-DESTDIR.patch | 20 +-
> ...ux-nat-Define-_ABIO32-if-not-defined.patch | 8 +-
> ...e-pt_regs-uapi_pt_regs-on-GLIBC-syst.patch | 10 +-
> ...port-for-Renesas-SH-sh4-architecture.patch | 39 +-
> ...readline.a-when-using-disable-static.patch | 12 +-
> .../gdb/gdb/0006-use-asm-sgidefs.h.patch | 8 +-
> ...atch => 0007-Change-order-of-CFLAGS.patch} | 12 +-
> ...8-resolve-restrict-keyword-conflict.patch} | 8 +-
> ...> 0009-Fix-invalid-sigprocmask-call.patch} | 8 +-
> ...h => 0010-gdbserver-ctrl-c-handling.patch} | 10 +-
> ...-arc-Add-support-for-signal-handlers.patch | 218 -
> ...-for-signal-frames-for-Linux-targets.patch | 232 --
> ...count-the-REGNUM-in-supply-collect-g.patch | 104 -
> ...-native-support-for-ARC-in-GNU-Linux.patch | 414 --
> .../gdb/{gdb_10.2.bb => gdb_11.1.bb} | 0
> 19 files changed, 74 insertions(+), 1045 deletions(-)
> rename meta/recipes-devtools/gdb/{gdb-10.2.inc => gdb-11.1.inc} (56%)
> rename meta/recipes-devtools/gdb/{gdb-cross-canadian_10.2.bb =>
> gdb-cross-canadian_11.1.bb} (100%)
> rename meta/recipes-devtools/gdb/{gdb-cross_10.2.bb => gdb-cross_11.1.bb}
> (100%)
> rename meta/recipes-devtools/gdb/gdb/{0008-Change-order-of-CFLAGS.patch =>
> 0007-Change-order-of-CFLAGS.patch} (75%)
> rename
> meta/recipes-devtools/gdb/gdb/{0009-resolve-restrict-keyword-conflict.patch
> => 0008-resolve-restrict-keyword-conflict.patch} (91%)
> rename
> meta/recipes-devtools/gdb/gdb/{0010-Fix-invalid-sigprocmask-call.patch =>
> 0009-Fix-invalid-sigprocmask-call.patch} (90%)
> rename meta/recipes-devtools/gdb/gdb/{0011-gdbserver-ctrl-c-handling.patch
> => 0010-gdbserver-ctrl-c-handling.patch} (82%)
> delete mode 100644
> meta/recipes-devtools/gdb/gdb/0012-arc-Add-support-for-signal-handlers.patch
> delete mode 100644
> meta/recipes-devtools/gdb/gdb/0013-arc-Add-support-for-signal-frames-for-Linux-targets.patch
> delete mode 100644
> meta/recipes-devtools/gdb/gdb/0014-arc-Take-into-account-the-REGNUM-in-supply-collect-g.patch
> delete mode 100644
> meta/recipes-devtools/gdb/gdb/0015-gdb-Add-native-support-for-ARC-in-GNU-Linux.patch
> rename meta/recipes-devtools/gdb/{gdb_10.2.bb => gdb_11.1.bb} (100%)
Breaks on mingw:
https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/4299
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157890):
https://lists.openembedded.org/g/openembedded-core/message/157890
Mute This Topic: https://lists.openembedded.org/mt/86807405/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH 3/6] linux-libc-headers: update to v5.15
On Thu, 2021-11-04 at 15:48 -0400, bruce.ashfi...@gmail.com wrote:
> From: Bruce Ashfield
>
> No patches needed refreshing or removal, so we just update the
> SRC_URI and pick up the latest uapi / kernel headers.
>
> Signed-off-by: Bruce Ashfield
> ---
> meta/conf/distro/include/tcmode-default.inc | 2 +-
> ...{linux-libc-headers_5.14.bb => linux-libc-headers_5.15.bb} | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
> rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_5.14.bb =>
> linux-libc-headers_5.15.bb} (81%)
>
> diff --git a/meta/conf/distro/include/tcmode-default.inc
> b/meta/conf/distro/include/tcmode-default.inc
> index 58f49800c4..86a6b50433 100644
> --- a/meta/conf/distro/include/tcmode-default.inc
> +++ b/meta/conf/distro/include/tcmode-default.inc
> @@ -21,7 +21,7 @@ SDKGCCVERSION ?= "${GCCVERSION}"
> BINUVERSION ?= "2.37%"
> GDBVERSION ?= "10.%"
> GLIBCVERSION ?= "2.34"
> -LINUXLIBCVERSION ?= "5.14%"
> +LINUXLIBCVERSION ?= "5.15%"
> QEMUVERSION ?= "6.1%"
> GOVERSION ?= "1.16%"
> # This can not use wildcards like 8.0.% since it is also used in mesa to
> denote
> diff --git
> a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.14.bb
> b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.15.bb
> similarity index 81%
> rename from meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.14.bb
> rename to meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.15.bb
> index 282c04d79c..588cc3acd1 100644
> --- a/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.14.bb
> +++ b/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_5.15.bb
> @@ -14,7 +14,7 @@ SRC_URI:append = "\
>
> LIC_FILES_CHKSUM = "file://COPYING;md5=6bc538ed5bd9a7fc9398086aedcd7e46"
>
> -SRC_URI[md5sum] = "a082ef5748b813abca0649dab8be5f52"
> -SRC_URI[sha256sum] =
> "7e068b5e0d26a62b10e5320b25dce57588cbbc6f781c090442138c9c9c3271b2"
> +SRC_URI[md5sum] = "071d49ff4e020d58c04f9f3f76d3b594"
> +SRC_URI[sha256sum] =
> "57b2cf6991910e3b67a1b3490022e8a0674b6965c74c12da1e99d138d1991ee8"
>
>
Looks like there is a musl issue with the ipx.h header in ppp:
https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/4299
https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/4313
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157889):
https://lists.openembedded.org/g/openembedded-core/message/157889
Mute This Topic: https://lists.openembedded.org/mt/86824895/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 7/7] libpcre/libpcre2: correct SRC_URI
http://ftp.pcre.org is down, take sources according to links on
http://www.pcre.org
Signed-off-by: Alexander Kanavin
---
meta/recipes-support/libpcre/libpcre2_10.37.bb | 4 +++-
meta/recipes-support/libpcre/libpcre_8.45.bb | 2 +-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-support/libpcre/libpcre2_10.37.bb
b/meta/recipes-support/libpcre/libpcre2_10.37.bb
index e0ead59da6..ccedf688d7 100644
--- a/meta/recipes-support/libpcre/libpcre2_10.37.bb
+++ b/meta/recipes-support/libpcre/libpcre2_10.37.bb
@@ -10,7 +10,9 @@ SECTION = "devel"
LICENSE = "BSD-3-Clause"
LIC_FILES_CHKSUM = "file://LICENCE;md5=6b3022283c9a79238d521848ea9dcb4d"
-SRC_URI = "https://ftp.pcre.org/pub/pcre/pcre2-${PV}.tar.bz2;
+SRC_URI =
"https://github.com/PhilipHazel/pcre2/releases/download/pcre2-${PV}/pcre2-${PV}.tar.bz2;
+
+UPSTREAM_CHECK_URI = "https://github.com/PhilipHazel/pcre2/releases;
SRC_URI[sha256sum] =
"4d95a96e8b80529893b4562be12648d798b957b1ba1aae39606bbc2ab956d270"
diff --git a/meta/recipes-support/libpcre/libpcre_8.45.bb
b/meta/recipes-support/libpcre/libpcre_8.45.bb
index 76b20f5f08..46fedbae48 100644
--- a/meta/recipes-support/libpcre/libpcre_8.45.bb
+++ b/meta/recipes-support/libpcre/libpcre_8.45.bb
@@ -7,7 +7,7 @@ HOMEPAGE = "http://www.pcre.org;
SECTION = "devel"
LICENSE = "BSD-3-Clause"
LIC_FILES_CHKSUM = "file://LICENCE;md5=b5d5d1a69a24ea2718263f1ff85a1c58"
-SRC_URI = "https://ftp.pcre.org/pub/pcre/pcre-${PV}.tar.bz2 \
+SRC_URI = "${SOURCEFORGE_MIRROR}/pcre/pcre-${PV}.tar.bz2 \
file://run-ptest \
file://Makefile \
"
--
2.20.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157888):
https://lists.openembedded.org/g/openembedded-core/message/157888
Mute This Topic: https://lists.openembedded.org/mt/86836030/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 3/7] valgrind: mark ptest-specific patch as inappropriate
I do not think upstream is going to accept this; if you disagree please do the submission. Signed-off-by: Alexander Kanavin --- .../0005-Modify-vg_test-wrapper-to-support-PTEST-formats.patch | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-devtools/valgrind/valgrind/0005-Modify-vg_test-wrapper-to-support-PTEST-formats.patch b/meta/recipes-devtools/valgrind/valgrind/0005-Modify-vg_test-wrapper-to-support-PTEST-formats.patch index 0c399ef52c..a3637ea846 100644 --- a/meta/recipes-devtools/valgrind/valgrind/0005-Modify-vg_test-wrapper-to-support-PTEST-formats.patch +++ b/meta/recipes-devtools/valgrind/valgrind/0005-Modify-vg_test-wrapper-to-support-PTEST-formats.patch @@ -14,7 +14,7 @@ option, --yocto-ptest, the valgrind regression test output is unchanged. Enforce 30 seconds limit for the test. This resume execution of the remaining tests when valgrind hangs. -Upstream-Status: Pending +Upstream-Status: Inappropriate [oe-core specific] Signed-off-by: Dave Lerner Signed-off-by: Tudor Florea -- 2.20.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#157884): https://lists.openembedded.org/g/openembedded-core/message/157884 Mute This Topic: https://lists.openembedded.org/mt/86836026/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 5/7] librsvg: set the needed atomic configuration flags directly per-target
Do not try to mangle the upstream list of targets;
after discussion with upstream it turns out it's neither
necessary nor upstreamable:
https://github.com/crossbeam-rs/crossbeam/pull/751
Signed-off-by: Alexander Kanavin
---
...check-only-the-architecture-not-the-.patch | 143 --
meta/recipes-gnome/librsvg/librsvg_2.52.3.bb | 4 +-
2 files changed, 3 insertions(+), 144 deletions(-)
delete mode 100644
meta/recipes-gnome/librsvg/librsvg/0001-crossbeam-utils-check-only-the-architecture-not-the-.patch
diff --git
a/meta/recipes-gnome/librsvg/librsvg/0001-crossbeam-utils-check-only-the-architecture-not-the-.patch
b/meta/recipes-gnome/librsvg/librsvg/0001-crossbeam-utils-check-only-the-architecture-not-the-.patch
deleted file mode 100644
index 0c1cf59eff..00
---
a/meta/recipes-gnome/librsvg/librsvg/0001-crossbeam-utils-check-only-the-architecture-not-the-.patch
+++ /dev/null
@@ -1,143 +0,0 @@
-From 70557b217644901daaf9d8ef793f5e84c937762e Mon Sep 17 00:00:00 2001
-From: Alexander Kanavin
-Date: Tue, 5 Oct 2021 23:41:59 +0200
-Subject: [PATCH] crossbeam-utils: check only the architecture, not the whole
- target string
-
-There can be custom targets in use, and it's not possible to make a list
-of them; for the check only the first item in the target string is actually
-relevant (the architecture of the target).
-
-Upstream-Status: Pending [needs an upstream ticket and possibly a rework of
list generator script]
-Signed-off-by: Alexander Kanavin
- vendor/crossbeam-utils/.cargo-checksum.json | 4 +-
- vendor/crossbeam-utils/build.rs | 8 ++-
- vendor/crossbeam-utils/no_atomic.rs | 78 -
- 3 files changed, 38 insertions(+), 52 deletions(-)
-
a/vendor/crossbeam-utils/.cargo-checksum.json
-+++ b/vendor/crossbeam-utils/.cargo-checksum.json
-@@ -1 +1,3 @@
--{"files":{"CHANGELOG.md":"5242f1740c65509c465c9a36326d344722facff5f5e58dd064f7b77806b83a46","Cargo.toml":"ac35a7b8ccb16f1ab256951576537aa4179a316c068929c2acef89e0adc12319","LICENSE-APACHE":"a60eea817514531668d7e00765731449fe14d059d3249e0bc93b36de45f759f2","LICENSE-MIT":"5734ed989dfca1f625b40281ee9f4530f91b2411ec01cb748223e7eb87e201ab","README.md":"dfa9fbed47c344c134a63c84b7c0e4651baeac1554b7b3266d0e38643743fc33","benches/atomic_cell.rs":"c927eb3cd1e5ecc4b91adbc3bde98af15ffab4086190792ba64d5cde0e24df3d","build.rs":"68cfc4be02429834a19411fba29cb1cb52c841f03ac8104d1bae59a8b2184f9c","no_atomic.rs":"a2621c1b029c614fb0ab8e3f5cda2e839df88d90d26133181c1b901965f7eec4","src/atomic/atomic_cell.rs":"1a3a1e073340317b5ce7a94e29c6a87db89ff7e00da6b92cb3c0339364c3b084","src/atomic/consume.rs":"7a7736fcd64f6473dfea7653559ffc5e1a2a234df43835f8aa8734862145ac15","src/atomic/mod.rs":"7f6afd5bd0da1f7b51765ab04da4e5f683588ac2d23506e61bf7007bb1e61ba2","src/atomic/seq_lock.rs":"27182e6b87a9db73c5f6831759f8625f9fcdec3c2828204c444aef04f427735a","src/atomic/seq_lock_wide.rs":"9888dd03116bb89ca36d4ab8d5a0b5032107a2983a7eb8024454263b09080088","src/backoff.rs":"7cc7754e15f69b52e92a70d4f49d1bc274693455a0933a2d7eb0605806566af3","src/cache_padded.rs":"6a512698115ad0d5a5b163dbd7a83247e1f1c146c4a30f3fc74b952e3b767b59","src/lib.rs":"6f1bcf157abe06ad8458a53e865bf8efab9fad4a9424790147cee8fefb3795d8","src/sync/mod.rs":"59986f559a8f170a4b3247ab2eea2460b09809d87c8110ed88e4e7103d3519dc","src/sync/parker.rs":"ba8f75bff31b8be9275808e8f393e71cc682dfc1109ceccb12f69a3700cff5be","src/sync/sharded_lock.rs":"14be659744918d0b27db24c56b41c618b0f0484b6761da46561023d96c4c120f","src/sync/wait_group.rs":"32e946a7581c55f8aa9904527b92b177c538fa0cf7cbcfa1d1f25990582cb6ea","src/thread.rs":"0eb5ec1d3c1b40600d88eb70539d14276e32307f5bed2b679f50f6a20777a01e","tests/atomic_cell.rs":"6c9453384ecbbe76f8b97b62f022d478d3a76b4eae1e960f49790970f5d52158","tests/cache_padded.rs":"1bfaff8354c8184e1ee1f902881ca9400b60effb273b0d3f752801a483d2b66d","tests/parker.rs":"6def4721287d9d70b1cfd63ebb34e1c83fbb3376edbad2bc8aac6ef69dd99d20","tests/sharded_lock.rs":"726025ce6351fb56ed629d5a56bdf6e833b7afc5dedfa08de0b056c726b6c26d","tests/thread.rs":"9a7d7d3028c552fd834c68598b04a1cc252a816bc20ab62cec060d6cd09cab10","tests/wait_group.rs":"ad8f0cdfed31f9594a2e0737234d418f8b924d784a4db8d7e469deab8c95f5f8"},"package":"d82cfc11ce7f2c3faef78d8a684447b40d503d9681acebed6cb728d45940c4db"}
-\ No newline at end of file
-+{"files":{"CHANGELOG.md":"5242f1740c65509c465c9a36326d344722facff5f5e58dd064f7b77806b83a46","Cargo.toml":"ac35a7b8ccb16f1ab256951576537aa4179a316c068929c2acef89e0adc12319","LICENSE-APACHE":"a60eea817514531668d7e00765731449fe14d059d3249e0bc93b36de45f759f2","LICENSE-MIT":"5734ed989dfca1f625b40281ee9f4530f91b2411ec01cb748223e7eb87e201ab","README.md":"dfa9fbed47c344c134a63c84b7c0e4651baeac1554b7b3266d0e38643743fc33","benches/atomic_cell.rs":"c927eb3cd1e5ecc4b91adbc3bde98af15ffab4086190792ba64d5cde0e24df3d",
-+"build.rs":"15c1a41a88373231cbc17c7de5ade07c6098455af9cdeef81b576f37ed923354",
[OE-core] [PATCH 6/7] libxml2: mark patch as non-upstreamable
Signed-off-by: Alexander Kanavin --- .../libxml/libxml2/libxml-m4-use-pkgconfig.patch| 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/meta/recipes-core/libxml/libxml2/libxml-m4-use-pkgconfig.patch b/meta/recipes-core/libxml/libxml2/libxml-m4-use-pkgconfig.patch index 90fa193775..a5c112db7b 100644 --- a/meta/recipes-core/libxml/libxml2/libxml-m4-use-pkgconfig.patch +++ b/meta/recipes-core/libxml/libxml2/libxml-m4-use-pkgconfig.patch @@ -5,7 +5,11 @@ Subject: [PATCH] AM_PATH_XML2 uses xml-config which we disable through binconfig-disabled.bbclass, so port it to use pkg-config instead. -Upstream-Status: Pending +This cannot be upstreamed, as the original macro supports various +optional arguments which cannot be supported with a direct call +to pkg-config. + +Upstream-Status: Inappropriate [oe-core specific; see above] Signed-off-by: Ross Burton Rebase to 2.9.9 -- 2.20.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#157887): https://lists.openembedded.org/g/openembedded-core/message/157887 Mute This Topic: https://lists.openembedded.org/mt/86836029/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 4/7] systemd-bootchart: submit musl patches upstream
Signed-off-by: Alexander Kanavin --- ...1-comparison_fn_t-is-glibc-specific-use-raw-signature-.patch | 2 +- .../systemd-bootchart/0002-musl-does-not-provide-printf-h.patch | 2 +- .../0003-musl-does-not-provide-canonicalize_file_name.patch | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/meta/recipes-devtools/systemd-bootchart/systemd-bootchart/0001-comparison_fn_t-is-glibc-specific-use-raw-signature-.patch b/meta/recipes-devtools/systemd-bootchart/systemd-bootchart/0001-comparison_fn_t-is-glibc-specific-use-raw-signature-.patch index f392ceafcc..12eecc989b 100644 --- a/meta/recipes-devtools/systemd-bootchart/systemd-bootchart/0001-comparison_fn_t-is-glibc-specific-use-raw-signature-.patch +++ b/meta/recipes-devtools/systemd-bootchart/systemd-bootchart/0001-comparison_fn_t-is-glibc-specific-use-raw-signature-.patch @@ -12,8 +12,8 @@ systemd/0013-comparison_fn_t-is-glibc-specific-use-raw-signature-.patch Based on work by: Khem Raj Signed-off-by: Tim Orling +Upstream-Status: Submitted [https://github.com/systemd/systemd-bootchart/pull/47] --- -Upstream-Status: Pending src/util.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-devtools/systemd-bootchart/systemd-bootchart/0002-musl-does-not-provide-printf-h.patch b/meta/recipes-devtools/systemd-bootchart/systemd-bootchart/0002-musl-does-not-provide-printf-h.patch index 196272f7a2..8be3bed395 100644 --- a/meta/recipes-devtools/systemd-bootchart/systemd-bootchart/0002-musl-does-not-provide-printf-h.patch +++ b/meta/recipes-devtools/systemd-bootchart/systemd-bootchart/0002-musl-does-not-provide-printf-h.patch @@ -10,8 +10,8 @@ Original patch author: Emil Renner Berthing Includes work by: Khem Raj Signed-off-by: Tim Orling +Upstream-Status: Submitted [https://github.com/systemd/systemd-bootchart/pull/47] --- -Upstream-Status: Pending Makefile.am | 4 + configure.ac | 3 + diff --git a/meta/recipes-devtools/systemd-bootchart/systemd-bootchart/0003-musl-does-not-provide-canonicalize_file_name.patch b/meta/recipes-devtools/systemd-bootchart/systemd-bootchart/0003-musl-does-not-provide-canonicalize_file_name.patch index 7670d95f07..c2c276e458 100644 --- a/meta/recipes-devtools/systemd-bootchart/systemd-bootchart/0003-musl-does-not-provide-canonicalize_file_name.patch +++ b/meta/recipes-devtools/systemd-bootchart/systemd-bootchart/0003-musl-does-not-provide-canonicalize_file_name.patch @@ -9,8 +9,8 @@ systemd/0007-check-for-missing-canonicalize_file_name.patch Based on work by: Khem Raj Signed-off-by: Tim Orling +Upstream-Status: Submitted [https://github.com/systemd/systemd-bootchart/pull/47] --- -Upstream-Status: Pending src/path-util.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- 2.20.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#157885): https://lists.openembedded.org/g/openembedded-core/message/157885 Mute This Topic: https://lists.openembedded.org/mt/86836027/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 1/7] gdbm: upgrade 1.19 -> 1.22
From: Alexander Kanavin
Signed-off-by: Alexander Kanavin
---
meta/recipes-support/gdbm/files/ptest.patch| 18 +-
.../gdbm/{gdbm_1.19.bb => gdbm_1.22.bb}| 3 +--
2 files changed, 10 insertions(+), 11 deletions(-)
rename meta/recipes-support/gdbm/{gdbm_1.19.bb => gdbm_1.22.bb} (90%)
diff --git a/meta/recipes-support/gdbm/files/ptest.patch
b/meta/recipes-support/gdbm/files/ptest.patch
index 1e67dbd554..187f09655d 100644
--- a/meta/recipes-support/gdbm/files/ptest.patch
+++ b/meta/recipes-support/gdbm/files/ptest.patch
@@ -1,4 +1,4 @@
-From 41448708e163c8ec1f980464e7dd6741db427c8a Mon Sep 17 00:00:00 2001
+From 8bea84a598b51a7ac7e50aa8f0f20857a9b6b07b Mon Sep 17 00:00:00 2001
From: Josep Puigdemont
Date: Sun, 4 May 2014 16:02:07 +0200
Subject: [PATCH] Add install-ptest rules.
@@ -13,12 +13,12 @@ Upstream-Status: Pending
2 files changed, 16 insertions(+)
diff --git a/Makefile.am b/Makefile.am
-index ecc03df..9fbbda5 100644
+index 25e200d..03d5ef0 100644
--- a/Makefile.am
+++ b/Makefile.am
-@@ -55,3 +55,8 @@ ChangeLog:
- awk -f $(top_srcdir)/git2chg.awk\
- -v append=$(top_srcdir)/$(prev_change_log) > ChangeLog; \
+@@ -64,3 +64,8 @@ ChangeLog:
+ mv ChangeLog.tmp ChangeLog; \
+ rm -f ChangeLog.tmp; \
fi
+
+install-ptest:
@@ -26,12 +26,12 @@ index ecc03df..9fbbda5 100644
+ $(MAKE) -C $$subdir DESTDIR=$(DESTDIR)/$$subdir $@; \
+ done
diff --git a/tests/Makefile.am b/tests/Makefile.am
-index dbe17dd..06f537f 100644
+index 337cbed..92ec3be 100644
--- a/tests/Makefile.am
+++ b/tests/Makefile.am
-@@ -169,3 +169,14 @@ EXTRA_DIST += \
- gdbmtool/base.exp\
- config/default.exp
+@@ -139,3 +139,14 @@ d_creat_ce_LDADD = ../src/libgdbm.la
../compat/libgdbm_compat.la
+
+ SUBDIRS = gdbmtool
+buildtests: $(check_PROGRAMS) $(TESTSUITE)
+
diff --git a/meta/recipes-support/gdbm/gdbm_1.19.bb
b/meta/recipes-support/gdbm/gdbm_1.22.bb
similarity index 90%
rename from meta/recipes-support/gdbm/gdbm_1.19.bb
rename to meta/recipes-support/gdbm/gdbm_1.22.bb
index 1d1a0c8dd1..5cb12cd57c 100644
--- a/meta/recipes-support/gdbm/gdbm_1.19.bb
+++ b/meta/recipes-support/gdbm/gdbm_1.22.bb
@@ -13,8 +13,7 @@ SRC_URI = "${GNU_MIRROR}/gdbm/gdbm-${PV}.tar.gz \
file://ptest.patch \
"
-SRC_URI[md5sum] = "aeb29c6a90350a4c959cd1df38cd0a7e"
-SRC_URI[sha256sum] =
"37ed12214122b972e18a0d94995039e57748191939ef74115b1d41d8811364bc"
+SRC_URI[sha256sum] =
"f366c823a6724af313b6bbe975b2809f9a157e5f6a43612a72949138d161d762"
inherit autotools gettext texinfo lib_package ptest
--
2.20.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#157882):
https://lists.openembedded.org/g/openembedded-core/message/157882
Mute This Topic: https://lists.openembedded.org/mt/86836024/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 2/7] perl: backport gdbm 1.2x compatibility fixes
Signed-off-by: Alexander Kanavin
---
...e5fdd87aa205011512cd1e6cc655bcf677fd.patch | 31 ++
...2398e766500cb5d83c4d76b642fcf31d997a.patch | 40 +++
...297a58b8f10ab885c19eec48ea076116cc1f.patch | 25
meta/recipes-devtools/perl/perl_5.34.0.bb | 3 ++
4 files changed, 99 insertions(+)
create mode 100644
meta/recipes-devtools/perl/files/5bc1e5fdd87aa205011512cd1e6cc655bcf677fd.patch
create mode 100644
meta/recipes-devtools/perl/files/aacd2398e766500cb5d83c4d76b642fcf31d997a.patch
create mode 100644
meta/recipes-devtools/perl/files/ea57297a58b8f10ab885c19eec48ea076116cc1f.patch
diff --git
a/meta/recipes-devtools/perl/files/5bc1e5fdd87aa205011512cd1e6cc655bcf677fd.patch
b/meta/recipes-devtools/perl/files/5bc1e5fdd87aa205011512cd1e6cc655bcf677fd.patch
new file mode 100644
index 00..1cb65d932c
--- /dev/null
+++
b/meta/recipes-devtools/perl/files/5bc1e5fdd87aa205011512cd1e6cc655bcf677fd.patch
@@ -0,0 +1,31 @@
+From 5bc1e5fdd87aa205011512cd1e6cc655bcf677fd Mon Sep 17 00:00:00 2001
+From: Sergey Poznyakoff
+Date: Wed, 23 Jun 2021 15:31:42 +0300
+Subject: [PATCH] Fix definition of ITEM_NOT_FOUND for pre-1.13 versions.
+
+Upstream-Status: Backport
+Signed-off-by: Alexander Kanavin
+---
+ ext/GDBM_File/GDBM_File.xs | 9 +
+ 1 file changed, 5 insertions(+), 4 deletions(-)
+
+diff --git a/ext/GDBM_File/GDBM_File.xs b/ext/GDBM_File/GDBM_File.xs
+index 494c2889ca89..0125b5dcac4d 100644
+--- a/ext/GDBM_File/GDBM_File.xs
b/ext/GDBM_File/GDBM_File.xs
+@@ -145,10 +145,11 @@ output_datum(pTHX_ SV *arg, char *str, int size)
+ #define gdbm_setopt(db,optflag,optval,optlen) not_here("gdbm_setopt")
+ #endif
+
+-#if GDBM_VERSION_MAJOR == 1 && GDBM_VERSION_MINOR < 13
+-/* Prior to 1.13, gdbm_fetch family functions set gdbm_errno to GDBM_NO_ERROR
+- if the requested key did not exist */
+-# define ITEM_NOT_FOUND() (gdbm_errno == GDBM_NO_ERROR)
++#if GDBM_VERSION_MAJOR == 1 && GDBM_VERSION_MINOR < 13
++/* Prior to 1.13, only gdbm_fetch set GDBM_ITEM_NOT_FOUND if the requested
++ key did not exist. Other similar function wouls set GDBM_NO_ERROR instead.
++ The GDBM_ITEM_NOT_FOUND existeds as early as in 1.7.3 */
++# define ITEM_NOT_FOUND() (gdbm_errno == GDBM_NO_ERROR || gdbm_errno ==
GDBM_ITEM_NOT_FOUND)
+ #else
+ # define ITEM_NOT_FOUND() (gdbm_errno == GDBM_ITEM_NOT_FOUND)
+ #endif
diff --git
a/meta/recipes-devtools/perl/files/aacd2398e766500cb5d83c4d76b642fcf31d997a.patch
b/meta/recipes-devtools/perl/files/aacd2398e766500cb5d83c4d76b642fcf31d997a.patch
new file mode 100644
index 00..628903f41c
--- /dev/null
+++
b/meta/recipes-devtools/perl/files/aacd2398e766500cb5d83c4d76b642fcf31d997a.patch
@@ -0,0 +1,40 @@
+From aacd2398e766500cb5d83c4d76b642fcf31d997a Mon Sep 17 00:00:00 2001
+From: Sergey Poznyakoff
+Date: Wed, 23 Jun 2021 10:26:50 +0300
+Subject: [PATCH] Fix GDBM_File to compile with version 1.20 and earlier
+
+* ext/GDBM_File/GDBM_File.xs (ITEM_NOT_FOUND): Define conditionally,
+depending on the GDBM_VERSION_MAJOR and GDBM_VERSION_MINOR.
+Don't assume GDBM_ITEM_NOT_FOUND is a define (it isn't since
+gdbm commit d3e27957).
+
+Upstream-Status: Backport
+Signed-off-by: Alexander Kanavin
+---
+ ext/GDBM_File/GDBM_File.xs | 11 +--
+ 1 file changed, 5 insertions(+), 6 deletions(-)
+
+diff --git a/ext/GDBM_File/GDBM_File.xs b/ext/GDBM_File/GDBM_File.xs
+index cd0bb6f26ffa..494c2889ca89 100644
+--- a/ext/GDBM_File/GDBM_File.xs
b/ext/GDBM_File/GDBM_File.xs
+@@ -145,14 +145,13 @@ output_datum(pTHX_ SV *arg, char *str, int size)
+ #define gdbm_setopt(db,optflag,optval,optlen) not_here("gdbm_setopt")
+ #endif
+
+-#ifndef GDBM_ITEM_NOT_FOUND
+-# define GDBM_ITEM_NOT_FOUND GDBM_NO_ERROR
+-#endif
+-
++#if GDBM_VERSION_MAJOR == 1 && GDBM_VERSION_MINOR < 13
+ /* Prior to 1.13, gdbm_fetch family functions set gdbm_errno to GDBM_NO_ERROR
+if the requested key did not exist */
+-#define ITEM_NOT_FOUND()\
+-(gdbm_errno == GDBM_ITEM_NOT_FOUND || gdbm_errno == GDBM_NO_ERROR)
++# define ITEM_NOT_FOUND() (gdbm_errno == GDBM_NO_ERROR)
++#else
++# define ITEM_NOT_FOUND() (gdbm_errno == GDBM_ITEM_NOT_FOUND)
++#endif
+
+ #define CHECKDB(db) do {\
+ if (!db->dbp) { \
diff --git
a/meta/recipes-devtools/perl/files/ea57297a58b8f10ab885c19eec48ea076116cc1f.patch
b/meta/recipes-devtools/perl/files/ea57297a58b8f10ab885c19eec48ea076116cc1f.patch
new file mode 100644
index 00..3864f1a121
--- /dev/null
+++
b/meta/recipes-devtools/perl/files/ea57297a58b8f10ab885c19eec48ea076116cc1f.patch
@@ -0,0 +1,25 @@
+From ea57297a58b8f10ab885c19eec48ea076116cc1f Mon Sep 17 00:00:00 2001
+From: Sergey Poznyakoff
+Date: Wed, 23 Jun 2021 14:24:47 +0300
+Subject: [PATCH] Raise version number in ext/GDBM_File/GDBM_File.pm
+
+Upstream-Status: Backport
+Signed-off-by: Alexander Kanavin
+
+---
+ ext/GDBM_File/GDBM_File.pm |
