Re: [yocto] Difference b/w yocto kernels and normal linux.org kernels

[Nicholas Krause]

On March 10, 2015 12:33:14 AM EDT, Khem Raj  wrote:
>
>
>
>> On Mar 9, 2015, at 9:21 PM, Raghavendra Kakarla
> wrote:
>> 
>> Hi Paul Eggleton,
>> I have some doubt that is ,there is any difference between the linux
>kernels downloaded from the yocto and that are download from the
>kernel.org with same version number?
>> Can you please clarify the my doubt.
>> 
>
>Yocto project provides a reference kernel called linux-yocto hosted at
>https://git.yoctoproject.org/ search for "Yocto Linux Kernel”
>you will find the trees for various versions. The root of linux-yocto
>is linux-stable from kernel.org. Then there are device specific
>branches where the reference BSPs are using to build the reference
>kernel. So yes there are differences where linux-yocto might have back
>ported or forward ported patches to get a given machine working on a
>given kernel version. On top it has its own tooling to help you create
>kernel build infrastructure for new machine that you might be working
>on.
>there is extensive documentation and training on developing with
>linux-yocto as kernel. The branches eg.
>
>https://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.19/refs/heads
>
>However the OE infrastructure ( which yocto project uses for its build
>system), does not bind you to use linux-yocto, infact it provides base
>classes which help you to write your own recipes for kernel you would
>like to have. So you can very well you a different kernel.
>
>> Thanks and Regards,
>> Raghavendra Kakarla__
>> __
I would recommend looking into the reference docs for kernel building and 
programming under documents in the yocto project's main website for more 
information on how to build or custom your kernel using recipe files.  
Furthermore Raghavendra is right to my knowledge in how the yocto project is 
different from the mainline kernel trees,  however if you wish you can still 
use them. 
Nick
>> From: Raghavendra Kakarla
>> Sent: Tuesday, March 3, 2015 5:47 PM
>> To: Paul Eggleton
>> Cc: yocto@yoctoproject.org
>> Subject: RE: SDK generation issue
>> 
>> Hi Paul Eggleton,
>> 
>> Shall i get any API information in the generated SDK documents.
>> 
>> Regards,
>> Raghavendra.
>> 
>> From: Paul Eggleton 
>> Sent: Tuesday, March 3, 2015 5:40 PM
>> To: Raghavendra Kakarla
>> Cc: yocto@yoctoproject.org
>> Subject: Re: SDK generation issue
>> 
>> Assuming you built the SDK you had installed with "doc-pkgs" in
>> SDKIMAGE_FEATURES, they would be in the target sysroot i.e.
>> /sysroots//usr/share/doc/
>> 
>> On Tuesday 03 March 2015 11:55:22 Raghavendra Kakarla wrote:
>>> Hi Paul Eggleton,
>>> 
>>> Where can i get the documents generated by the yocto sdk.
>>> 
>>> Regards,
>>> Raghavendra.
>>> 
>>> From: Raghavendra Kakarla
>>> Sent: Tuesday, March 3, 2015 3:56 PM
>>> To: Paul Eggleton
>>> Cc: yocto@yoctoproject.org
>>> Subject: RE: SDK generation issue
>>> 
>>> Hi Paul Eggleton,
>>> 
>>> Thank you for your response.
>>> 
>>> Now my issue is resolved.
>>> 
>>> I have some doubts on yocto-sdk. Can you please clarify them.
>>> 
>>> When i Built SDK for YOCTO, I am getting a cross compilation tool
>chain.
>>> With which i am able to build the applications for my platform. I
>wanted to
>>> confirm, whether SDK means  a toolchain to build the applications or
>is
>>> there something more (such as documentation, libraries, etc
>generated for
>>> our platform)
>>> 
>>> Regards,
>>> Raghavendra.
>>> 
>>> From: Paul Eggleton 
>>> Sent: Tuesday, March 3, 2015 3:07 PM
>>> To: Raghavendra Kakarla
>>> Cc: yocto@yoctoproject.org
>>> Subject: Re: SDK generation issue
>>> 
>>> On Tuesday 03 March 2015 05:41:43 Raghavendra Kakarla wrote:
 I am generated the yocto SDK using the yocto sdk script "bitbake
 core-image-minimal -c populate_sdk" command. With this command I am
>able
 to
 generte the installation script file and .manifest file.
 
 I run the installation script file. After running installation
>script file
 it propts that following message:
 
 Extracting SDK...done
 Setting it up...done
 SDK has been successfully set up and is ready to be used.
 
 
 After this i run the ".
 /opt/poky/1.7/environment-setup-mips32rel-poky-linux" and echo
>$PATH i got
 the correct path.
 
 After this i built wrote a small example and try to build with the
>sdk
 generated toolchain by running following command:
 
 mipsel-poky-linux-gcc test.c
>>> 
>>> Use $CC instead of running the compiler directly so that you get the
>correct
>>> options.
>>> 
>>> Cheers,
>>> Paul
>>> 
>>> 
>>> --
>>> 
>>> Paul Eggleton
>>> Intel Open Source Technology Centre
>> 
>> --
>> 
>> Paul Eggleton
>> Intel Open Source Technology Centre
>> -- 
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
>-- 
>

[yocto] Intel BSP for Rangeley

[Albert K]

Dear all,

May I know which BSP to use for Intel Atom C2000 Rangeley?  I do not
see that Intel BSP has the mohon peak bsp.  I am trying out the Dizzy
1.7 branch.  Thanks.

Regards,
Albert.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Difference b/w yocto kernels and normal linux.org kernels

[Khem Raj]

> On Mar 9, 2015, at 9:21 PM, Raghavendra Kakarla 
>  wrote:
> 
> Hi Paul Eggleton,
> I have some doubt that is ,there is any difference between the linux kernels 
> downloaded from the yocto and that are download from the kernel.org with same 
> version number?
> Can you please clarify the my doubt.
> 

Yocto project provides a reference kernel called linux-yocto hosted at 
https://git.yoctoproject.org/ search for "Yocto Linux Kernel”
you will find the trees for various versions. The root of linux-yocto is 
linux-stable from kernel.org. Then there are device specific branches where the 
reference BSPs are using to build the reference kernel. So yes there are 
differences where linux-yocto might have back ported or forward ported patches 
to get a given machine working on a given kernel version. On top it has its own 
tooling to help you create kernel build infrastructure for new machine that you 
might be working on.
there is extensive documentation and training on developing with linux-yocto as 
kernel. The branches eg.

https://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.19/refs/heads

However the OE infrastructure ( which yocto project uses for its build system), 
does not bind you to use linux-yocto, infact it provides base classes which 
help you to write your own recipes for kernel you would like to have. So you 
can very well you a different kernel.

> Thanks and Regards,
> Raghavendra Kakarla__
> __
> From: Raghavendra Kakarla
> Sent: Tuesday, March 3, 2015 5:47 PM
> To: Paul Eggleton
> Cc: yocto@yoctoproject.org
> Subject: RE: SDK generation issue
> 
> Hi Paul Eggleton,
> 
> Shall i get any API information in the generated SDK documents.
> 
> Regards,
> Raghavendra.
> 
> From: Paul Eggleton 
> Sent: Tuesday, March 3, 2015 5:40 PM
> To: Raghavendra Kakarla
> Cc: yocto@yoctoproject.org
> Subject: Re: SDK generation issue
> 
> Assuming you built the SDK you had installed with "doc-pkgs" in
> SDKIMAGE_FEATURES, they would be in the target sysroot i.e.
> /sysroots//usr/share/doc/
> 
> On Tuesday 03 March 2015 11:55:22 Raghavendra Kakarla wrote:
>> Hi Paul Eggleton,
>> 
>> Where can i get the documents generated by the yocto sdk.
>> 
>> Regards,
>> Raghavendra.
>> 
>> From: Raghavendra Kakarla
>> Sent: Tuesday, March 3, 2015 3:56 PM
>> To: Paul Eggleton
>> Cc: yocto@yoctoproject.org
>> Subject: RE: SDK generation issue
>> 
>> Hi Paul Eggleton,
>> 
>> Thank you for your response.
>> 
>> Now my issue is resolved.
>> 
>> I have some doubts on yocto-sdk. Can you please clarify them.
>> 
>> When i Built SDK for YOCTO, I am getting a cross compilation tool chain.
>> With which i am able to build the applications for my platform. I wanted to
>> confirm, whether SDK means  a toolchain to build the applications or is
>> there something more (such as documentation, libraries, etc generated for
>> our platform)
>> 
>> Regards,
>> Raghavendra.
>> 
>> From: Paul Eggleton 
>> Sent: Tuesday, March 3, 2015 3:07 PM
>> To: Raghavendra Kakarla
>> Cc: yocto@yoctoproject.org
>> Subject: Re: SDK generation issue
>> 
>> On Tuesday 03 March 2015 05:41:43 Raghavendra Kakarla wrote:
>>> I am generated the yocto SDK using the yocto sdk script "bitbake
>>> core-image-minimal -c populate_sdk" command. With this command I am able
>>> to
>>> generte the installation script file and .manifest file.
>>> 
>>> I run the installation script file. After running installation script file
>>> it propts that following message:
>>> 
>>> Extracting SDK...done
>>> Setting it up...done
>>> SDK has been successfully set up and is ready to be used.
>>> 
>>> 
>>> After this i run the ".
>>> /opt/poky/1.7/environment-setup-mips32rel-poky-linux" and echo $PATH i got
>>> the correct path.
>>> 
>>> After this i built wrote a small example and try to build with the sdk
>>> generated toolchain by running following command:
>>> 
>>> mipsel-poky-linux-gcc test.c
>> 
>> Use $CC instead of running the compiler directly so that you get the correct
>> options.
>> 
>> Cheers,
>> Paul
>> 
>> 
>> --
>> 
>> Paul Eggleton
>> Intel Open Source Technology Centre
> 
> --
> 
> Paul Eggleton
> Intel Open Source Technology Centre
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Difference b/w yocto kernels and normal linux.org kernels

[Raghavendra Kakarla]

Hi Paul Eggleton,
I have some doubt that is ,there is any difference between the linux kernels 
downloaded from the yocto and that are download from the kernel.org with same 
version number?
Can you please clarify the my doubt.

Thanks and Regards,
Raghavendra Kakarla__
__
From: Raghavendra Kakarla
Sent: Tuesday, March 3, 2015 5:47 PM
To: Paul Eggleton
Cc: yocto@yoctoproject.org
Subject: RE: SDK generation issue

Hi Paul Eggleton,

Shall i get any API information in the generated SDK documents.

Regards,
Raghavendra.

From: Paul Eggleton 
Sent: Tuesday, March 3, 2015 5:40 PM
To: Raghavendra Kakarla
Cc: yocto@yoctoproject.org
Subject: Re: SDK generation issue

Assuming you built the SDK you had installed with "doc-pkgs" in
SDKIMAGE_FEATURES, they would be in the target sysroot i.e.
/sysroots//usr/share/doc/

On Tuesday 03 March 2015 11:55:22 Raghavendra Kakarla wrote:
> Hi Paul Eggleton,
>
> Where can i get the documents generated by the yocto sdk.
>
> Regards,
> Raghavendra.
> 
> From: Raghavendra Kakarla
> Sent: Tuesday, March 3, 2015 3:56 PM
> To: Paul Eggleton
> Cc: yocto@yoctoproject.org
> Subject: RE: SDK generation issue
>
> Hi Paul Eggleton,
>
> Thank you for your response.
>
> Now my issue is resolved.
>
> I have some doubts on yocto-sdk. Can you please clarify them.
>
> When i Built SDK for YOCTO, I am getting a cross compilation tool chain.
> With which i am able to build the applications for my platform. I wanted to
> confirm, whether SDK means  a toolchain to build the applications or is
> there something more (such as documentation, libraries, etc generated for
> our platform)
>
> Regards,
> Raghavendra.
>
> From: Paul Eggleton 
> Sent: Tuesday, March 3, 2015 3:07 PM
> To: Raghavendra Kakarla
> Cc: yocto@yoctoproject.org
> Subject: Re: SDK generation issue
>
> On Tuesday 03 March 2015 05:41:43 Raghavendra Kakarla wrote:
> > I am generated the yocto SDK using the yocto sdk script "bitbake
> > core-image-minimal -c populate_sdk" command. With this command I am able
> > to
> > generte the installation script file and .manifest file.
> >
> > I run the installation script file. After running installation script file
> > it propts that following message:
> >
> > Extracting SDK...done
> > Setting it up...done
> > SDK has been successfully set up and is ready to be used.
> >
> >
> > After this i run the ".
> > /opt/poky/1.7/environment-setup-mips32rel-poky-linux" and echo $PATH i got
> > the correct path.
> >
> > After this i built wrote a small example and try to build with the sdk
> > generated toolchain by running following command:
> >
> > mipsel-poky-linux-gcc test.c
>
> Use $CC instead of running the compiler directly so that you get the correct
> options.
>
> Cheers,
> Paul
>
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre

--

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Question: Yocto 1.7.1 kernel config defconfig will not be used?

[Bruce Ashfield]

On Mon, Mar 9, 2015 at 10:02 PM, Chung-Yeh Wang  wrote:
> Thanks for the information, Bruce.
>
> I removed all kernel configuration fragments from the bb file but difference
> between defconfig and .config is huge. I may do something wrong and will
> study more.

There's no guarantee that the defconfig passed will end up being a perfect
match to the .config. It depends on how up to date the defconfig is, how it
was generated, etc. The kernel configuration subsystem still processes
that default config and will select, enable and disable many options that are
not part of the input defconfig.

Cheers,

Bruce

>
> Chungyeh
>
> 2015-03-09 21:02 GMT+08:00 Bruce Ashfield :
>>
>> On 15-03-09 04:36 AM, Chung-Yeh Wang wrote:
>>>
>>> Hi List,
>>>
>>> I am using Yocto 1.7.1 to build linux-mainline. I found defconfig will
>>> not be used when using linux-yocto-custom.bb
>>>  (maybe also happens on linux-yocto).
>>>
>>> I think below is the reason,
>>>
>>> 1. kernel_do_configure is run after do_kernel_configme.The last line of
>>> do_kernel_configme is echo
>>> "CONFIG_LOCALVERSION="\"${LINUX_VERSION_EXTENSION}\" >> ${B}/.config
>>>
>>> 2. Following are the code to use defconfig,
>>
>>
>> The linux-yocto kernel_configme task takes the defconfig into account,
>> and uses it along with kernel configuration fragment processing.
>>
>> The skipping of the blind defconfig copy is completely intentional.
>>
>> Cheers,
>>
>> Bruce
>>
>>
>>>
>>> # Copy defconfig to .config if .config does not exist. This allows
>>> # recipes to manage the .config themselves in do_configure_prepend().
>>> if [ -f "${WORKDIR}/defconfig" ] && [ ! -f "${B}/.config" ]; then
>>> cp "${WORKDIR}/defconfig" "${B}/.config"
>>>
>>> The condition '[ ! -f "${B}/.config"]' will not be true, so
>>> recepe-kernel/linux/linux-yocto-custom/defconfig will nerver be used.
>>>
>>>
>>> To use defconfig is one of the method suggested in Kernel developer
>>> manual.
>>>
>>> Thanks and Regards,
>>> Chungyeh
>>>
>>>
>>
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Question: Yocto 1.7.1 kernel config defconfig will not be used?

[Chung-Yeh Wang]

Thanks for the information, Bruce.

I removed all kernel configuration fragments from the bb file but
difference between defconfig and .config is huge. I may do something wrong
and will study more.

Chungyeh

2015-03-09 21:02 GMT+08:00 Bruce Ashfield :

> On 15-03-09 04:36 AM, Chung-Yeh Wang wrote:
>
>> Hi List,
>>
>> I am using Yocto 1.7.1 to build linux-mainline. I found defconfig will
>> not be used when using linux-yocto-custom.bb
>>  (maybe also happens on linux-yocto).
>>
>> I think below is the reason,
>>
>> 1. kernel_do_configure is run after do_kernel_configme.The last line of
>> do_kernel_configme is echo
>> "CONFIG_LOCALVERSION="\"${LINUX_VERSION_EXTENSION}\" >> ${B}/.config
>>
>> 2. Following are the code to use defconfig,
>>
>
> The linux-yocto kernel_configme task takes the defconfig into account,
> and uses it along with kernel configuration fragment processing.
>
> The skipping of the blind defconfig copy is completely intentional.
>
> Cheers,
>
> Bruce
>
>
>
>> # Copy defconfig to .config if .config does not exist. This allows
>> # recipes to manage the .config themselves in do_configure_prepend().
>> if [ -f "${WORKDIR}/defconfig" ] && [ ! -f "${B}/.config" ]; then
>> cp "${WORKDIR}/defconfig" "${B}/.config"
>>
>> The condition '[ ! -f "${B}/.config"]' will not be true, so
>> recepe-kernel/linux/linux-yocto-custom/defconfig will nerver be used.
>>
>>
>> To use defconfig is one of the method suggested in Kernel developer
>> manual.
>>
>> Thanks and Regards,
>> Chungyeh
>>
>>
>>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Agenda: Yocto Project Technical Team Meeting - Tuesday, Mar. 10, 2015 8:00 AM US Pacific Time

[Jolley, Stephen K]

Tuesday, March 10, 2015 8:00 AM US Pacific Time



Agenda:



* Opens collection - 5 min (Stephen)

* Yocto Project status - 5 min (Stephen/team)

https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.8_Status

https://wiki.yoctoproject.org/wiki/Yocto_1.8_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_1.8_Features

* SWAT team rotation: Beth -> Saul

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

* Opens - 10 min

* Team Sharing - 10 min





We encourage people attending the meeting to logon the Yocto Project IRC 
chancel during the meeting (optional):



Yocto IRC: http://webchat.freenode.net/?channels=#yocto

IRC Tutorial: http://www.irchelp.org/irchelp/irctutorial.html



Conference Details:

Company:   WIND RIVER SYS

Ready-Access Number: 8007302996/9139049836

Access Code: 2705751


For International numbers see: 
https://www.yoctoproject.org/tools-resources/community/weekly-technical-call


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*   Work Telephone:  (503) 712-0534
*Cell:(208) 244-4460
* Email: stephen.k.jol...@intel.com

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 0/1] layer.conf: set high layer priority

[Andreas Müller]

On Mon, Mar 9, 2015 at 10:19 PM, Gary Thomas  wrote:
> On 2015-03-09 15:07, Andreas Müller wrote:
>>
>> On Mon, Mar 9, 2015 at 9:58 PM, Gary Thomas  wrote:
>>>
>>> On 2015-03-09 14:50, Andreas Müller wrote:


 On Sun, Mar 1, 2015 at 1:14 AM, Andrei Gherzan 
 wrote:
>
>
> Hello,
>
> On Fri, Feb 20, 2015 at 05:40:21PM +0100, Petter Mabäcker wrote:
>>
>>
>> The following changes since commit
>> d8bf60ce6c4a6c6371527c6df2e3243d2771c0cc:
>>
>> README: Github repo changed (2015-02-14 02:00:57 +0100)
>>
>> are available in the git repository at:
>>
>> git://git.yoctoproject.org/poky-contrib petmab/rpi_layer_prio
>>
>>
>> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=petmab/rpi_layer_prio
>>
>> Petter Mabäcker (1):
>> layer.conf: set high layer priority
>>
>>conf/layer.conf | 2 +-
>>1 file changed, 1 insertion(+), 1 deletion(-)
>
>
>
> Patch merged to master. Thanks Petter.
>
> --
> Andrei Gherzan
> --



 This one breaks xserver-xf86-config for me

 | Function failed: Fetcher failure for URL:
 'file://xorg.conf.d/10-evdev.conf'. Unable to fetch URL from any
 source.
>>>
>>>
>>>
>>> Are you trying to build for the RaspberryPi2?
>>>
>>> I [temporarily] fixed this by copying the missing files.  In
>>> the meta-raspberrypi layer, do
>>>% rsync -a
>>> recipes-graphics/xorg-xserver/xserver-xf86-config/raspberrypi{/,2}
>>
>> ctoproject.org/listinfo/yocto
>>
>>
>> I checked both (I have simply copied xserver-xf86-config files for
>> rpi2). Increasing Layer priority above 7 fails for me - have no idea
>> why. What should this patch solve/enhance?
>
>
> That command will let bitbake find the missing file:
>   recipes-graphics/xorg-xserver/xserver-xf86-config/raspberrypi2/
>   recipes-graphics/xorg-xserver/xserver-xf86-config/raspberrypi2/xorg.conf.d
>
> recipes-graphics/xorg-xserver/xserver-xf86-config/raspberrypi2/xorg.conf.d/10-evdev.conf
>   recipes-graphics/xorg-xserver/xserver-xf86-config/raspberrypi2/xorg.conf
>
> With this I was able to build for the rpi2.  Too bad Newark hasn't
> delivered mine yet (although it was promised 10 days ago...)
>
To avoid misunderstandings: The problem came up (for me) by increasing
layer priority and affects raspberrypi (I know files are missing for
raspberrypi2)

Andreas
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto Daisy 1.6.1 on CentOS 6.5

[Khem Raj]

> On Mar 9, 2015, at 2:05 PM, Vuille, Martin (Martin)  wrote:
> 
> Thanks, but that doesn’t quite answer my question.

well you could just download and install

http://downloads.yoctoproject.org/releases/yocto/yocto-1.6.1/buildtools/poky-eglibc-x86_64-buildtools-tarball-core2-64-buildtools-nativesdk-standalone-1.6.1.sh
>  
> The link you pointed to also claims that all required dependencies are
> available on CentOS 6.
>  
> But the package list at http://mirror.centos.org/centos/6/os/x86_64/Packages/ 
> 
> says otherwise. As I found, the version of Python on CentOS is 2.6.6
>  

that doc is obsolete as it says on top of the page.

