From: Robert Yang <liezhi.yang@windriver.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: "_append" error in gdb-cross-canadian.inc?
Date: Thu, 5 Mar 2015 16:10:50 +0800 [thread overview]
Message-ID: <54F80F8A.4040909@windriver.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1503050259530.21019@Device-040570>
On 03/05/2015 04:01 PM, Robert P. J. Day wrote:
>
> EXTRA_OECONF_append = "--with-python=${WORKDIR}/python"
> ^??
>
> does that not require a leading space there?
It is required, this one doesn't cause error is because in gdb-common.inc:
EXTRA_OECONF = "[snip] \
--disable-rpath \
"
If:
EXTRA_OECONF = "[snip] \
--disable-rpath"
Then there would be errors.
// Robert
>
> rday
>
next prev parent reply other threads:[~2015-03-05 8:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 8:01 "_append" error in gdb-cross-canadian.inc? Robert P. J. Day
2015-03-05 8:06 ` Robert P. J. Day
2015-03-05 8:43 ` Martin Jansa
2015-03-05 9:11 ` Robert P. J. Day
2015-03-05 8:10 ` Robert Yang [this message]
2015-03-05 8:40 ` Robert P. J. Day
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=54F80F8A.4040909@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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