All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Chris Larson <clarson@kergoth.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: Library paths for Makefile based recipes
Date: Thu, 30 Dec 2010 08:33:26 -0800	[thread overview]
Message-ID: <4D1CB456.5030402@linux.intel.com> (raw)
In-Reply-To: <AANLkTikv=8nUngfb5we7U5xevQ55hD_iP9KMKW07d8QF@mail.gmail.com>

On 12/30/2010 06:11 AM, Chris Larson wrote:
> On Thu, Dec 30, 2010 at 4:21 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org>  wrote:
>> On Tue, 2010-12-28 at 16:58 -0800, Darren Hart wrote:
>>> Turns out the project Makefile is doing this:
>>>
>>> CC = $(CROSS_COMPILE)gcc
>>> AR = $(CROSS_COMPILE)ar
>>>
>>> Removing those lines from the Makefile allows the project to build.
>>
>> You could also set CROSS_COMPILE to the right value (TARGET_PREFIX?) and
>> things should work. This looks very similar to how we cross compile the
>> kernel.
>
> I'm not familiar with this particular project, but unless it's bare
> metal or nearly so like a kernel or bootloader, that's likely not a
> good idea, since it won't end up obeying our TARGET_CC_ARCH.  An
> alternative to setting CC/AR in EXTRA_OEMAKE or removing those lines
> from the makefile would be to set them there, but using ?=.  This
> would let the versions in the environment be used in preference to
> those.

I'll ask Steven if he'd accept such a change.


-- 
Darren Hart
Yocto Linux Kernel


  reply	other threads:[~2010-12-30 16:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-29  0:29 Library paths for Makefile based recipes Darren Hart
2010-12-29  0:41 ` Chris Larson
2010-12-29  0:58   ` Darren Hart
2010-12-30 11:21     ` Richard Purdie
2010-12-30 14:11       ` Chris Larson
2010-12-30 16:33         ` Darren Hart [this message]
2010-12-30 16:32       ` Darren Hart
2010-12-29  0:43 ` Tian, Kevin
2010-12-29  0:54   ` Darren Hart
2010-12-30 21:08     ` Bruce Ashfield
2010-12-30 21:10       ` Bruce Ashfield
2010-12-30 22:31         ` Darren Hart
2010-12-31  6:11           ` Bruce Ashfield
2010-12-29  9:18 ` Koen Kooi
2010-12-29 16:19   ` Darren Hart
2010-12-30 10:24     ` 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=4D1CB456.5030402@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=clarson@kergoth.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.