From: Darren Hart <dvhart@linux.intel.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 1/3] trace-cmd: fix cross-compilation
Date: Thu, 30 Dec 2010 14:29:59 -0800 [thread overview]
Message-ID: <4D1D07E7.7010000@linux.intel.com> (raw)
In-Reply-To: <AANLkTi=HVSpVxnx9QbU++mRMMW=csPz13PyT+vVX28b7@mail.gmail.com>
On 12/30/2010 01:02 PM, Bruce Ashfield wrote:
> On Tue, Dec 28, 2010 at 8:17 PM, Darren Hart<dvhart@linux.intel.com> wrote:
>> The trace-cmd Makefile forces certain variables, such as CC and AR.
>> It was using the host gcc and loader, fix it to use the poky-built
>> cross-compiler and linker.
>>
>> inherit pkgconfig to ensure we don't use the host pkg-config.
>>
>> Remove unecessary variables from the oemake commands, such as ARCH
>> and LD which aren't used by the Makefile.
>>
>> Signed-off-by: Darren Hart<dvhart@linux.intel.com>
>> CC: Tom Zanussi<tom.zanussi@intel.com>
>
> I actually hacked up the original of this one .. ;)
Right, sorry, forgot to check git blame on this one.
>
>
>> ---
>> meta/recipes-kernel/trace-cmd/trace-cmd_git.bb | 12 +++++-------
>> 1 files changed, 5 insertions(+), 7 deletions(-)
>>
>> diff --git a/meta/recipes-kernel/trace-cmd/trace-cmd_git.bb b/meta/recipes-kernel/trace-cmd/trace-cmd_git.bb
>> index e375afc..a7eca5f 100644
>> --- a/meta/recipes-kernel/trace-cmd/trace-cmd_git.bb
>> +++ b/meta/recipes-kernel/trace-cmd/trace-cmd_git.bb
>> @@ -2,18 +2,16 @@ DESCRIPTION = "User interface to Ftrace"
>> LICENSE = "GPL"
>> LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe"
>>
>> -PR = r1
>> +PR = r2
>> PV = "1.0.4+git${SRCPV}"
>>
>> +inherit pkgconfig
>> +
>> SRC_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git;protocol=git"
>> S = "${WORKDIR}/git"
>>
>> -
>> -do_compile() {
>> - oe_runmake ARCH="${ARCH}" CC="${CC}" LD="${LD}" prefix=${prefix}
>> -}
>> +EXTRA_OEMAKE = "'CC=${CC}' 'AR=${AR}' 'prefix=${prefix}'"
>
> So we've determined that we don't need ARCH anymore ? At one point
> this did. Or is it coming from the pkgconfig inheritance now ?
Good question. My understanding of setting these variables here was to
override whatever the Makefile was using. This makefile doesn't use ARCH
at all. Am I missing something about how this is used?
--
Darren
>
> Bruce
>
>>
>> do_install() {
>> - oe_runmake ARCH="${ARCH}" CC="${CC}" LD="${LD}" \
>> - prefix=${prefix} DESTDIR=${D} install
>> + oe_runmake CC="${CC}" AR="${AR}" prefix="${prefix}" DESTDIR="${D}" install
>> }
>> --
>> 1.7.1
>>
>> _______________________________________________
>> poky mailing list
>> poky@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/poky
>>
>
>
>
--
Darren Hart
Yocto Linux Kernel
next prev parent reply other threads:[~2010-12-30 22:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 17:57 [PATCH 0/3] tracing: trace-cmd fixes and new kernelshark recipe Darren Hart
2010-12-29 1:10 ` [PATCH 3/3] kernelshark: add ftrace gui viewer Darren Hart
2010-12-31 8:01 ` Saul Wold
2010-12-31 18:39 ` Darren Hart
2010-12-29 1:17 ` [PATCH 1/3] trace-cmd: fix cross-compilation Darren Hart
2010-12-30 21:02 ` Bruce Ashfield
2010-12-30 22:29 ` Darren Hart [this message]
2010-12-31 6:08 ` Bruce Ashfield
2010-12-31 7:41 ` Darren Hart
2010-12-31 13:12 ` Bruce Ashfield
2010-12-29 18:10 ` [PATCH 2/3] glib-2.0: fix g_once_init_enter compile failure Darren Hart
2010-12-31 8:05 ` Saul Wold
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=4D1D07E7.7010000@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=bruce.ashfield@gmail.com \
--cc=poky@yoctoproject.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