> MV
>  
> From: Khem Raj [mailto:raj.k...@gmail.com] 
> Sent: March 09, 2015 4:47 PM
> To: Vuille, Martin (Martin)
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Yocto Daisy 1.6.1 on CentOS 6.5
>  
>  
> On Mar 9, 2015, at 1:36 PM, Vuille, Martin (Martin)  > wrote:
>  
> The Yocto 1.6.1 Project Reference Manual states that it is supported and 
> tested
> against CentOS release 6.5, but later states that Python 2.7.3 is required, 
> CentOS 6.5
> seems to have an older version of Python (2.6.6).
>  
> The build does not, in fact, work and complains that the version of Python is 
> too old.
>  
> Is the information about supported/tested distros out of date? Is there an 
> expectation
> that Python must be manually updated to the required version?
>  
>  
> https://wiki.yoctoproject.org/wiki/Poky/GettingStarted/Dependencies 
> 
> 
> 
>  
> MV
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org 
> https://lists.yoctoproject.org/listinfo/yocto 
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 0/1] layer.conf: set high layer priority

[Gary Thomas]

On 2015-03-09 15:07, Andreas Müller wrote:

On Mon, Mar 9, 2015 at 9:58 PM, Gary Thomas  wrote:

On 2015-03-09 14:50, Andreas Müller wrote:


On Sun, Mar 1, 2015 at 1:14 AM, Andrei Gherzan  wrote:


Hello,

On Fri, Feb 20, 2015 at 05:40:21PM +0100, Petter Mabäcker wrote:


The following changes since commit
d8bf60ce6c4a6c6371527c6df2e3243d2771c0cc:

README: Github repo changed (2015-02-14 02:00:57 +0100)

are available in the git repository at:

git://git.yoctoproject.org/poky-contrib petmab/rpi_layer_prio

http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=petmab/rpi_layer_prio

Petter Mabäcker (1):
layer.conf: set high layer priority

   conf/layer.conf | 2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)



Patch merged to master. Thanks Petter.

--
Andrei Gherzan
--



This one breaks xserver-xf86-config for me

| Function failed: Fetcher failure for URL:
'file://xorg.conf.d/10-evdev.conf'. Unable to fetch URL from any
source.



Are you trying to build for the RaspberryPi2?

I [temporarily] fixed this by copying the missing files.  In
the meta-raspberrypi layer, do
   % rsync -a
recipes-graphics/xorg-xserver/xserver-xf86-config/raspberrypi{/,2}

ctoproject.org/listinfo/yocto


I checked both (I have simply copied xserver-xf86-config files for
rpi2). Increasing Layer priority above 7 fails for me - have no idea
why. What should this patch solve/enhance?


That command will let bitbake find the missing file:
  recipes-graphics/xorg-xserver/xserver-xf86-config/raspberrypi2/
  recipes-graphics/xorg-xserver/xserver-xf86-config/raspberrypi2/xorg.conf.d
  
recipes-graphics/xorg-xserver/xserver-xf86-config/raspberrypi2/xorg.conf.d/10-evdev.conf
  recipes-graphics/xorg-xserver/xserver-xf86-config/raspberrypi2/xorg.conf

With this I was able to build for the rpi2.  Too bad Newark hasn't
delivered mine yet (although it was promised 10 days ago...)

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 0/1] layer.conf: set high layer priority

[Andreas Müller]

On Mon, Mar 9, 2015 at 9:58 PM, Gary Thomas  wrote:
> On 2015-03-09 14:50, Andreas Müller wrote:
>>
>> On Sun, Mar 1, 2015 at 1:14 AM, Andrei Gherzan  wrote:
>>>
>>> Hello,
>>>
>>> On Fri, Feb 20, 2015 at 05:40:21PM +0100, Petter Mabäcker wrote:

 The following changes since commit
 d8bf60ce6c4a6c6371527c6df2e3243d2771c0cc:

README: Github repo changed (2015-02-14 02:00:57 +0100)

 are available in the git repository at:

git://git.yoctoproject.org/poky-contrib petmab/rpi_layer_prio

 http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=petmab/rpi_layer_prio

 Petter Mabäcker (1):
layer.conf: set high layer priority

   conf/layer.conf | 2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>>
>>> Patch merged to master. Thanks Petter.
>>>
>>> --
>>> Andrei Gherzan
>>> --
>>
>>
>> This one breaks xserver-xf86-config for me
>>
>> | Function failed: Fetcher failure for URL:
>> 'file://xorg.conf.d/10-evdev.conf'. Unable to fetch URL from any
>> source.
>
>
> Are you trying to build for the RaspberryPi2?
>
> I [temporarily] fixed this by copying the missing files.  In
> the meta-raspberrypi layer, do
>   % rsync -a
> recipes-graphics/xorg-xserver/xserver-xf86-config/raspberrypi{/,2}
ctoproject.org/listinfo/yocto


I checked both (I have simply copied xserver-xf86-config files for
rpi2). Increasing Layer priority above 7 fails for me - have no idea
why. What should this patch solve/enhance?

Andreas
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto Daisy 1.6.1 on CentOS 6.5

[Vuille, Martin (Martin)]

Thanks, but that doesn't quite answer my question.

The link you pointed to also claims that all required dependencies are
available on CentOS 6.

But the package list at http://mirror.centos.org/centos/6/os/x86_64/Packages/
says otherwise. As I found, the version of Python on CentOS is 2.6.6

MV

From: Khem Raj [mailto:raj.k...@gmail.com]
Sent: March 09, 2015 4:47 PM
To: Vuille, Martin (Martin)
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Yocto Daisy 1.6.1 on CentOS 6.5


On Mar 9, 2015, at 1:36 PM, Vuille, Martin (Martin) 
mailto:vmar...@avaya.com>> wrote:

The Yocto 1.6.1 Project Reference Manual states that it is supported and tested
against CentOS release 6.5, but later states that Python 2.7.3 is required, 
CentOS 6.5
seems to have an older version of Python (2.6.6).

The build does not, in fact, work and complains that the version of Python is 
too old.

Is the information about supported/tested distros out of date? Is there an 
expectation
that Python must be manually updated to the required version?


https://wiki.yoctoproject.org/wiki/Poky/GettingStarted/Dependencies



MV
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 0/1] layer.conf: set high layer priority

[Gary Thomas]

On 2015-03-09 14:50, Andreas Müller wrote:

On Sun, Mar 1, 2015 at 1:14 AM, Andrei Gherzan  wrote:

Hello,

On Fri, Feb 20, 2015 at 05:40:21PM +0100, Petter Mabäcker wrote:

The following changes since commit d8bf60ce6c4a6c6371527c6df2e3243d2771c0cc:

   README: Github repo changed (2015-02-14 02:00:57 +0100)

are available in the git repository at:

   git://git.yoctoproject.org/poky-contrib petmab/rpi_layer_prio
   
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=petmab/rpi_layer_prio

Petter Mabäcker (1):
   layer.conf: set high layer priority

  conf/layer.conf | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)


Patch merged to master. Thanks Petter.

--
Andrei Gherzan
--


This one breaks xserver-xf86-config for me

| Function failed: Fetcher failure for URL:
'file://xorg.conf.d/10-evdev.conf'. Unable to fetch URL from any
source.


Are you trying to build for the RaspberryPi2?

I [temporarily] fixed this by copying the missing files.  In
the meta-raspberrypi layer, do
  % rsync -a recipes-graphics/xorg-xserver/xserver-xf86-config/raspberrypi{/,2}

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 0/1] layer.conf: set high layer priority

[Andrei Gherzan]

Hi Andreas,

On Mon, Mar 9, 2015 at 9:50 PM, Andreas Müller  wrote:

> On Sun, Mar 1, 2015 at 1:14 AM, Andrei Gherzan  wrote:
> > Hello,
> >
> > On Fri, Feb 20, 2015 at 05:40:21PM +0100, Petter Mabäcker wrote:
> >> The following changes since commit
> d8bf60ce6c4a6c6371527c6df2e3243d2771c0cc:
> >>
> >>   README: Github repo changed (2015-02-14 02:00:57 +0100)
> >>
> >> are available in the git repository at:
> >>
> >>   git://git.yoctoproject.org/poky-contrib petmab/rpi_layer_prio
> >>
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=petmab/rpi_layer_prio
> >>
> >> Petter Mabäcker (1):
> >>   layer.conf: set high layer priority
> >>
> >>  conf/layer.conf | 2 +-
> >>  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > Patch merged to master. Thanks Petter.
> >
> > --
> > Andrei Gherzan
> > --
>
> This one breaks xserver-xf86-config for me
>
> | Function failed: Fetcher failure for URL:
> 'file://xorg.conf.d/10-evdev.conf'. Unable to fetch URL from any
> source.
>
> Andreas
>

There is an issue with that conf file. This was introduced by the rpi2
support patches. Could you please fill in a redmine issue? Or maybe shoot
us a patch? J

Thanks!

-- 
*Andrei Gherzan*
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH 0/1] layer.conf: set high layer priority

[Andreas Müller]

On Sun, Mar 1, 2015 at 1:14 AM, Andrei Gherzan  wrote:
> Hello,
>
> On Fri, Feb 20, 2015 at 05:40:21PM +0100, Petter Mabäcker wrote:
>> The following changes since commit d8bf60ce6c4a6c6371527c6df2e3243d2771c0cc:
>>
>>   README: Github repo changed (2015-02-14 02:00:57 +0100)
>>
>> are available in the git repository at:
>>
>>   git://git.yoctoproject.org/poky-contrib petmab/rpi_layer_prio
>>   
>> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=petmab/rpi_layer_prio
>>
>> Petter Mabäcker (1):
>>   layer.conf: set high layer priority
>>
>>  conf/layer.conf | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> Patch merged to master. Thanks Petter.
>
> --
> Andrei Gherzan
> --

This one breaks xserver-xf86-config for me

| Function failed: Fetcher failure for URL:
'file://xorg.conf.d/10-evdev.conf'. Unable to fetch URL from any
source.

Andreas
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto Daisy 1.6.1 on CentOS 6.5

[Khem Raj]

> On Mar 9, 2015, at 1:36 PM, Vuille, Martin (Martin)  wrote:
> 
> The Yocto 1.6.1 Project Reference Manual states that it is supported and 
> tested
> against CentOS release 6.5, but later states that Python 2.7.3 is required, 
> CentOS 6.5
> seems to have an older version of Python (2.6.6).
>  
> The build does not, in fact, work and complains that the version of Python is 
> too old.
>  
> Is the information about supported/tested distros out of date? Is there an 
> expectation
> that Python must be manually updated to the required version?


https://wiki.yoctoproject.org/wiki/Poky/GettingStarted/Dependencies 


>  
> MV
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org 
> https://lists.yoctoproject.org/listinfo/yocto 
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Daisy 1.6.1 on CentOS 6.5

[Vuille, Martin (Martin)]

The Yocto 1.6.1 Project Reference Manual states that it is supported and tested
against CentOS release 6.5, but later states that Python 2.7.3 is required, 
CentOS 6.5
seems to have an older version of Python (2.6.6).

The build does not, in fact, work and complains that the version of Python is 
too old.

Is the information about supported/tested distros out of date? Is there an 
expectation
that Python must be manually updated to the required version?

MV
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] 2 images with single Bitbake recipe

[Nikolay Dimitrov]

Hi Gary,

On 03/09/2015 10:00 PM, Gary Thomas wrote:

On 2015-03-09 13:56, Nikolay Dimitrov wrote:

Hi Khem,

On 03/09/2015 09:31 PM, Khem Raj wrote:



On Mar 9, 2015, at 12:22 PM, Nikolay Dimitrov 
wrote:

Hi guys,

I need an advice for the following Yocto use case.

My system has to boot via minimal initramfs and then must use the full
rootfs. I can use 2 separate recipes to generate the 2 images (minimal
initramfs, complete rootfs), but I prefer to create all my build-
products via single bitbake command.

So, is it possible to build these 2 images with 1 recipe, and if "yes"
then how?




Look at how initramfs
http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-tasks-bundle_initramfs

and also meta/conf/local.conf.sample.extended


Thanks for answering. INITRAMFS_IMAGE_BUNDLE doesn't achieve what I
need, instead it merges the kernel image and initramfs in a single
file. What I need is, instead of invoking:

bitbake myproduct-image
bitbake myproduct-initrams-image

to invoke:

bitbake myproduct-combined-image

...which should create 2 separate images.


Just list them both on one command:
   bitbake myproduct-image myproduct-initrams-image

If you really want, you could write a recipe myproduct-combined-image
which includes
   DEPENDS = "myproduct-image myproduct-initrams-image"


Thanks. I'll try that and will share what worked for me.

Regards,
Nikolay
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] 2 images with single Bitbake recipe

[Nikolay Dimitrov]

Hi Ross,

On 03/09/2015 09:58 PM, Burton, Ross wrote:


On 9 March 2015 at 19:56, Nikolay Dimitrov mailto:picmas...@mail.bg>> wrote:

bitbake myproduct-combined-image

...which should create 2 separate images.


If typing both is too much bother, have a recipe that just has
DEPENDS=myproduct-image myproduct-initramfs-image and stub out all the
other tasks so it doesn't do anything.


Thanks for the idea, I'll try the add the image as a dependency.

Regards,
Nikolay

PS: It's not just a matter of typing. Other people need to use the
results of my work, and there are already lots of other manual steps
when a software needs to be built and deployed on the target, so adding
one more step doesn't improve our lives.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] 2 images with single Bitbake recipe

[Gary Thomas]

On 2015-03-09 13:56, Nikolay Dimitrov wrote:

Hi Khem,

On 03/09/2015 09:31 PM, Khem Raj wrote:



On Mar 9, 2015, at 12:22 PM, Nikolay Dimitrov  wrote:

Hi guys,

I need an advice for the following Yocto use case.

My system has to boot via minimal initramfs and then must use the full
rootfs. I can use 2 separate recipes to generate the 2 images (minimal
initramfs, complete rootfs), but I prefer to create all my build-
products via single bitbake command.

So, is it possible to build these 2 images with 1 recipe, and if "yes"
then how?




Look at how initramfs 
http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-tasks-bundle_initramfs
and also meta/conf/local.conf.sample.extended


Thanks for answering. INITRAMFS_IMAGE_BUNDLE doesn't achieve what I
need, instead it merges the kernel image and initramfs in a single
file. What I need is, instead of invoking:

bitbake myproduct-image
bitbake myproduct-initrams-image

to invoke:

bitbake myproduct-combined-image

...which should create 2 separate images.


Just list them both on one command:
  bitbake myproduct-image myproduct-initrams-image

If you really want, you could write a recipe myproduct-combined-image
which includes
  DEPENDS = "myproduct-image myproduct-initrams-image"

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] 2 images with single Bitbake recipe

[Burton, Ross]

On 9 March 2015 at 19:56, Nikolay Dimitrov  wrote:

> bitbake myproduct-combined-image
>
> ...which should create 2 separate images.
>

If typing both is too much bother, have a recipe that just has
DEPENDS=myproduct-image myproduct-initramfs-image and stub out all the
other tasks so it doesn't do anything.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Adding new library to yocto project

