From: <olani@axis.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [RFC PATCH 0/5] Remove automake patch that changes path to test-driver
Date: Mon, 11 Nov 2024 09:35:36 +0100 [thread overview]
Message-ID: <20241111083541.291594-1-olani@axis.com> (raw)
From: Ola x Nilsson <olani@axis.com>
Fixes [YOCTO #15635]
The automake patch
"Set relative to top_builddir path in Makefile to access"
sets the default path of `test-driver` to
`$(top_builddir)/$(config_aux_dir)` instead of the normal
`$(top_srcdir)/$(config_aux_dir)`.
This breaks `check test` for Automake projects in generated images.
To reproduce, use core-image-kernel-dev with git added.
git clone https://git.kernel.org/pub/scm/linux/kernel/git/kay/libabc.git
(cd libabc && ./autogen.sh)
mkdir build
cd build
../libabc/configure CFLAGS='-g -O0' --prefix=/usr --sysconfdir=/etc --libdir=/usr/lib
make check
/bin/sh: ./build-aux/test-driver: No such file or directory
Removing the patch makes the checks complete successfully.
Some ptests depend on this patch to find test-driver. They need to be
addressed individually. In all cases I've found so far this is just
another sed substitution and should work even before removing the
patch.
I have not verified the ptests in meta-openembedded yet, but I'm
working on it.
Ola x Nilsson (5):
attr: Fix the ptest path to test-driver
sed: Fix the ptest path to test-driver
parted: Fix the ptest path to test-driver
strace: Fix the ptest path to test-driver
automake: Remove patch that changes path to test-driver
...top_builddir-path-in-Makefile-to-acc.patch | 50 -------------------
.../automake/automake_1.17.bb | 1 -
meta/recipes-devtools/strace/strace_6.11.bb | 4 +-
meta/recipes-extended/parted/parted_3.6.bb | 16 +++---
meta/recipes-extended/sed/sed_4.9.bb | 1 +
meta/recipes-support/attr/attr.inc | 11 ++--
6 files changed, 20 insertions(+), 63 deletions(-)
delete mode 100644 meta/recipes-devtools/automake/automake/0005-Set-relative-to-top_builddir-path-in-Makefile-to-acc.patch
--
2.39.5
next reply other threads:[~2024-11-11 8:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 8:35 olani [this message]
2024-11-11 8:35 ` [RFC PATCH 1/5] attr: Fix the ptest path to test-driver olani
2024-11-12 9:35 ` [OE-core] " Richard Purdie
2024-11-13 8:37 ` Ola x Nilsson
2024-11-11 8:35 ` [RFC PATCH 2/5] sed: " olani
2024-11-11 8:35 ` [RFC PATCH 3/5] parted: " olani
2024-11-11 8:35 ` [RFC PATCH 4/5] strace: " olani
2024-11-11 8:35 ` [RFC PATCH 5/5] automake: Remove patch that changes " olani
2024-11-11 10:52 ` [OE-core] [RFC PATCH 0/5] Remove automake " Alexander Kanavin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241111083541.291594-1-olani@axis.com \
--to=olani@axis.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.