From: Randy Witt <randy.e.witt@linux.intel.com>
To: Gary Robertson <gary.robertson@linaro.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Mike Holmes <mike.holmes@linaro.org>
Subject: Re: Autoconf problems in OE build of LTP realtime tests
Date: Fri, 05 Sep 2014 15:34:29 -0700 [thread overview]
Message-ID: <540A3A75.4040503@linux.intel.com> (raw)
In-Reply-To: <CAF7YWnxMgNYAFH9=TFJvxwumF36KH=nDnZPPUKn3iazOwh1wJA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
> I am not personally familiar with the detailed function of the autoconf
> macros, and I can find no documentation about how OE interacts with
> those macros in order to coerce them into configuring for the target
> machine in a cross-build environment... so I am hoping the autoconf
> experts at OE can shed some light on this and at least provide some
> clues as to where to look for the problem and possible resolution. Any
> insight you can provide in this matter would be appreciated.
Gary,
I looked at the configure logs on an x86 build and saw the same problem.
By default the autotools.bbclass searches for m4 macros in the source
tree. But it searches a depth that is lower than the directory depth of
the location of testcases/realtime/m4. That seems to be causing some of
the macros to be missing and falsely causing features to be missing.
I made this patch and it seemed to address the issue. Let me know if it
resolves the issues you are seeing.
[-- Attachment #2: 0001-ltp-Add-additional-m4-path-to-autoconf.patch --]
[-- Type: text/plain, Size: 1165 bytes --]
From bce5869545cacd4923b1efcf6e1218f65ad46af7 Mon Sep 17 00:00:00 2001
From: Randy Witt <randy.e.witt@linux.intel.com>
Date: Fri, 5 Sep 2014 15:00:59 -0700
Subject: [PATCH] ltp: Add additional m4 path to autoconf.
The ltp code has some m4 macros that are deeper than the default depth
that the directory depth the autotools.bbclass checks. This causes some
macros to not be found and for supported features to not be enabled.
This patch adds the extra m4 path to the autoconf arguments.
---
meta/recipes-extended/ltp/ltp_20140422.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-extended/ltp/ltp_20140422.bb b/meta/recipes-extended/ltp/ltp_20140422.bb
index c658bc0..0b29ea4 100644
--- a/meta/recipes-extended/ltp/ltp_20140422.bb
+++ b/meta/recipes-extended/ltp/ltp_20140422.bb
@@ -37,6 +37,7 @@ TARGET_CC_ARCH += "${LDFLAGS}"
export prefix = "/opt/ltp"
export exec_prefix = "/opt/ltp"
+EXTRA_AUTORECONF += "-I ${S}/testcases/realtime/m4"
EXTRA_OECONF = " --with-power-management-testsuite --with-realtime-testsuite "
# ltp doesn't regenerate ffsb-6.0-rc2 configure and hardcode configure call.
--
1.9.3
next prev parent reply other threads:[~2014-09-05 22:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 20:36 Autoconf problems in OE build of LTP realtime tests Gary Robertson
2014-09-05 21:51 ` Peter A. Bigot
2014-09-05 22:34 ` Randy Witt [this message]
2014-09-29 11:07 ` Gary Robertson
2014-09-29 18:52 ` Gary Robertson
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=540A3A75.4040503@linux.intel.com \
--to=randy.e.witt@linux.intel.com \
--cc=gary.robertson@linaro.org \
--cc=mike.holmes@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox