All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 2/2] kernel.bbclass: pass AR, NM and OBJCOPY to make
Date: Mon, 16 May 2011 14:14:49 +0200	[thread overview]
Message-ID: <4DD11539.5070701@opendreambox.org> (raw)
In-Reply-To: <1305546243.2429.1.camel@phil-desktop>

On 05/16/2011 01:44 PM, Phil Blundell wrote:
> I'm mildly curious as to what Montavista can have done that requires a
> custom version of ar.  But the patch looks fine to me anyway.

I don't know whether this change came from Montavista or from the vendor
supplying the kernel sources. Anyway, someone changed CROSS_COMPILE to
override the environment, thus using a prefix different from the
toolchain built by OE.

CROSS_COMPILE   = $(shell if [ -f .mvl_cross_compile ]; then \
                                  cat .mvl_cross_compile; \
                          fi)

With the patch applied, the variable CROSS_COMPILE isn't used anymore,
because all cross-tools are specified on the command line in the same
manner.

Another way to solve this problem could have been to set CROSS_COMPILE
on the command line instead of in the environment. I haven't tried that.
I could create an updated patch if this was preferred.

Regards,
Andreas



  reply	other threads:[~2011-05-16 12:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-15  0:03 [PATCH 1/2] kernel.bbclass: pass KERNEL_VERSION through legitimize_package_name Andreas Oberritter
2011-04-15  0:03 ` [PATCH 2/2] kernel.bbclass: pass AR, NM and OBJCOPY to make Andreas Oberritter
2011-05-16 11:40   ` Andreas Oberritter
2011-05-16 11:44     ` Phil Blundell
2011-05-16 12:14       ` Andreas Oberritter [this message]
2011-05-16 11:40 ` [PATCH 1/2] kernel.bbclass: pass KERNEL_VERSION through legitimize_package_name Andreas Oberritter
2011-05-16 11:45   ` Phil Blundell

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=4DD11539.5070701@opendreambox.org \
    --to=obi@opendreambox.org \
    --cc=openembedded-devel@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 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.