From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Bodke, Kishore K" <kishore.k.bodke@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: compiling package with bitbake with CROSS_COMPILE flag
Date: Thu, 06 Sep 2012 10:56:31 +0100 [thread overview]
Message-ID: <1751966.om2roK65Ws@helios> (raw)
In-Reply-To: <D956029D25CF204F948EA0FB515E1EE20AD6186E@ORSMSX105.amr.corp.intel.com>
On Monday 27 August 2012 18:10:12 Bodke, Kishore K wrote:
> I hope I am asking this question to the right mailing list, since it is
> related to meta modules classes.
>
> I have a package trying to compile using bitbake.
>
> When you inherit module, I think CROSS_COMPILE option is enabled by
> module-base.bbclass.
>
> I get below error because of this CROSS_COMPILE flag.
>
> error: inlining failed in call to always_inline 'icp_adf_pollQueue':
> function body not available
>
> I disabled the flag in my recipe by export CROSS_COMPILE="".
> Then it compiled fine.
>
> My question is
> what this CROSS_COMPILE flag does when bitbake runs? Does it set any extra
> compiler flags, which is not accepted by my package I am building using
> bitbake? How do you avoid this inlining issue when CROSS_COMPILE flag is
> enabled?
CROSS_COMPILE is set in order for the kernel module makefiles to be able to
determine the correct prefix for the compilation tools. If it isn't set I think
you would potentially be using the wrong compiler and tools for the target
platform.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2012-09-06 10:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 18:10 compiling package with bitbake with CROSS_COMPILE flag Bodke, Kishore K
2012-09-06 9:56 ` Paul Eggleton [this message]
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=1751966.om2roK65Ws@helios \
--to=paul.eggleton@linux.intel.com \
--cc=kishore.k.bodke@intel.com \
--cc=openembedded-core@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.