From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] autotools.bbclass: use relative path to run configure script
Date: Tue, 12 Jan 2016 10:04:24 +0800 [thread overview]
Message-ID: <56945F28.70608@windriver.com> (raw)
In-Reply-To: <cover.1452489034.git.liezhi.yang@windriver.com>
Thanks all, I updated "glibc-initial.inc: use relative path to run configure",
now it should work for external source:
git://git.openembedded.org/openembedded-core-contrib rbt/relative
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/relative
Robert Yang (2):
glibc-initial.inc: use relative path to run configure
autotools.bbclass: use relative path to run configure script
diff --git a/meta/recipes-core/glibc/glibc-initial.inc
b/meta/recipes-core/glibc/glibc-initial.inc
index 8e81f09..7214f71 100644
--- a/meta/recipes-core/glibc/glibc-initial.inc
+++ b/meta/recipes-core/glibc/glibc-initial.inc
@@ -11,7 +11,8 @@ TOOLCHAIN_OPTIONS = " --sysroot=${STAGING_DIR_TCBOOTSTRAP}"
do_configure () {
(cd ${S} && gnu-configize) || die "failure in running gnu-configize"
find ${S} -name "configure" | xargs touch
- ${S}/configure --host=${TARGET_SYS} --build=${BUILD_SYS} \
+ cfgscript=`python -c "import os; print os.path.relpath('${S}',
'.')"`/configure
+ $cfgscript --host=${TARGET_SYS} --build=${BUILD_SYS} \
--prefix=/usr \
--without-cvs --disable-sanity-checks \
--with-headers=${STAGING_DIR_TARGET}${includedir} \
// Robert
On 01/11/2016 01:11 PM, Robert Yang wrote:
> Hi,
>
> The 2 patches can reduce a lot of QA Issues for buildpaths.
>
> // Robert
>
> The following changes since commit 5661d8cb7849df62358368743134c0aaf523965e:
>
> image: Really remove lockfiles flag (2016-01-07 13:41:47 +0000)
>
> are available in the git repository at:
>
> git://git.openembedded.org/openembedded-core-contrib rbt/relative
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/relative
>
> Robert Yang (2):
> glibc-initial.inc: use relative path to run configure
> autotools.bbclass: use relative path to run configure script
>
> meta/classes/autotools.bbclass | 4 +++-
> meta/recipes-core/glibc/glibc-initial.inc | 2 +-
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
prev parent reply other threads:[~2016-01-12 2:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 5:11 [PATCH 0/2] autotools.bbclass: use relative path to run configure script Robert Yang
2016-01-11 5:11 ` [PATCH 1/2] glibc-initial.inc: use relative path to run configure Robert Yang
2016-01-11 14:55 ` Trevor Woerner
2016-01-11 15:06 ` Mark Hatle
2016-01-11 16:18 ` Christopher Larson
2016-01-11 16:25 ` Mark Hatle
2016-01-11 5:11 ` [PATCH 2/2] autotools.bbclass: use relative path to run configure script Robert Yang
2016-01-12 2:04 ` Robert Yang [this message]
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=56945F28.70608@windriver.com \
--to=liezhi.yang@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox