Re: [yocto] GCC plugin missing

2014-12-30 Thread akuster808
Atul. I believe you need to add EXTRA_OECONF += "--enable-plugin" in a bbappend file for the gcc you need the support it. That wont solve your problem. The kernel Makefile is hard coded to use your 'HOST' gcc. It is trying to build 'HOST' tools. Look at the kernel Makefile. You might need

[yocto] GCC plugin missing

2014-12-30 Thread atulkumar singh
Hi All, I have built the toolchin using meta-toolchain. But while building the kernel using the same toolchain,we are getting error message as below:- Makefile:635: *** Your gcc installation does not support plugins. If the necessary headers for plugin support are missing, they should be instal

[yocto] Fwd: RE: GCC plugin missing

2014-12-30 Thread atulkumar singh
Hi All, I have built the toolchin using meta-toolchain. But while building the kernel using the same toolchain,we are getting error message as below:- Makefile:635: *** Your gcc installation does not support plugins. If the necessary headers for plugin support are missing, they should be ins

Re: [yocto] more BSP Guide pedantry involving customizing a recipe

2014-12-30 Thread Gary Thomas
On 2014-12-30 15:48, Gary Thomas wrote: On 2014-12-30 12:31, Robert P. J. Day wrote: (you can tell i'm bored and want to get back up to speed on stuff ...) section 1.4 in BSP Guide, "Customizing a Recipe for a BSP", appears to discuss a new layer, "meta-xyz", then suggests the new "inter

Re: [yocto] more BSP Guide pedantry involving customizing a recipe

2014-12-30 Thread Gary Thomas
On 2014-12-30 12:31, Robert P. J. Day wrote: (you can tell i'm bored and want to get back up to speed on stuff ...) section 1.4 in BSP Guide, "Customizing a Recipe for a BSP", appears to discuss a new layer, "meta-xyz", then suggests the new "interfaces" file for this machine needs to go

[yocto] [PATCH] yocto-docs: Minor, aesthetic touchups to BSP Guide.

2014-12-30 Thread Robert P. J. Day
Signed-off-by: Robert P. J. Day --- diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml index d485023..2f5a2cc 100644 --- a/documentation/bsp-guide/bsp.xml +++ b/documentation/bsp-guide/bsp.xml @@ -35,12 +35,12 @@ Collectively, you can think of the ba

Re: [yocto] libm implementation issue

2014-12-30 Thread Benjamin Esquivel
On Tue, 2014-12-30 at 20:09 +1030, peterengcomau...@adam.com.au wrote: > > I have some software that uses specific mathematical functions. When I > attempt to compile them with the Yocto cross-compile tools, the > functions are not recognised. E.g. 'pow' in > According to website https://wiki.yoc

[yocto] more BSP Guide pedantry involving customizing a recipe

2014-12-30 Thread Robert P. J. Day
(you can tell i'm bored and want to get back up to speed on stuff ...) section 1.4 in BSP Guide, "Customizing a Recipe for a BSP", appears to discuss a new layer, "meta-xyz", then suggests the new "interfaces" file for this machine needs to go at the location: meta-xyz/recipes-core/init-ifup

Re: [yocto] is it not a *requirement* that layers start with "meta-"?

2014-12-30 Thread Robert P. J. Day
On Wed, 31 Dec 2014, peterengcomau...@adam.com.au wrote: > If you use the yocto scripts for setting up a new layer, it > automatically prepends 'meta-'. That may be why there is no > requirement but that still doesn't address that (from memory) some OE scripts/utils seem to *require* layers sta

[yocto] BSP guide refers to meta-fri2 as example for binary/ data, it has none

2014-12-30 Thread Robert P. J. Day
in sec 1.3.1 of BSP guide, there is an explanation of the README.sources file. first, the text suggests that file is mandatory: "You must include a README.sources in the meta-bsp_name directory." however, as i read it, it's really only necessary when a layer provides some binary content in the

[yocto] BSP Guide needs to be updated considerably given changes to meta-crownbay

2014-12-30 Thread Robert P. J. Day
i suspect people are already working on this, but the BSP Guide needs updating given that it uses the meta-crownbay layer as a working example, and there have been substantial changes to that layer that no longer match the guide. rday -- ==

Re: [yocto] is it not a *requirement* that layers start with "meta-"?

2014-12-30 Thread peterengcomau001
If you use the yocto scripts for setting up a new layer, it automatically prepends 'meta-'. That may be why there is no requirement.Lachlan - Original Message - From: "Robert P. J. Day" To:"Yocto discussion list" Cc: Sent:Tue, 30 Dec 2014 09:20:55 -0500 (EST) Subject:[yocto] is it not a

[yocto] is it not a *requirement* that layers start with "meta-"?

2014-12-30 Thread Robert P. J. Day
just proofing the BSP Guide and i read again that starting a layer name with "meta-" is not an actual requirement, it's just standard practice. but is there no code/script anywhere that requires that prefix to process the layer properly? i'm pretty sure i've run across YP utilities that check

[yocto] [PATCH] yocto-docs: Tidy up documentation Makefile.

2014-12-30 Thread Robert P. J. Day
Some aesthetic fixes to yocto-docs Makefile, none of which should affect the documentation builds: * small number of typos fixed * documentation corrected in a couple places * for most part, reduce line lengths to 80 for printing Signed-off-by: Robert P. J. Day --- was going to fix ju

[yocto] libm implementation issue

2014-12-30 Thread peterengcomau001
I have some software that uses specific mathematical functions. When I attempt to compile them with the Yocto cross-compile tools, the functions are not recognised. E.g. 'pow' in According to website https://wiki.yoctoproject.org/wiki/Minimal_Image, not all eglibc features are installed as stand