[Burton, Ross]

On 9 March 2015 at 18:30, Kfrell  wrote:

> ERROR: This autoconf log indicates errors, it looked at host include and/or
> library paths while determining system capabilities.
> Rerun configure task after fixing this.
> build/tmp/work/oe-linux-gnueabi/libxerces/3.1.1-r1/xerces-c-3.1.1'
> ERROR: Function failed: do_qa_configure
> ERROR: Logfile of failure stored
>
> in:build/tmp/work/oe-linux-gnueabi/libxerces/3.1.1-r1/temp/log.do_configure.21943
> ERROR: Task 541
>

Oh right, you never included this in your first mail.  As it says,
configure is failing.  There are no packages because nothing was compiled.

You'll need to have a look at the configure log output and configure script
and determine what paths it is using from the host when it shouldn't be,
and fix it.  Obviously xerces has a pretty bad build system as I seem to
recall this coming up once a year.  Someone should fix it *and send the
patch to Apache*.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] 2 images with single Bitbake recipe

[Nikolay Dimitrov]

Hi Khem,

On 03/09/2015 09:31 PM, Khem Raj wrote:



On Mar 9, 2015, at 12:22 PM, Nikolay Dimitrov  wrote:

Hi guys,

I need an advice for the following Yocto use case.

My system has to boot via minimal initramfs and then must use the full
rootfs. I can use 2 separate recipes to generate the 2 images (minimal
initramfs, complete rootfs), but I prefer to create all my build-
products via single bitbake command.

So, is it possible to build these 2 images with 1 recipe, and if "yes"
then how?




Look at how initramfs 
http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-tasks-bundle_initramfs
and also meta/conf/local.conf.sample.extended


Thanks for answering. INITRAMFS_IMAGE_BUNDLE doesn't achieve what I
need, instead it merges the kernel image and initramfs in a single
file. What I need is, instead of invoking:

bitbake myproduct-image
bitbake myproduct-initrams-image

to invoke:

bitbake myproduct-combined-image

...which should create 2 separate images.

Regards,
Nikolay
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] 2 images with single Bitbake recipe

[Khem Raj]

> On Mar 9, 2015, at 12:22 PM, Nikolay Dimitrov  wrote:
> 
> Hi guys,
> 
> I need an advice for the following Yocto use case.
> 
> My system has to boot via minimal initramfs and then must use the full
> rootfs. I can use 2 separate recipes to generate the 2 images (minimal
> initramfs, complete rootfs), but I prefer to create all my build-
> products via single bitbake command.
> 
> So, is it possible to build these 2 images with 1 recipe, and if "yes"
> then how?
> 


Look at how initramfs 
http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#ref-tasks-bundle_initramfs
and also meta/conf/local.conf.sample.extended

> Thanks in advance. Regards,
> Nikolay
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] 2 images with single Bitbake recipe

[Nikolay Dimitrov]

Hi guys,

I need an advice for the following Yocto use case.

My system has to boot via minimal initramfs and then must use the full
rootfs. I can use 2 separate recipes to generate the 2 images (minimal
initramfs, complete rootfs), but I prefer to create all my build-
products via single bitbake command.

So, is it possible to build these 2 images with 1 recipe, and if "yes"
then how?

Thanks in advance. Regards,
Nikolay
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] can there be a entire (sub)section on build parallelism?

[Robert P. J. Day]

  currently, in the YP ref manual, there's a section on "speeding up
the build":

http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#speeding-up-the-build

first part discussing the variables related to parallelism, but that
bit is not really complete.

  it discusses those three variables, but makes no mention of when one
might want to tweak one rather than the other, or how they're related.
it also doesn't mention the related PARALLEL_MAKEINST variable, or why
one might want to set

PARALLEL_MAKE = ""

in a particular recipe.

  what are the chances of expanding a section to explain exclusively
the variables related to parallelism, and when they should (and should
not) be tweaked?

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Adding new library to yocto project

[Kfrell]

Burton, Ross  writes:

> 
> 
> 
> On 9 March 2015 at 16:50, Kfrell
 wrote:I added
"libxerces" to my bb image by using IMAGE_INSTALL += " libxerces".
> Then, I try to build my image thru bitbake my-image-test and eveything is
> done correctly but libxerces returns some errors :
> 
> Packages containing libraries get renamed (by default) depending on the
library name, so just because you called the recipe "libxerces" doesn't mean
the resulting package is called that.
> 
> Have a look in tmp/work/[machine]/libxerces/deploy-* for the packages that
were actually generated, it's probably something like libxerces-c.
> 
> Ross
> 
> 

I had a look in this directory but under
tmp/work/[machine]/libxerces/3.1.1-r1 there is only three folders named
xerces-c-3.1.1, licence-destdir and temp. I checked under
tmp/work/deploy/ipk and nothing is actually created.

I have the following errors :

ERROR: This autoconf log indicates errors, it looked at host include and/or
library paths while determining system capabilities.
Rerun configure task after fixing this.
build/tmp/work/oe-linux-gnueabi/libxerces/3.1.1-r1/xerces-c-3.1.1'
ERROR: Function failed: do_qa_configure 
ERROR: Logfile of failure stored
in:build/tmp/work/oe-linux-gnueabi/libxerces/3.1.1-r1/temp/log.do_configure.21943
ERROR: Task 541



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Adding new library to yocto project

[Kfrell]

Kfrell  writes:

> 
> I am using Yocto and I just would like to integrate a new library 
> in my project.
> 
> I create a new recipe named "libxerces" which contains a file
> "libxerces-3.1.1.bb". The bb file is quite simple and it is based 
> on autotools : 
> 
> DESCRIPTION = "Xerces-c is a validating xml parser written in C++"
> HOMEPAGE = "http://xerces.apache.org/xerces-c/";
> PRIORITY = "optional"
> LICENSE = "MIT"
> LIC_FILES_CHKSUM = "file://LICENSE;md5=3b83ef96387f14655fc854ddc3c6bd57"
> 
> PR = "r1"
> 
> SRC_URI =
>
"http://mirror.serversupportforum.de/apache/xerces/c/3/sources/xerces-c-${PV}.tar.gz";
> 
> SRC_URI[md5sum] = "6a8ec45d83c8cfb1584c5a5345cb51ae"
> SRC_URI[sha256sum] =
> "a42785f71e0b91d5fd273831c87410ce60a73ccfdd207de1b805d26d44968736"
> 
> s="${WORKDIR}/xerces-c-${PV}"
> 
> inherit autotools pkgconfig
> 
> BBCLASSEXTEND += "native"
> 
> I added "libxerces" to my bb image by using IMAGE_INSTALL += " libxerces".
> Then, I try to build my image thru bitbake my-image-test and eveything is
> done correctly but libxerces returns some errors :
> 
> I just would like to create the .ipk package named libxerces in 
> which .so files should be available.
> 

I read almost all your example but nothing help me about my issues. 

The actuel returned errors are :

ERROR: This autoconf log indicates errors it looked at host include and/or
library paths while determining system capabilities. Rerun configure task
after fixing this.The path was
/build/tmp/work/oe-linux-gnueabi/libxerces/3.1.1-r1/xerces-c-3.1.1
ERROR: Function failed: do_qa_configure
ERROR: Logfile of failure stored in:
build/tmp/work/oe-linux-gnueabi/libxerces/3.1.1-r1/templog.do_configure.21943
ERROR: Task 541

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Adding new library to yocto project

[Burton, Ross]

On 9 March 2015 at 16:50, Kfrell  wrote:

> I added "libxerces" to my bb image by using IMAGE_INSTALL += " libxerces".
> Then, I try to build my image thru bitbake my-image-test and eveything is
> done correctly but libxerces returns some errors :
>

Packages containing libraries get renamed (by default) depending on the
library name, so just because you called the recipe "libxerces" doesn't
mean the resulting package is called that.

Have a look in tmp/work/[machine]/libxerces/deploy-* for the packages that
were actually generated, it's probably something like libxerces-c.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Adding new library to yocto project

[Alex J Lennon]

On 09/03/2015 17:50, Kfrell wrote:
> I am using Yocto and I just would like to integrate a new library 
> in my project.
>
> I create a new recipe named "libxerces" which contains a file
> "libxerces-3.1.1.bb". The bb file is quite simple and it is based 
> on autotools : 
>
> DESCRIPTION = "Xerces-c is a validating xml parser written in C++"
> HOMEPAGE = "http://xerces.apache.org/xerces-c/";
> PRIORITY = "optional"
> LICENSE = "MIT"
> LIC_FILES_CHKSUM = "file://LICENSE;md5=3b83ef96387f14655fc854ddc3c6bd57"
>
> PR = "r1"
>
> SRC_URI =
> "http://mirror.serversupportforum.de/apache/xerces/c/3/sources/xerces-c-${PV}.tar.gz";
>
> SRC_URI[md5sum] = "6a8ec45d83c8cfb1584c5a5345cb51ae"
> SRC_URI[sha256sum] =
> "a42785f71e0b91d5fd273831c87410ce60a73ccfdd207de1b805d26d44968736"
>
> s="${WORKDIR}/xerces-c-${PV}"
>
> inherit autotools pkgconfig
>
> BBCLASSEXTEND += "native"
>
> I added "libxerces" to my bb image by using IMAGE_INSTALL += " libxerces".
> Then, I try to build my image thru bitbake my-image-test and eveything is
> done correctly but libxerces returns some errors :
>
> I just would like to create the .ipk package named libxerces in 
> which .so files should be available.
>

This might possibly help. The example I created shows how to build a
package including an autotools generated library

https://wiki.yoctoproject.org/wiki/Building_your_own_recipes_from_first_principles

Regards, Alex

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Adding new library to yocto project

[Kfrell]

I am using Yocto and I just would like to integrate a new library 
in my project.

I create a new recipe named "libxerces" which contains a file
"libxerces-3.1.1.bb". The bb file is quite simple and it is based 
on autotools : 

DESCRIPTION = "Xerces-c is a validating xml parser written in C++"
HOMEPAGE = "http://xerces.apache.org/xerces-c/";
PRIORITY = "optional"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE;md5=3b83ef96387f14655fc854ddc3c6bd57"

PR = "r1"

SRC_URI =
"http://mirror.serversupportforum.de/apache/xerces/c/3/sources/xerces-c-${PV}.tar.gz";

SRC_URI[md5sum] = "6a8ec45d83c8cfb1584c5a5345cb51ae"
SRC_URI[sha256sum] =
"a42785f71e0b91d5fd273831c87410ce60a73ccfdd207de1b805d26d44968736"

s="${WORKDIR}/xerces-c-${PV}"

inherit autotools pkgconfig

BBCLASSEXTEND += "native"

I added "libxerces" to my bb image by using IMAGE_INSTALL += " libxerces".
Then, I try to build my image thru bitbake my-image-test and eveything is
done correctly but libxerces returns some errors :

I just would like to create the .ipk package named libxerces in 
which .so files should be available.

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Building local sources

[Koehler, Yannick (HP Networking)]

Hi,

 I need some help regarding this since I cannot find out how to achieve this.  
I have a git repo with a lot of code splitted in module, such as:

/.git
/module_a
/module_b

 Etc...

  I want to compile those modules using a bitbake recipe within yocto so I 
created the following tree structure:

/.git
/module_a
/module_b
/poky
/meta-modules
/recipes-
/module_a
module_a.bb
/recipes-
/module_b
module_b.bb

  So far so good, but now I am having issue with unpack/compile step, my 
modules are make-based (not autotools and not CMake).  So I used EXTRA_OEMAKE 
to get them to use the proper target toolchain.  Problem lies with the SRC_URI, 
my files from module_a gets copied into $WORKDIR and not into $S, as such the 
compile step failed.  I understand that SRC_URI is not really the proper usage 
in such situation, appears to be meant to retrieve external packages and some 
files here and there, mostly patches.  Even thought all my modules are within a 
git repo, I do not want to extract the full repo for each modules either.

  I am now looking into writing my own unpack function to move my code under S 
manually, but I was wondering if yocto had something to support this model and 
I simply missed it or if writing a custom unpack is the appropriate solution 
(likely I'll have to create a class so that all my modules use the same unpack 
behavior).

Yannick Koehler
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Openembedded/yocto bitbake with gcc 4.8.2 crashes at do_compile elfutils

[Everhard Ros]

Hello guys,

I'm trying to run bitbake to get a linux image on an altera Cyclone 5
devboard(SoCrates). The end goal is to get a linux image that has the OpenCV
library installed. I'm using the altera version of the yocto project.

Currently everything is running fairly well on ubuntu 12.04.
When I try to run this bitbake process on CentOS 7, I get the following
error:

Error: argument to 'sizeof' in 'snprintf' call is the same expression as the
destination; did you mean to provide an explicit length?
[-Werror=sizeof-pointer-memaccess]

cc1: all warnings being treated as errors

After some googling
 here
 and
 there, I kind of found the
'bug'.(new gcc has this new flag that older versions didn't have which
causes a warning and an error with -wall).

So now I'm looking for the place where flags are passed to the gcc compiler:
I tried doing this in the bitbake.conf file in the meta -layer;
TOOLCHAIN_OPTIONS, BUILD_CFLAGS and TARGET_CFLAGS are now empty.
In the

manual they mention these flags are being sent to the compiler.

I also checked out the elfutils and gcc folders in yocto/meta/devtools/, but
couldn't find anything relevant there (I used find/grep and the GUI,
searching for the flags mentioned)


Changing the flags in the bitbake.conf file didn't help; do you guys happen
to have any idea where the compiler flags are being set when bitbake
executes the do_compile task for elfutils?

Thank you in advance.

cheers!

 

P.S: This is a cross-post from this thread
  I made at
linuxquestions.org

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] avoid kernel building

[Maxin John]

Hi Parthiban,

On Mon, Mar 9, 2015 at 2:40 PM, Parthiban Kandasamy
 wrote:
> i am using beagle board-xm, for this board i don want to build kernel
> package. so how to exclude linux-yocto from build process. i tried following
> option
>
> PACKAGE_EXCLUDE = "linux-yocto" -> it was not effect,
> BBMASK .= "|.*linux-yocto" -> it was not effect,
>
> those statement not work, so what will be the correct option.

Please set this in local.conf file:
PREFERRED_PROVIDER_virtual/kernel = "linux-dummy"

and build again.

> thanks and regards,
> parthiban
>   +919790329795

Best Regards,
Maxin
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] avoid kernel building

[Parthiban Kandasamy]

i am using beagle board-xm, for this board i don want to build kernel
package. so how to exclude linux-yocto from build process. i tried
following option

PACKAGE_EXCLUDE = "linux-yocto" -> it was not effect,
BBMASK .= "|.*linux-yocto" -> it was not effect,

those statement not work, so what will be the correct option.

