From: Darren Hart <dvhart@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/4] autotools.bbclass: Report the missing configure path
Date: Wed, 30 Nov 2011 14:57:50 -0800 [thread overview]
Message-ID: <4ED6B4EE.6000703@linux.intel.com> (raw)
In-Reply-To: <CAMKF1sojotYjyRDVaVu0poUDRpTYMhA_9sX7sNvLQW7n-bL5Uw@mail.gmail.com>
On 11/30/2011 02:48 PM, Khem Raj wrote:
>>>> - bbfatal "no configure script found"
>>>> + bbfatal "no configure script found at $cfgscript"
>>>
>>> why not just do one line change something like
>>>
>>> bbfatal "configure script ${S}/configure not found"
>>
>> I prefer to use a variable when I need a value more than once. It avoids
>> future bugs where one is changed and the others were missed. As this
>> string is used 4 times, it seemed like the right call.
>
> ok with variable still the cfgscript itself is the script and the
> message "no configure script found at $cfgscript"
> seems like $cfgscript is a location. you may want to make it
> "$cfgscript configure script not found" or something
I can see that (although I think can be argued this is correct as well -
a path with a filename is still a location). I was copying the language
used elsewhere... but from where is eluding my search at the moment. RP
has pulled these already I believe, so if the language here truly
bothers you, we can address it in a follow-on. Personally I don't think
it's really worth the trouble.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-11-30 23:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 21:49 [PATCH 0/4] Cleanups: grub, autotools, meta-environment Darren Hart
2011-11-30 21:49 ` [PATCH 1/4] meta-environment: Fix a typo in do_populate_sysroot[noexec] Darren Hart
2011-11-30 21:49 ` [PATCH 2/4] autotools.bbclass: Report the missing configure path Darren Hart
2011-11-30 22:31 ` Khem Raj
2011-11-30 22:37 ` Darren Hart
2011-11-30 22:48 ` Khem Raj
2011-11-30 22:57 ` Darren Hart [this message]
2011-11-30 23:26 ` Khem Raj
2011-11-30 21:49 ` [PATCH 3/4] grub: Use COMPATIBLE_MACHINE Darren Hart
2011-11-30 21:57 ` Koen Kooi
2011-11-30 22:04 ` Darren Hart
2011-11-30 21:49 ` [PATCH 4/4] grub: Drop "apply=yes" from patch Darren Hart
2011-11-30 22:24 ` [PATCH 0/4] Cleanups: grub, autotools, meta-environment Richard Purdie
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=4ED6B4EE.6000703@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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