Openembedded Core Discussions
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
	<openembedded-core@lists.openembedded.org>,
	Randy Witt <randy.e.witt@intel.com>
Subject: Re: [PATCH 1/8] populate_sdk_ext: install the latest buildtools-tarball
Date: Thu, 20 Aug 2015 15:08:20 +0800	[thread overview]
Message-ID: <55D57CE4.7010607@windriver.com> (raw)
In-Reply-To: <1839307.RBueBEjXet@peggleto-mobl.ger.corp.intel.com>

On 08/18/2015 09:51 PM, Paul Eggleton wrote:
> On Monday 10 August 2015 11:17:59 Chen Qi wrote:
>> If we do `bitbake buildtools-tarball' and then after one day do `bitbake
>> core-image-minimal -c populate_sdk_ext', we would meet errors like below.
>>
>> | install: cannot stat
>> | '/buildarea2/chenqi/poky/build-systemd/tmp/deploy/sdk/
>>
>> poky-glibc-x86_64-buildtools-tarball-core2-64-buildtools-nativesdk-standalon
>> e -1.8+snapshot-20150429.sh': No such file or directory
>>
>> The problem is that the output name for buildtools-tarball has ${DATE} in
>> it. So if populate_sdk_ext task is executed but buildtools-tarball is not
>> rebuilt, the above error appears.
>>
>> Instead of hardcoding ${DISTRO_VERSION} which consists of ${DATE} in the
>> install_tools() function, we should find the latest buildtools-tarball based
>> on the modification time and install it.
>>
>> [YOCTO #7674]
>>
>> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
>> ---
>>   meta/classes/populate_sdk_ext.bbclass | 4 +++-
>>   1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/meta/classes/populate_sdk_ext.bbclass
>> b/meta/classes/populate_sdk_ext.bbclass index a36bf16..b6725e0 100644
>> --- a/meta/classes/populate_sdk_ext.bbclass
>> +++ b/meta/classes/populate_sdk_ext.bbclass
>> @@ -169,7 +169,9 @@ install_tools() {
>>   	lnr ${SDK_OUTPUT}/${SDKPATH}/${scriptrelpath}/recipetool
>> ${SDK_OUTPUT}/${SDKPATHNATIVE}${bindir_nativesdk}/recipetool touch
>> ${SDK_OUTPUT}/${SDKPATH}/.devtoolbase
>>
>> -	install
>> ${SDK_DEPLOY}/${DISTRO}-${TCLIBC}-${SDK_ARCH}-buildtools-tarball-${TUNE_PKG
>> ARCH}-buildtools-nativesdk-standalone-${DISTRO_VERSION}.sh
>> ${SDK_OUTPUT}/${SDKPATH} +	# find latest buildtools-tarball and install it
>> +	buildtools_path=`ls -t1
>> ${SDK_DEPLOY}/${DISTRO}-${TCLIBC}-${SDK_ARCH}-buildtools-tarball-${TUNE_PKG
>> ARCH}-buildtools-nativesdk-standalone-*.sh | head -n1` +	install
>> $buildtools_path ${SDK_OUTPUT}/${SDKPATH}
>>
>>   	install ${SDK_DEPLOY}/${BUILD_ARCH}-nativesdk-libc.tar.bz2
>> ${SDK_OUTPUT}/${SDKPATH} }
> Hmm, it turns out there's another problem here - this assumes SDK_NAME is set
> as it is in poky. Perhaps we correct that in a follow-up patch though, but
> it'll be a little bit tricky as it'll need to be done by getting the actual
> value of SDK_NAME as it would have been when IMAGE_BASENAME is "buildtools-
> tarball".
>
> The more I think about this though the more I wonder why we're bothering with
> buildtools instead of just bundling its contents inside the native part of the
> extensible SDK itself. Randy can you remind me why we did it that way?
>
> Cheers,
> Paul
>
Hi Paul,

I've dropped this patch from the patchset and sent out V2.
I think we can fix this buildtool problem in other patches.

Best Regards,
Chen Qi


  reply	other threads:[~2015-08-20  7:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10  3:17 [PATCH 0/8] Extensible SDK fixes Chen Qi
2015-08-10  3:17 ` [PATCH 1/8] populate_sdk_ext: install the latest buildtools-tarball Chen Qi
2015-08-18 13:51   ` Paul Eggleton
2015-08-20  7:08     ` ChenQi [this message]
2015-08-10  3:18 ` [PATCH 2/8] copy_buildsystem: make sure bitbake directory is copied Chen Qi
2015-08-10  3:18 ` [PATCH 3/8] populate_sdk_ext: consider custom configuration in local.conf Chen Qi
2015-08-10  3:18 ` [PATCH 4/8] populate_sdk_ext: don't remove the native qemu dependencies Chen Qi
2015-08-10  3:18 ` [PATCH 5/8] Extensible SDK: allow for installation without preparing build system Chen Qi
2015-08-10 15:39   ` Christopher Larson
2015-08-12 15:39     ` Paul Eggleton
2015-08-10  3:18 ` [PATCH 6/8] oe-publish-sdk: add script Chen Qi
2015-08-12 15:39   ` Paul Eggleton
2015-08-10  3:18 ` [PATCH 7/8] populate_sdk_ext: record SDK_TARGETS in devtool.conf Chen Qi
2015-08-10  3:18 ` [PATCH 8/8] devtool: add sdk.py plugin Chen Qi
2015-08-10 15:33   ` Christopher Larson
2015-08-12 16:41   ` Paul Eggleton
2015-08-12 16:42 ` [PATCH 0/8] Extensible SDK fixes Paul Eggleton

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=55D57CE4.7010607@windriver.com \
    --to=qi.chen@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    --cc=randy.e.witt@intel.com \
    /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