-- 
thanks and regards,
parthiban
  +919790329795
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Question: Yocto 1.7.1 kernel config defconfig will not be used?

[Bruce Ashfield]

On 15-03-09 04:36 AM, Chung-Yeh Wang wrote:

Hi List,

I am using Yocto 1.7.1 to build linux-mainline. I found defconfig will
not be used when using linux-yocto-custom.bb
 (maybe also happens on linux-yocto).

I think below is the reason,

1. kernel_do_configure is run after do_kernel_configme.The last line of
do_kernel_configme is echo
"CONFIG_LOCALVERSION="\"${LINUX_VERSION_EXTENSION}\" >> ${B}/.config

2. Following are the code to use defconfig,


The linux-yocto kernel_configme task takes the defconfig into account,
and uses it along with kernel configuration fragment processing.

The skipping of the blind defconfig copy is completely intentional.

Cheers,

Bruce



# Copy defconfig to .config if .config does not exist. This allows
# recipes to manage the .config themselves in do_configure_prepend().
if [ -f "${WORKDIR}/defconfig" ] && [ ! -f "${B}/.config" ]; then
cp "${WORKDIR}/defconfig" "${B}/.config"

The condition '[ ! -f "${B}/.config"]' will not be true, so
recepe-kernel/linux/linux-yocto-custom/defconfig will nerver be used.


To use defconfig is one of the method suggested in Kernel developer manual.

Thanks and Regards,
Chungyeh




--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-mono] Update to 3.12.1 to address SKIP TLS / FREAK vulnerabilities

[Alex J Lennon]

Hi,

meta-mono master has been updated to build the latest Mono 3.12.1
release which addresses SKIP TLS / FREAK vulnerabilities in all prior
Mono versions >= 3.4.0.

For further details see:

http://www.mono-project.com/news/2015/03/07/mono-tls-vulnerability/

Basic testing has been performed on an i.MX6 platform running helloworld
(console) and helloworldworld (matchbox ui)

Regards,

Alex
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [Recipe reporting system] Upgradable recipe name list

[recipe-report]

This mail was sent out by Recipe reporting system.

This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade this time, they can fill in
RECIPE_NO_UPDATE_REASON_pn-"xxx" in upstream_tracking files to ignore this
recipe remainder until newer upstream version was detected.

Example:
RECIPE_NO_UPDATE_REASON_pn-"xxx" = "Not upgrade to 2.0 is unstable"

You can check the detail information at:

http://packages.yoctoproject.org/

Package   Version  Upstream version  Maintainer   
NoUpgradeReason
  ---    ---  
--
nfs-utils 1.3.11.3.2 Alejandro Hernandez
midori0.5.80.5.9 Alejandro Hernandez
python-smmap  0.8.20.9.0 Alejandro Hernandez
gnome-icon-theme  2.31.0   3.12.0Alejandro Hernandez  
waiting for the sato gtk3 port
jpeg  8d   9aAníbal Limón 
webkit-gtk 1.8.3 doesn't wo...
apt   0.9.9.4  1.0.9.7   Aníbal Limón
dpkg  1.17.21  1.17.24   Aníbal Limón
sqlite3   3.8.7.4  3.8.8.3.  Aníbal Limón
screen4.0.34.2.1 Aníbal Limón
nettle2.7.13.0   Armin Kuster 
3.0.0 breaks gnutls, api ch...
linux-libc-headers3.19 3.19.1Bruce Ashfield
resolvconf1.76 1.76.1Chen Qi
console-tools 0.3.21999.03.02Chen Qi
util-linux2.25.2   2.26  Chen Qi
kmod  19+gitX  20+gitAUTOINC+037...  Chen Qi
curl  7.40.0   7.41.0Chen Qi
sudo  1.8.11p2 1.8.12Chen Qi
sysstat   11.0.2   11.1.3Chen Qi
xz5.2.05.2.1 Chen Qi
dbus-glib 0.1020.104 Chong Lu
dbus-test 1.8.10   1.9.14Chong Lu
dbus  1.8.10   1.9.14Chong Lu 
D-BUS 1.9.x is the developm...
bison 2.7.13.0.4 Chong Lu
strace4.9  4.10  Chong Lu
bluez44.1015.28  Cristian Iorga   
BlueZ 5.x is not backward-c...
gst-plugin-bluetooth  4.1015.28  Cristian Iorga
iproute2  3.17.0   3.19.0Cristian Iorga
alsa-lib  1.0.28   1.0.29Cristian Iorga
alsa-utils-alsaconf   1.0.28   1.0.29Cristian Iorga
alsa-utils1.0.28   1.0.29Cristian Iorga
gst-ffmpeg0.10.13  0.11.2Cristian Iorga
gst-fluendo-mp3   0.10.31  0.10.32   Cristian Iorga
gst-plugins-bad   0.10.23  1.4.5 Cristian Iorga   
not compatible with gst-flu...
gst-plugins-base  0.10.36  1.4.5 Cristian Iorga   
not compatible with gst-flu...
gst-plugins-good  0.10.31  1.4.5 Cristian Iorga   
not compatible with gst-flu...
gst-plugins-ugly  0.10.19  1.4.5 Cristian Iorga
gstreamer 0.10.36  1.4.5 Cristian Iorga   
not compatible with gst-fl...
libvorbis 1.3.41.3.5 Cristian Iorga
libatomics-ops7.2  7.4.0 Cristian Iorga
speex 1.2rc1   1.2rc2Cristian Iorga
db6.0.30   6.1.23.NC Cristian Iorga   
API compatibility issue
libical   1.0.01.0.1 Cristian Iorga
quota 4.01 4.02  Cristian Iorga
harfbuzz  0.9.38   0.9.39Cristian Iorga
hwlatdetect   0.89 0.91  Darren Hart
rt-tests  0.89 0.91  Darren Hart
dhcp  4.3.14.3.2 Hongxu Jia
socat 1.7.2.4  1.7.3.0   Hongxu Jia
distcc3.1  3.2rc1Hongxu Jia
qmmp  0.7.70.8.3 Hongxu Jia
patch 2.7.12.7.5 Hongxu Jia
perl  5.20.0   5.21.9Hongxu Jia
createrepo0.4.11   0.10.3Hongxu Jia   
Versions after 0.9.* use YU...
bash  4.3  4.3.30Hongxu Jia   
The latest version in yocto...
groff 1.22.2   1.22.3Hongxu Jia 

[yocto] Question: Yocto 1.7.1 kernel config defconfig will not be used?

[Chung-Yeh Wang]

Hi List,

I am using Yocto 1.7.1 to build linux-mainline. I found defconfig will not
be used when using linux-yocto-custom.bb (maybe also happens on
linux-yocto).

I think below is the reason,

1. kernel_do_configure is run after do_kernel_configme.The last line of
do_kernel_configme is echo
"CONFIG_LOCALVERSION="\"${LINUX_VERSION_EXTENSION}\" >> ${B}/.config

2. Following are the code to use defconfig,

# Copy defconfig to .config if .config does not exist. This allows
# recipes to manage the .config themselves in do_configure_prepend().
if [ -f "${WORKDIR}/defconfig" ] && [ ! -f "${B}/.config" ]; then
cp "${WORKDIR}/defconfig" "${B}/.config"

The condition '[ ! -f "${B}/.config"]' will not be true, so
recepe-kernel/linux/linux-yocto-custom/defconfig will nerver be used.


To use defconfig is one of the method suggested in Kernel developer manual.

Thanks and Regards,
Chungyeh
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto