From: Randy MacLeod <randy.macleod@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] ptest-runner: trivial fixes and refine
Date: Thu, 19 Sep 2013 11:04:01 -0400 [thread overview]
Message-ID: <523B1261.1060709@windriver.com> (raw)
In-Reply-To: <20130919114753.GA26522@sestofb10.enea.se>
On 13-09-19 07:47 AM, Björn Stenberg wrote:
> Chris Larson wrote:
>> On Wed, Sep 11, 2013 at 2:17 AM, <rongqing.li@windriver.com> wrote:
>>
>>> + for x in `find -L ./ -name run-ptest -type f -perm /u+x,g+x`
>>> + do
>>>
>>
>> As far as I can tell, busybox find doesn't support -L, so this adds an
>> implicit, undeclared dependency upon findutils.
>
> Rongqing, are you planning on fixing this? As committed, ptest-runner can't run on busybox systems
>
Yes, Roy will fix this. He's on holiday for a few days.
I presume he'll add a check to see which arg to use for find
rather than add a dependency on findutils.
> (which I'd argue are the majority of embedded systems).
That's becoming less true over time, IMO.
It seems that more and more embedded linux users are on bigger
targets that use the discrete GNU tools.
--
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350
next prev parent reply other threads:[~2013-09-19 15:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 9:17 [PATCH 0/1 v2] ptest-runner: trivial fixes and refine rongqing.li
2013-09-11 9:17 ` [PATCH 1/1] " rongqing.li
2013-09-12 20:45 ` Chris Larson
2013-09-17 13:35 ` Björn Stenberg
2013-09-19 11:47 ` Björn Stenberg
2013-09-19 15:04 ` Randy MacLeod [this message]
2013-09-20 9:17 ` Björn Stenberg
-- strict thread matches above, loose matches on Subject: below --
2013-09-11 7:34 [PATCH 0/1] " rongqing.li
2013-09-11 7:34 ` [PATCH 1/1] " rongqing.li
2013-09-11 8:40 ` Richard Purdie
2013-09-11 9:02 ` Rongqing Li
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=523B1261.1060709@windriver.com \
--to=randy.macleod@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