From: Richard Purdie <[email protected]> Add some further info to the patch based on upsream changes. Given the last release in 2017 and glaring issues on at least armv5, it does raise the question on whether we should drop this. There are probably better compression tools now.
Signed-off-by: Richard Purdie <[email protected]> --- .../lzo/0001-Use-memcpy-instead-of-reinventing-it.patch | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/meta/recipes-support/lzo/lzo/0001-Use-memcpy-instead-of-reinventing-it.patch b/meta/recipes-support/lzo/lzo/0001-Use-memcpy-instead-of-reinventing-it.patch index db3a70e8031..4e6ca4132b5 100644 --- a/meta/recipes-support/lzo/lzo/0001-Use-memcpy-instead-of-reinventing-it.patch +++ b/meta/recipes-support/lzo/lzo/0001-Use-memcpy-instead-of-reinventing-it.patch @@ -10,6 +10,13 @@ Change suggested by Julian Taylor. Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757037 +RP: Patch is still in debian as of 20220524 in a revised form: +https://sources.debian.org/patches/lzo2/2.10-2/ +https://sources.debian.org/patches/lzo2/2.10-2/0001-Conditionally-replace-reinvention-of-memcpy-with-cal.patch/ + +We likely need this in OE to prevent against unaligned accesses +on systems such as armv5. + Upstream-Status: Pending Signed-off-by: Saul Wold <[email protected]> --- -- 2.25.1
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#166071): https://lists.openembedded.org/g/openembedded-core/message/166071 Mute This Topic: https://lists.openembedded.org/mt/91313379/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
