Re: [yocto] Issue with yocto ADT
Hi Todor, For not working scenario there is no makefile created. For working scenario using build directory sysroot makefiles are created. I attaching the makefile for working scenario. Regards, Raghavendra K. From: Minchev, Todor todor.minc...@intel.com Sent: Tuesday, May 19, 2015 12:13 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT On Mon, 2015-05-18 at 16:55 +, Raghavendra Kakarla wrote: Hi Todor, I created four more new projects. For all the projects I gives error like this only. Is the error message the same as the original one you posted about a missing make `all` target? Can send those projects make files? Please share both your working and non-working Makefiles. But when I give the sysroot path in eclipse to the poky/build/tmp/sysroot/machine it worked properly. When we give the extracted sysroot it gives problem. Regards, Raghavendra. From: Minchev, Todor [todor.minc...@intel.com] Sent: Monday, May 18, 2015 9:51 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT Hello Raghavendra, On Mon, 2015-05-18 at 05:07 +, Raghavendra Kakarla wrote: Hi Todor, Could you please let me know the cause for the issue. Please pastebin your Makefile and share the pastebin link. Seem like your project is corrupt and the Makefile is not generated correctly. Have you tried to delete the project and create a new one? Thanks in advance. Regards, Raghavendra K. From: Raghavendra Kakarla Sent: Friday, May 15, 2015 5:31 PM To: Minchev, Todor Cc: yocto@yoctoproject.org Subject: RE: [yocto] Issue with yocto ADT Hi Todor, It is provided by the Yocto eclipse plugin itself. Regards, Raghavendra. From: Minchev, Todor todor.minc...@intel.com Sent: Friday, May 15, 2015 5:27 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT On Fri, 2015-05-15 at 11:33 +, Raghavendra Kakarla wrote: Hi Todor, It is an autotool based example. It is not generated makefile itself. Is it an example you created yourself or is it the autotools C Hello World template provided by the Yocto Eclipse Plug-in. I attached the makefile.in and makefile.am file to the paste bin. Could you please paste the Makefile and share the pastebin link? Thanks, Raghavendra. From: Minchev, Todor todor.minc...@intel.com Sent: Friday, May 15, 2015 4:41 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT Hello Raghavendra, Could you please pastebin the makefile from your project? http://pastebin.com/ Cheers, Todor On Fri, 2015-05-15 at 10:47 +, Raghavendra Kakarla wrote: Hi Todor, Thank you for your reply. By default we have the setting like this only. But we got the error. Thanks, Raghavendra. From: Minchev, Todor todor.minc...@intel.com Sent: Friday, May 15, 2015 4:05 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT Hello Raghavendra, Please try the following: Right click on your project - Properties - C/C++ Build - Select the 'Behavior' tab - untick 'Build on resource save' and remove 'all' from the 'Build' field Cheers, Todor On Fri, 2015-05-15 at 09:32 +, Raghavendra Kakarla wrote: Hi All, I have problem with the ADT while i am building the autotool example helloword project which is given in the yocto ADT autotool project. Could you please help me in resolving this issue. I followed the following steps for installing the adt in my development PC: I built the toolchain using the following command: $cd ~/poky $source ./oe-init-build-env $bitbake meta-ide-support Extract the root file system by using the following commands: $cd ~ $source ~/poky/build/tmp/environment-setup-mips32r2el-poky-linux $runqemu-extract-sdk \ ~/poky/build/tmp/deploy/images/arqlyn/ core-image-minimal-dhruwa_ioe-20150511102759.rootfs.tar.bz2\ $HOME/arqlyn I followed the command given in the yocto project dev-manual for installing eclipse and adding yocto plugin to eclipse. I Gave the following data to the eclipse for configuring the cross-compiler options: 1. I select the Build System Derived Toolchain 2.point the toolchain path to home/testuser/poky/build 3.gave sysroot path to
Re: [yocto] Issue with yocto ADT
On Tue, 2015-05-19 at 07:07 +, Raghavendra Kakarla wrote: Hi Todor, For not working scenario there is no makefile created. For working scenario using build directory sysroot makefiles are created. So configure fails to create your Makefile. You probably see something like this in your config.log: configure: error: C compiler cannot create executables configure: error: C compiler cannot create executables See `config.log' for more details Please have a look at this thread, it explains how to resolve this problem: https://lists.yoctoproject.org/pipermail/yocto/2015-March/024089.html Cheers, Todor I attaching the makefile for working scenario. Regards, Raghavendra K. From: Minchev, Todor todor.minc...@intel.com Sent: Tuesday, May 19, 2015 12:13 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT On Mon, 2015-05-18 at 16:55 +, Raghavendra Kakarla wrote: Hi Todor, I created four more new projects. For all the projects I gives error like this only. Is the error message the same as the original one you posted about a missing make `all` target? Can send those projects make files? Please share both your working and non-working Makefiles. But when I give the sysroot path in eclipse to the poky/build/tmp/sysroot/machine it worked properly. When we give the extracted sysroot it gives problem. Regards, Raghavendra. From: Minchev, Todor [todor.minc...@intel.com] Sent: Monday, May 18, 2015 9:51 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT Hello Raghavendra, On Mon, 2015-05-18 at 05:07 +, Raghavendra Kakarla wrote: Hi Todor, Could you please let me know the cause for the issue. Please pastebin your Makefile and share the pastebin link. Seem like your project is corrupt and the Makefile is not generated correctly. Have you tried to delete the project and create a new one? Thanks in advance. Regards, Raghavendra K. From: Raghavendra Kakarla Sent: Friday, May 15, 2015 5:31 PM To: Minchev, Todor Cc: yocto@yoctoproject.org Subject: RE: [yocto] Issue with yocto ADT Hi Todor, It is provided by the Yocto eclipse plugin itself. Regards, Raghavendra. From: Minchev, Todor todor.minc...@intel.com Sent: Friday, May 15, 2015 5:27 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT On Fri, 2015-05-15 at 11:33 +, Raghavendra Kakarla wrote: Hi Todor, It is an autotool based example. It is not generated makefile itself. Is it an example you created yourself or is it the autotools C Hello World template provided by the Yocto Eclipse Plug-in. I attached the makefile.in and makefile.am file to the paste bin. Could you please paste the Makefile and share the pastebin link? Thanks, Raghavendra. From: Minchev, Todor todor.minc...@intel.com Sent: Friday, May 15, 2015 4:41 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT Hello Raghavendra, Could you please pastebin the makefile from your project? http://pastebin.com/ Cheers, Todor On Fri, 2015-05-15 at 10:47 +, Raghavendra Kakarla wrote: Hi Todor, Thank you for your reply. By default we have the setting like this only. But we got the error. Thanks, Raghavendra. From: Minchev, Todor todor.minc...@intel.com Sent: Friday, May 15, 2015 4:05 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT Hello Raghavendra, Please try the following: Right click on your project - Properties - C/C++ Build - Select the 'Behavior' tab - untick 'Build on resource save' and remove 'all' from the 'Build' field Cheers, Todor On Fri, 2015-05-15 at 09:32 +, Raghavendra Kakarla wrote: Hi All, I have problem with the ADT while i am building the autotool example helloword project which is given in the yocto ADT autotool project. Could you please help me in resolving this issue. I followed the following steps for installing the adt in my development PC: I built the toolchain using the following command: $cd ~/poky $source ./oe-init-build-env $bitbake meta-ide-support Extract the root file system by using the following commands:
Re: [yocto] Issue with yocto ADT
On Mon, 2015-05-18 at 16:55 +, Raghavendra Kakarla wrote: Hi Todor, I created four more new projects. For all the projects I gives error like this only. Is the error message the same as the original one you posted about a missing make `all` target? Can send those projects make files? Please share both your working and non-working Makefiles. But when I give the sysroot path in eclipse to the poky/build/tmp/sysroot/machine it worked properly. When we give the extracted sysroot it gives problem. Regards, Raghavendra. From: Minchev, Todor [todor.minc...@intel.com] Sent: Monday, May 18, 2015 9:51 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT Hello Raghavendra, On Mon, 2015-05-18 at 05:07 +, Raghavendra Kakarla wrote: Hi Todor, Could you please let me know the cause for the issue. Please pastebin your Makefile and share the pastebin link. Seem like your project is corrupt and the Makefile is not generated correctly. Have you tried to delete the project and create a new one? Thanks in advance. Regards, Raghavendra K. From: Raghavendra Kakarla Sent: Friday, May 15, 2015 5:31 PM To: Minchev, Todor Cc: yocto@yoctoproject.org Subject: RE: [yocto] Issue with yocto ADT Hi Todor, It is provided by the Yocto eclipse plugin itself. Regards, Raghavendra. From: Minchev, Todor todor.minc...@intel.com Sent: Friday, May 15, 2015 5:27 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT On Fri, 2015-05-15 at 11:33 +, Raghavendra Kakarla wrote: Hi Todor, It is an autotool based example. It is not generated makefile itself. Is it an example you created yourself or is it the autotools C Hello World template provided by the Yocto Eclipse Plug-in. I attached the makefile.in and makefile.am file to the paste bin. Could you please paste the Makefile and share the pastebin link? Thanks, Raghavendra. From: Minchev, Todor todor.minc...@intel.com Sent: Friday, May 15, 2015 4:41 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT Hello Raghavendra, Could you please pastebin the makefile from your project? http://pastebin.com/ Cheers, Todor On Fri, 2015-05-15 at 10:47 +, Raghavendra Kakarla wrote: Hi Todor, Thank you for your reply. By default we have the setting like this only. But we got the error. Thanks, Raghavendra. From: Minchev, Todor todor.minc...@intel.com Sent: Friday, May 15, 2015 4:05 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT Hello Raghavendra, Please try the following: Right click on your project - Properties - C/C++ Build - Select the 'Behavior' tab - untick 'Build on resource save' and remove 'all' from the 'Build' field Cheers, Todor On Fri, 2015-05-15 at 09:32 +, Raghavendra Kakarla wrote: Hi All, I have problem with the ADT while i am building the autotool example helloword project which is given in the yocto ADT autotool project. Could you please help me in resolving this issue. I followed the following steps for installing the adt in my development PC: I built the toolchain using the following command: $cd ~/poky $source ./oe-init-build-env $bitbake meta-ide-support Extract the root file system by using the following commands: $cd ~ $source ~/poky/build/tmp/environment-setup-mips32r2el-poky-linux $runqemu-extract-sdk \ ~/poky/build/tmp/deploy/images/arqlyn/ core-image-minimal-dhruwa_ioe-20150511102759.rootfs.tar.bz2\ $HOME/arqlyn I followed the command given in the yocto project dev-manual for installing eclipse and adding yocto plugin to eclipse. I Gave the following data to the eclipse for configuring the cross-compiler options: 1. I select the Build System Derived Toolchain 2.point the toolchain path to home/testuser/poky/build 3.gave sysroot path to /home/testuser/arqlyn After entered this information I got the my machine-name in the select the target architecture filed. After this I create a autotool support project and tried to build but it gives the error. Regards, Raghavendra. ___ yocto mailing list yocto@yoctoproject.org
Re: [yocto] Issue with yocto ADT
Hi Todor, Thank you for your reply. Now I am able to build the application with my extracted rootfs. I built the rootfs for our machine. for launching the qemu from the eclipse,is it required we should build it for qemu? I have the previously built qemu kernel image and i give it path to the eclipse's qemu kernel path field. Qemu is launched but it gives error while switching from kernel to rootfs i.e init script execution problem. Regards, Raghavendra. From: Minchev, Todor todor.minc...@intel.com Sent: Tuesday, May 19, 2015 1:14 PM To: Raghavendra Kakarla Cc: Surya Dommeti; Ramakrishna Chatram; yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT On Tue, 2015-05-19 at 07:07 +, Raghavendra Kakarla wrote: Hi Todor, For not working scenario there is no makefile created. For working scenario using build directory sysroot makefiles are created. So configure fails to create your Makefile. You probably see something like this in your config.log: configure: error: C compiler cannot create executables configure: error: C compiler cannot create executables See `config.log' for more details Please have a look at this thread, it explains how to resolve this problem: https://lists.yoctoproject.org/pipermail/yocto/2015-March/024089.html Cheers, Todor I attaching the makefile for working scenario. Regards, Raghavendra K. From: Minchev, Todor todor.minc...@intel.com Sent: Tuesday, May 19, 2015 12:13 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT On Mon, 2015-05-18 at 16:55 +, Raghavendra Kakarla wrote: Hi Todor, I created four more new projects. For all the projects I gives error like this only. Is the error message the same as the original one you posted about a missing make `all` target? Can send those projects make files? Please share both your working and non-working Makefiles. But when I give the sysroot path in eclipse to the poky/build/tmp/sysroot/machine it worked properly. When we give the extracted sysroot it gives problem. Regards, Raghavendra. From: Minchev, Todor [todor.minc...@intel.com] Sent: Monday, May 18, 2015 9:51 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT Hello Raghavendra, On Mon, 2015-05-18 at 05:07 +, Raghavendra Kakarla wrote: Hi Todor, Could you please let me know the cause for the issue. Please pastebin your Makefile and share the pastebin link. Seem like your project is corrupt and the Makefile is not generated correctly. Have you tried to delete the project and create a new one? Thanks in advance. Regards, Raghavendra K. From: Raghavendra Kakarla Sent: Friday, May 15, 2015 5:31 PM To: Minchev, Todor Cc: yocto@yoctoproject.org Subject: RE: [yocto] Issue with yocto ADT Hi Todor, It is provided by the Yocto eclipse plugin itself. Regards, Raghavendra. From: Minchev, Todor todor.minc...@intel.com Sent: Friday, May 15, 2015 5:27 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT On Fri, 2015-05-15 at 11:33 +, Raghavendra Kakarla wrote: Hi Todor, It is an autotool based example. It is not generated makefile itself. Is it an example you created yourself or is it the autotools C Hello World template provided by the Yocto Eclipse Plug-in. I attached the makefile.in and makefile.am file to the paste bin. Could you please paste the Makefile and share the pastebin link? Thanks, Raghavendra. From: Minchev, Todor todor.minc...@intel.com Sent: Friday, May 15, 2015 4:41 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT Hello Raghavendra, Could you please pastebin the makefile from your project? http://pastebin.com/ Cheers, Todor On Fri, 2015-05-15 at 10:47 +, Raghavendra Kakarla wrote: Hi Todor, Thank you for your reply. By default we have the setting like this only. But we got the error. Thanks, Raghavendra. From: Minchev, Todor todor.minc...@intel.com Sent: Friday, May 15, 2015 4:05 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT Hello Raghavendra, Please try the following: Right click on your project - Properties - C/C++ Build - Select the 'Behavior' tab - untick 'Build on resource save' and remove 'all' from the
Re: [yocto] Issue with yocto ADT
On Tue, 2015-05-19 at 09:49 +, Raghavendra Kakarla wrote: Hi Todor, Thank you for your reply. Now I am able to build the application with my extracted rootfs. I built the rootfs for our machine. for launching the qemu from the eclipse,is it required we should build it for qemu? I have the previously built qemu kernel image and i give it path to the eclipse's qemu kernel path field. Qemu is launched but it gives error while switching from kernel to rootfs i.e init script execution problem. If your rootfs does not have /sbin/init, your kernel won't be able to execute the topmost parent process(init) and the boot will fail? What is the error message? Regards, Raghavendra. From: Minchev, Todor todor.minc...@intel.com Sent: Tuesday, May 19, 2015 1:14 PM To: Raghavendra Kakarla Cc: Surya Dommeti; Ramakrishna Chatram; yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT On Tue, 2015-05-19 at 07:07 +, Raghavendra Kakarla wrote: Hi Todor, For not working scenario there is no makefile created. For working scenario using build directory sysroot makefiles are created. So configure fails to create your Makefile. You probably see something like this in your config.log: configure: error: C compiler cannot create executables configure: error: C compiler cannot create executables See `config.log' for more details Please have a look at this thread, it explains how to resolve this problem: https://lists.yoctoproject.org/pipermail/yocto/2015-March/024089.html Cheers, Todor I attaching the makefile for working scenario. Regards, Raghavendra K. From: Minchev, Todor todor.minc...@intel.com Sent: Tuesday, May 19, 2015 12:13 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT On Mon, 2015-05-18 at 16:55 +, Raghavendra Kakarla wrote: Hi Todor, I created four more new projects. For all the projects I gives error like this only. Is the error message the same as the original one you posted about a missing make `all` target? Can send those projects make files? Please share both your working and non-working Makefiles. But when I give the sysroot path in eclipse to the poky/build/tmp/sysroot/machine it worked properly. When we give the extracted sysroot it gives problem. Regards, Raghavendra. From: Minchev, Todor [todor.minc...@intel.com] Sent: Monday, May 18, 2015 9:51 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT Hello Raghavendra, On Mon, 2015-05-18 at 05:07 +, Raghavendra Kakarla wrote: Hi Todor, Could you please let me know the cause for the issue. Please pastebin your Makefile and share the pastebin link. Seem like your project is corrupt and the Makefile is not generated correctly. Have you tried to delete the project and create a new one? Thanks in advance. Regards, Raghavendra K. From: Raghavendra Kakarla Sent: Friday, May 15, 2015 5:31 PM To: Minchev, Todor Cc: yocto@yoctoproject.org Subject: RE: [yocto] Issue with yocto ADT Hi Todor, It is provided by the Yocto eclipse plugin itself. Regards, Raghavendra. From: Minchev, Todor todor.minc...@intel.com Sent: Friday, May 15, 2015 5:27 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT On Fri, 2015-05-15 at 11:33 +, Raghavendra Kakarla wrote: Hi Todor, It is an autotool based example. It is not generated makefile itself. Is it an example you created yourself or is it the autotools C Hello World template provided by the Yocto Eclipse Plug-in. I attached the makefile.in and makefile.am file to the paste bin. Could you please paste the Makefile and share the pastebin link? Thanks, Raghavendra. From: Minchev, Todor todor.minc...@intel.com Sent: Friday, May 15, 2015 4:41 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT Hello Raghavendra, Could you please pastebin the makefile from your project? http://pastebin.com/ Cheers, Todor On Fri, 2015-05-15 at 10:47 +, Raghavendra Kakarla wrote: Hi Todor, Thank you for your reply. By default we have the setting like this only. But we got the error. Thanks, Raghavendra. From: Minchev, Todor
Re: [yocto] [meta-ti] Migration from 1.7.1 to 1.8 - kernel-abiversion missing
On Fri, May 15, 2015 at 4:21 PM, Brian Hutchinson b.hutch...@gmail.com wrote: On Fri, May 15, 2015 at 3:26 PM, Brian Hutchinson b.hutch...@gmail.com wrote: On Fri, May 15, 2015 at 9:55 AM, Brian Hutchinson b.hutch...@gmail.com wrote: On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson b.hutch...@gmail.com wrote: On May 14, 2015 6:08 PM, Denys Dmytriyenko de...@denix.org wrote: On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote: On 2015-05-12 10:20 AM, Brian Hutchinson wrote: On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield bruce.ashfi...@windriver.com wrote: On 2015-05-11 02:10 PM, Brian Hutchinson wrote: On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield bruce.ashfi...@windriver.com wrote: It is plausible. But in theory, linux-dummy should still provide what you need (but since it doesn't build anything, there is no abi .. and no modules can be built against it) .. so the error isn't graceful. Bruce I can confirm this same problem is happening to me. I just updated one of my builds from 1.7 to 1.8 and am also getting my rootfs to fail due to no abi kernel version: We still have a race condition in the 1.8 branch for the population of the build-artifacts directory. If modules start building, they'll race against the population of the abiversion, and you may see that message. There's a proposed patch for master, but I don't think it is in fido yet. Bruce Hi Bruce, I did some searches and looks like there are a number of 'race' condition fixes but it wasn't obvious which one I may need. Is it this one: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98 That's the one that should make sure that the shared workdir (Which has the abiversion) is in place before building any modules. I can't say that it is exactly your issue, but it is the change I was thinking of. Brian, Were you able to try the above mentioned commit against am180x in meta-ti? Did it solve the missing abi kernel version? Thanks. -- Denys Hi Denys, No, I got caught up in something else ... I'll try it tomorrow and report back after I cherry pick that commit Bruce mentioned. Regards, Brian Update. Not sure if I did this right but this is what I did. I added master as a remote and cherry picked 02d0a003d603266114512160b209876199241e98. Next I just went for it and tried to bitbake my image again and got the same result as before. Next I did a bitbake cleanall on virtual/kernel and tried to make my image again and still got the same result. I'm going to leave this build as is and setup a new one using 1.8 master and see if I get the same thing again. I'll leave this broken build alone for a while in case someone wants me to try something with it to fix it. Regards, Brian Yet another update ... I did a fresh checkout of master and tried to build and had the same kernelabiversion error: WARNING: omap3-sgx-modules-5.01.01.01 ONLY supports hardfp mode for now### | ETA: 00:00:28 WARNING: omap3-sgx-modules-5.01.01.02 ONLY supports hardfp mode for now WARNING: ti-cgt6x-8.0.0 ONLY supports hardfp mode for now | ETA: 00:00:26 Parsing recipes: 100% |##| Time: 00:01:02 Parsing of 1802 .bb files complete (0 cached, 1802 parsed). 2303 targets, 182 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies NOTE: multiple providers are available for u-boot (u-boot, u-boot-glsdk, u-boot-ti-staging) NOTE: consider defining a PREFERRED_PROVIDER entry to match u-boot NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo) NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg Build Configuration: BB_VERSION= 1.27.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Debian-7.8 TARGET_SYS= arm-poky-linux-gnueabi MACHINE = am180x-evm DISTRO= poky DISTRO_VERSION= 1.8+snapshot-20150515 TUNE_FEATURES = arm armv5 thumb dsp TARGET_FPU= soft meta meta-yocto meta-yocto-bsp= master:fab7da4f8030a4067db0522f77eaa6d3b501c68f meta-ti = master:60a7bfbf96609ef6f3e084c32b2af853222b3b7e meta-oe meta-python meta-networking meta-webserver= master:53d55216c8c721d3b66ec8f968737bf081def870 NOTE: Preparing RunQueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks WARNING: QA Issue: /usr/bin/apxs_apache2-dev contained in package apache2-dev requires /usr/bin/perl, but no providers found in its RDEPENDS [file-rdeps] ERROR: No kernel-abiversion file found
Re: [yocto] Issue with yocto ADT
Hi Todor, sbin/init script is there in the rootfile system. But i built rootfile system for my BSP and I give this rootfs to the eclipse sysroot path. And i select the qemu instead of externel hardware. I give the qemu kernel path to prevuiously built qemumips kernel image which is built before my BSP is built. When I click on the external Tool - qemu_mips-poky-linux qemu image is booted and gives the following error. -sbin/init exist but could not execute it Regards, Raghavenmdra K. From: Minchev, Todor todor.minc...@intel.com Sent: Tuesday, May 19, 2015 5:01 PM To: Raghavendra Kakarla Cc: Surya Dommeti; Ramakrishna Chatram; yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT On Tue, 2015-05-19 at 09:49 +, Raghavendra Kakarla wrote: Hi Todor, Thank you for your reply. Now I am able to build the application with my extracted rootfs. I built the rootfs for our machine. for launching the qemu from the eclipse,is it required we should build it for qemu? I have the previously built qemu kernel image and i give it path to the eclipse's qemu kernel path field. Qemu is launched but it gives error while switching from kernel to rootfs i.e init script execution problem. If your rootfs does not have /sbin/init, your kernel won't be able to execute the topmost parent process(init) and the boot will fail? What is the error message? Regards, Raghavendra. From: Minchev, Todor todor.minc...@intel.com Sent: Tuesday, May 19, 2015 1:14 PM To: Raghavendra Kakarla Cc: Surya Dommeti; Ramakrishna Chatram; yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT On Tue, 2015-05-19 at 07:07 +, Raghavendra Kakarla wrote: Hi Todor, For not working scenario there is no makefile created. For working scenario using build directory sysroot makefiles are created. So configure fails to create your Makefile. You probably see something like this in your config.log: configure: error: C compiler cannot create executables configure: error: C compiler cannot create executables See `config.log' for more details Please have a look at this thread, it explains how to resolve this problem: https://lists.yoctoproject.org/pipermail/yocto/2015-March/024089.html Cheers, Todor I attaching the makefile for working scenario. Regards, Raghavendra K. From: Minchev, Todor todor.minc...@intel.com Sent: Tuesday, May 19, 2015 12:13 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT On Mon, 2015-05-18 at 16:55 +, Raghavendra Kakarla wrote: Hi Todor, I created four more new projects. For all the projects I gives error like this only. Is the error message the same as the original one you posted about a missing make `all` target? Can send those projects make files? Please share both your working and non-working Makefiles. But when I give the sysroot path in eclipse to the poky/build/tmp/sysroot/machine it worked properly. When we give the extracted sysroot it gives problem. Regards, Raghavendra. From: Minchev, Todor [todor.minc...@intel.com] Sent: Monday, May 18, 2015 9:51 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT Hello Raghavendra, On Mon, 2015-05-18 at 05:07 +, Raghavendra Kakarla wrote: Hi Todor, Could you please let me know the cause for the issue. Please pastebin your Makefile and share the pastebin link. Seem like your project is corrupt and the Makefile is not generated correctly. Have you tried to delete the project and create a new one? Thanks in advance. Regards, Raghavendra K. From: Raghavendra Kakarla Sent: Friday, May 15, 2015 5:31 PM To: Minchev, Todor Cc: yocto@yoctoproject.org Subject: RE: [yocto] Issue with yocto ADT Hi Todor, It is provided by the Yocto eclipse plugin itself. Regards, Raghavendra. From: Minchev, Todor todor.minc...@intel.com Sent: Friday, May 15, 2015 5:27 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT On Fri, 2015-05-15 at 11:33 +, Raghavendra Kakarla wrote: Hi Todor, It is an autotool based example. It is not generated makefile itself. Is it an example you created yourself or is it the autotools C Hello World template provided by the Yocto Eclipse Plug-in. I attached the makefile.in and makefile.am file to the paste bin. Could you please paste the Makefile and share the pastebin link? Thanks, Raghavendra.
Re: [yocto] Issue with yocto ADT
Hi Todor, Now I am able to build the application,launch the qemu and run the application from eclipse. but when I run the application in stepmode or stepover it gives the following error. Reading symbols from /home/testuser/workspace/test16/src/test16...done. warning: GDB can't find the start of the function at 0x31c73cf0. GDB is unable to find the start of the function at 0x31c73cf0 and thus can't determine the size of that function's stack frame. This means that GDB may be unable to access that stack frame, or the frames below it. This problem is most likely caused by an invalid program counter or stack pointer. However, if you think GDB should simply search farther back from 0x31c73cf0 for code which looks like the beginning of a function, you can increase the range of the search using the `set heuristic-fence-post' command. warning: GDB can't find the start of the function at 0x31c62ed4. warning: GDB can't find the start of the function at 0x31c73cf0. warning: GDB can't find the start of the function at 0x31c63e30. warning: GDB can't find the start of the function at 0x31d11380. Regards, Raghavendra K. From: Minchev, Todor todor.minc...@intel.com Sent: Tuesday, May 19, 2015 5:52 PM To: Raghavendra Kakarla Cc: Surya Dommeti; Ramakrishna Chatram; yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT On Tue, 2015-05-19 at 12:03 +, Raghavendra Kakarla wrote: Hi Todor, sbin/init script is there in the rootfile system. But i built rootfile system for my BSP and I give this rootfs to the eclipse sysroot path. And i select the qemu instead of externel hardware. I give the qemu kernel path to prevuiously built qemumips kernel image which is built before my BSP is built. When I click on the external Tool - qemu_mips-poky-linux qemu image is booted and gives the following error. -sbin/init exist but could not execute it This error message should be followed by an error number. Also check that your /sbin/init is executable. Regards, Raghavenmdra K. From: Minchev, Todor todor.minc...@intel.com Sent: Tuesday, May 19, 2015 5:01 PM To: Raghavendra Kakarla Cc: Surya Dommeti; Ramakrishna Chatram; yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT On Tue, 2015-05-19 at 09:49 +, Raghavendra Kakarla wrote: Hi Todor, Thank you for your reply. Now I am able to build the application with my extracted rootfs. I built the rootfs for our machine. for launching the qemu from the eclipse,is it required we should build it for qemu? I have the previously built qemu kernel image and i give it path to the eclipse's qemu kernel path field. Qemu is launched but it gives error while switching from kernel to rootfs i.e init script execution problem. If your rootfs does not have /sbin/init, your kernel won't be able to execute the topmost parent process(init) and the boot will fail? What is the error message? Regards, Raghavendra. From: Minchev, Todor todor.minc...@intel.com Sent: Tuesday, May 19, 2015 1:14 PM To: Raghavendra Kakarla Cc: Surya Dommeti; Ramakrishna Chatram; yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT On Tue, 2015-05-19 at 07:07 +, Raghavendra Kakarla wrote: Hi Todor, For not working scenario there is no makefile created. For working scenario using build directory sysroot makefiles are created. So configure fails to create your Makefile. You probably see something like this in your config.log: configure: error: C compiler cannot create executables configure: error: C compiler cannot create executables See `config.log' for more details Please have a look at this thread, it explains how to resolve this problem: https://lists.yoctoproject.org/pipermail/yocto/2015-March/024089.html Cheers, Todor I attaching the makefile for working scenario. Regards, Raghavendra K. From: Minchev, Todor todor.minc...@intel.com Sent: Tuesday, May 19, 2015 12:13 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT On Mon, 2015-05-18 at 16:55 +, Raghavendra Kakarla wrote: Hi Todor, I created four more new projects. For all the projects I gives error like this only. Is the error message the same as the original one you posted about a missing make `all` target? Can send those projects make files? Please share both your working and non-working Makefiles. But when I give the sysroot path in eclipse to the poky/build/tmp/sysroot/machine it worked properly. When we give the extracted sysroot it gives problem. Regards, Raghavendra. From: Minchev, Todor [todor.minc...@intel.com]
[yocto] Modify configuration via bb file
Dear All, I am compiling coreutils package with the coreutils.bb file and its compiling successfully, now I need to modify the arguments passed to ./configure command I tried to modify in the bb file but I did not get the proper results. Please suggest me where to modify parameters to ./configure via bb file or if any other way. Thanks and regards DILIP KUMAR B LT Technology Services Ltd www.LntTechservices.comhttp://www.lnttechservices.com/ This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Modify configuration via bb file
On May 19, 2015, at 9:44 PM, Dilip Basavaraju dilip.kum...@lnttechservices.com wrote: Dear All, I am compiling coreutils package with the coreutils.bb file and its compiling successfully, now I need to modify the arguments passed to ./configure command I tried to modify in the bb file but I did not get the proper results. Pass it using EXTRA_OECONF in recipe e.g. EXTRA_OECONF += “—enable-foo Please suggest me where to modify parameters to ./configure via bb file or if any other way. Thanks and regards DILIP KUMAR B LT Technology Services Ltd www.LntTechservices.com http://www.lnttechservices.com/ This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. -- ___ yocto mailing list yocto@yoctoproject.org mailto:yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto https://lists.yoctoproject.org/listinfo/yocto signature.asc Description: Message signed with OpenPGP using GPGMail -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Build available for QA
A build identified as needing QA has finished on the autobuilder. This build is located at: http://autobuilder.yoctoproject.org/pub/nightly/20150519-2 Build hash information: meta-intel : f9738ec19d3b2864c0bd71b9bb3418d16e922a12 meta-fsl-arm : f52c9106689f33c78b09496f4929ae1e87d13970 meta-minnow : 13a5f2ab84c7284647a3e067a33109c11dae0568 meta-qt3 : 3016129d90b7ac8517a5227d819f10ad417b5b45 meta-fsl-ppc : c3051ab6b3b24759e02202d00baf280f04fdac86 poky : 8b8859a8fee709a808b4cbb8ed126b8f7e1eafa9 This is an automated message from The Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder Email: elizabeth.flana...@intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Issue with yocto ADT
On Tue, 2015-05-19 at 12:03 +, Raghavendra Kakarla wrote: Hi Todor, sbin/init script is there in the rootfile system. But i built rootfile system for my BSP and I give this rootfs to the eclipse sysroot path. And i select the qemu instead of externel hardware. I give the qemu kernel path to prevuiously built qemumips kernel image which is built before my BSP is built. When I click on the external Tool - qemu_mips-poky-linux qemu image is booted and gives the following error. -sbin/init exist but could not execute it This error message should be followed by an error number. Also check that your /sbin/init is executable. Regards, Raghavenmdra K. From: Minchev, Todor todor.minc...@intel.com Sent: Tuesday, May 19, 2015 5:01 PM To: Raghavendra Kakarla Cc: Surya Dommeti; Ramakrishna Chatram; yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT On Tue, 2015-05-19 at 09:49 +, Raghavendra Kakarla wrote: Hi Todor, Thank you for your reply. Now I am able to build the application with my extracted rootfs. I built the rootfs for our machine. for launching the qemu from the eclipse,is it required we should build it for qemu? I have the previously built qemu kernel image and i give it path to the eclipse's qemu kernel path field. Qemu is launched but it gives error while switching from kernel to rootfs i.e init script execution problem. If your rootfs does not have /sbin/init, your kernel won't be able to execute the topmost parent process(init) and the boot will fail? What is the error message? Regards, Raghavendra. From: Minchev, Todor todor.minc...@intel.com Sent: Tuesday, May 19, 2015 1:14 PM To: Raghavendra Kakarla Cc: Surya Dommeti; Ramakrishna Chatram; yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT On Tue, 2015-05-19 at 07:07 +, Raghavendra Kakarla wrote: Hi Todor, For not working scenario there is no makefile created. For working scenario using build directory sysroot makefiles are created. So configure fails to create your Makefile. You probably see something like this in your config.log: configure: error: C compiler cannot create executables configure: error: C compiler cannot create executables See `config.log' for more details Please have a look at this thread, it explains how to resolve this problem: https://lists.yoctoproject.org/pipermail/yocto/2015-March/024089.html Cheers, Todor I attaching the makefile for working scenario. Regards, Raghavendra K. From: Minchev, Todor todor.minc...@intel.com Sent: Tuesday, May 19, 2015 12:13 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT On Mon, 2015-05-18 at 16:55 +, Raghavendra Kakarla wrote: Hi Todor, I created four more new projects. For all the projects I gives error like this only. Is the error message the same as the original one you posted about a missing make `all` target? Can send those projects make files? Please share both your working and non-working Makefiles. But when I give the sysroot path in eclipse to the poky/build/tmp/sysroot/machine it worked properly. When we give the extracted sysroot it gives problem. Regards, Raghavendra. From: Minchev, Todor [todor.minc...@intel.com] Sent: Monday, May 18, 2015 9:51 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT Hello Raghavendra, On Mon, 2015-05-18 at 05:07 +, Raghavendra Kakarla wrote: Hi Todor, Could you please let me know the cause for the issue. Please pastebin your Makefile and share the pastebin link. Seem like your project is corrupt and the Makefile is not generated correctly. Have you tried to delete the project and create a new one? Thanks in advance. Regards, Raghavendra K. From: Raghavendra Kakarla Sent: Friday, May 15, 2015 5:31 PM To: Minchev, Todor Cc: yocto@yoctoproject.org Subject: RE: [yocto] Issue with yocto ADT Hi Todor, It is provided by the Yocto eclipse plugin itself. Regards, Raghavendra. From: Minchev, Todor todor.minc...@intel.com Sent: Friday, May 15, 2015 5:27 PM To: Raghavendra Kakarla Cc: yocto@yoctoproject.org Subject: Re: [yocto] Issue with yocto ADT On Fri, 2015-05-15 at 11:33 +, Raghavendra Kakarla wrote: Hi Todor, It is an autotool based example. It is not generated makefile itself.
[yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, May 5, 2015 8:00 AM US Pacific Time
Attendees: Ross, Stephen, Richard, Jussi, Saul, Denys, Sona, Bruce, Paul, Mark, Josep, Oliver, Alex V., Maxin, Agenda: * Opens collection - 5 min (Stephen) * Yocto Project status - 5 min (Stephen/team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.9_Status https://wiki.yoctoproject.org/wiki/Yocto_1.9_Schedule https://wiki.yoctoproject.org/wiki/Yocto_1.9_Features YP 1.7.2 is released. YP 1.6.3 is in QA now. YP 1.9 M1 is in process. * SWAT team rotation: Benjamin - Juro https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team * Opens - 10 min Richard - gcc 5.1 recipes are in the master branch. * Team Sharing - 10 min Mark - Some patches coming from Samsung are in process and should be done in a few weeks. Let Mark know if there are concerns with this. 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-ti] Migration from 1.7.1 to 1.8 - kernel-abiversion missing
On Tue, May 19, 2015 at 12:31 PM, Bruce Ashfield bruce.ashfi...@windriver.com wrote: On 2015-05-19 07:39 AM, Bruce Ashfield wrote: On Fri, May 15, 2015 at 4:21 PM, Brian Hutchinson b.hutch...@gmail.com wrote: On Fri, May 15, 2015 at 3:26 PM, Brian Hutchinson b.hutch...@gmail.com wrote: On Fri, May 15, 2015 at 9:55 AM, Brian Hutchinson b.hutch...@gmail.com wrote: On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson b.hutch...@gmail.com wrote: On May 14, 2015 6:08 PM, Denys Dmytriyenko de...@denix.org wrote: On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote: On 2015-05-12 10:20 AM, Brian Hutchinson wrote: On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield bruce.ashfi...@windriver.com wrote: On 2015-05-11 02:10 PM, Brian Hutchinson wrote: On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield bruce.ashfi...@windriver.com wrote: It is plausible. But in theory, linux-dummy should still provide what you need (but since it doesn't build anything, there is no abi .. and no modules can be built against it) .. so the error isn't graceful. Bruce I can confirm this same problem is happening to me. I just updated one of my builds from 1.7 to 1.8 and am also getting my rootfs to fail due to no abi kernel version: We still have a race condition in the 1.8 branch for the population of the build-artifacts directory. If modules start building, they'll race against the population of the abiversion, and you may see that message. There's a proposed patch for master, but I don't think it is in fido yet. Bruce Hi Bruce, I did some searches and looks like there are a number of 'race' condition fixes but it wasn't obvious which one I may need. Is it this one: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98 That's the one that should make sure that the shared workdir (Which has the abiversion) is in place before building any modules. I can't say that it is exactly your issue, but it is the change I was thinking of. Brian, Were you able to try the above mentioned commit against am180x in meta-ti? Did it solve the missing abi kernel version? Thanks. -- Denys Hi Denys, No, I got caught up in something else ... I'll try it tomorrow and report back after I cherry pick that commit Bruce mentioned. Regards, Brian Update. Not sure if I did this right but this is what I did. I added master as a remote and cherry picked 02d0a003d603266114512160b209876199241e98. Next I just went for it and tried to bitbake my image again and got the same result as before. Next I did a bitbake cleanall on virtual/kernel and tried to make my image again and still got the same result. I'm going to leave this build as is and setup a new one using 1.8 master and see if I get the same thing again. I'll leave this broken build alone for a while in case someone wants me to try something with it to fix it. Regards, Brian Yet another update ... I did a fresh checkout of master and tried to build and had the same kernelabiversion error: WARNING: omap3-sgx-modules-5.01.01.01 ONLY supports hardfp mode for now### | ETA: 00:00:28 WARNING: omap3-sgx-modules-5.01.01.02 ONLY supports hardfp mode for now WARNING: ti-cgt6x-8.0.0 ONLY supports hardfp mode for now | ETA: 00:00:26 Parsing recipes: 100% |##| Time: 00:01:02 Parsing of 1802 .bb files complete (0 cached, 1802 parsed). 2303 targets, 182 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies NOTE: multiple providers are available for u-boot (u-boot, u-boot-glsdk, u-boot-ti-staging) NOTE: consider defining a PREFERRED_PROVIDER entry to match u-boot NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo) NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg Build Configuration: BB_VERSION= 1.27.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Debian-7.8 TARGET_SYS= arm-poky-linux-gnueabi MACHINE = am180x-evm DISTRO= poky DISTRO_VERSION= 1.8+snapshot-20150515 TUNE_FEATURES = arm armv5 thumb dsp TARGET_FPU= soft meta meta-yocto meta-yocto-bsp= master:fab7da4f8030a4067db0522f77eaa6d3b501c68f meta-ti = master:60a7bfbf96609ef6f3e084c32b2af853222b3b7e meta-oe meta-python meta-networking meta-webserver= master:53d55216c8c721d3b66ec8f968737bf081def870 NOTE: Preparing RunQueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks WARNING: QA Issue: /usr/bin/apxs_apache2-dev contained in package apache2-dev requires /usr/bin/perl, but no providers found in its RDEPENDS [file-rdeps]
Re: [linux-yocto] [PATCH] common-pc-drivers: Enable CONFIG_ATA_BMDMA
On 2015-05-19 12:23 AM, Saul Wold wrote: On 05/18/2015 08:21 PM, Bruce Ashfield wrote: On 2015-05-17 2:07 PM, Saul Wold wrote: Enabling the ATA_BMDMA re-enables ATA_PIIX which was getting disabled Which trees are you targeting with this change ? 3.19, -dev and 3.14 ? I would stay 3.19 and -dev for this one. I think it changed between 3.14 and 3.19 which caused the warning. sounds good. I worked on gcc5 issues all day today, and didn't get to merging the new content. But I will apply this tomorrow. Cheers, Bruce Sau! Bruce Signed-off-by: Saul Wold s...@linux.intel.com --- meta/cfg/kernel-cache/bsp/common-pc/common-pc-drivers.cfg | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/meta/cfg/kernel-cache/bsp/common-pc/common-pc-drivers.cfg b/meta/cfg/kernel-cache/bsp/common-pc/common-pc-drivers.cfg index 7160843..0b82190 100644 --- a/meta/cfg/kernel-cache/bsp/common-pc/common-pc-drivers.cfg +++ b/meta/cfg/kernel-cache/bsp/common-pc/common-pc-drivers.cfg @@ -5,7 +5,8 @@ CONFIG_PCI_MSI=y CONFIG_ATA=y CONFIG_ATA_ACPI=y CONFIG_ATA_SFF=y -CONFIG_ATA_PIIX=y +CONFIG_ATA_BMDMA=y +CONFIG_ATA_PIIX=m CONFIG_INPUT=y CONFIG_INPUT_MOUSEDEV=y -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [yocto] [meta-ti] Migration from 1.7.1 to 1.8 - kernel-abiversion missing
On 2015-05-19 07:39 AM, Bruce Ashfield wrote: On Fri, May 15, 2015 at 4:21 PM, Brian Hutchinson b.hutch...@gmail.com wrote: On Fri, May 15, 2015 at 3:26 PM, Brian Hutchinson b.hutch...@gmail.com wrote: On Fri, May 15, 2015 at 9:55 AM, Brian Hutchinson b.hutch...@gmail.com wrote: On Thu, May 14, 2015 at 6:16 PM, Brian Hutchinson b.hutch...@gmail.com wrote: On May 14, 2015 6:08 PM, Denys Dmytriyenko de...@denix.org wrote: On Tue, May 12, 2015 at 11:35:20AM -0400, Bruce Ashfield wrote: On 2015-05-12 10:20 AM, Brian Hutchinson wrote: On Mon, May 11, 2015 at 3:06 PM, Bruce Ashfield bruce.ashfi...@windriver.com wrote: On 2015-05-11 02:10 PM, Brian Hutchinson wrote: On Thu, Apr 30, 2015 at 10:06 AM, Bruce Ashfield bruce.ashfi...@windriver.com wrote: It is plausible. But in theory, linux-dummy should still provide what you need (but since it doesn't build anything, there is no abi .. and no modules can be built against it) .. so the error isn't graceful. Bruce I can confirm this same problem is happening to me. I just updated one of my builds from 1.7 to 1.8 and am also getting my rootfs to fail due to no abi kernel version: We still have a race condition in the 1.8 branch for the population of the build-artifacts directory. If modules start building, they'll race against the population of the abiversion, and you may see that message. There's a proposed patch for master, but I don't think it is in fido yet. Bruce Hi Bruce, I did some searches and looks like there are a number of 'race' condition fixes but it wasn't obvious which one I may need. Is it this one: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=02d0a003d603266114512160b209876199241e98 That's the one that should make sure that the shared workdir (Which has the abiversion) is in place before building any modules. I can't say that it is exactly your issue, but it is the change I was thinking of. Brian, Were you able to try the above mentioned commit against am180x in meta-ti? Did it solve the missing abi kernel version? Thanks. -- Denys Hi Denys, No, I got caught up in something else ... I'll try it tomorrow and report back after I cherry pick that commit Bruce mentioned. Regards, Brian Update. Not sure if I did this right but this is what I did. I added master as a remote and cherry picked 02d0a003d603266114512160b209876199241e98. Next I just went for it and tried to bitbake my image again and got the same result as before. Next I did a bitbake cleanall on virtual/kernel and tried to make my image again and still got the same result. I'm going to leave this build as is and setup a new one using 1.8 master and see if I get the same thing again. I'll leave this broken build alone for a while in case someone wants me to try something with it to fix it. Regards, Brian Yet another update ... I did a fresh checkout of master and tried to build and had the same kernelabiversion error: WARNING: omap3-sgx-modules-5.01.01.01 ONLY supports hardfp mode for now### | ETA: 00:00:28 WARNING: omap3-sgx-modules-5.01.01.02 ONLY supports hardfp mode for now WARNING: ti-cgt6x-8.0.0 ONLY supports hardfp mode for now | ETA: 00:00:26 Parsing recipes: 100% |##| Time: 00:01:02 Parsing of 1802 .bb files complete (0 cached, 1802 parsed). 2303 targets, 182 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies NOTE: multiple providers are available for u-boot (u-boot, u-boot-glsdk, u-boot-ti-staging) NOTE: consider defining a PREFERRED_PROVIDER entry to match u-boot NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo) NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg Build Configuration: BB_VERSION= 1.27.0 BUILD_SYS = x86_64-linux NATIVELSBSTRING = Debian-7.8 TARGET_SYS= arm-poky-linux-gnueabi MACHINE = am180x-evm DISTRO= poky DISTRO_VERSION= 1.8+snapshot-20150515 TUNE_FEATURES = arm armv5 thumb dsp TARGET_FPU= soft meta meta-yocto meta-yocto-bsp= master:fab7da4f8030a4067db0522f77eaa6d3b501c68f meta-ti = master:60a7bfbf96609ef6f3e084c32b2af853222b3b7e meta-oe meta-python meta-networking meta-webserver= master:53d55216c8c721d3b66ec8f968737bf081def870 NOTE: Preparing RunQueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks WARNING: QA Issue: /usr/bin/apxs_apache2-dev contained in package apache2-dev requires /usr/bin/perl, but no providers found in its RDEPENDS [file-rdeps] ERROR: No kernel-abiversion file found (/home/hutch/yocto_1.8_davinci_2/poky/build/tmp/sysroots/am180x-evm/pkgdata/kernel-depmod/kernel-abiversion), cannot run depmod, aborting ERROR: Function failed:
Re: [yocto] One recipe, two gits with destsuffix, how to patch?
Hi Paul, Sorry for the late, or veeery late reply, but your suggestion here seems to do the work. Thanks for the help! BR Kalle On 2015-01-27 11:42, Paul Eggleton wrote: On Tuesday 27 January 2015 10:29:12 Kalle Komierowski wrote: I just modified my recipe with the patchdir. SRC_URI = x.patch;patchdir=backports/ I can see that the patches are copied to the destination where I want them but for some reason they all fail when yocto tries to apply them. If I go manually to the destination git and type git am x.patch the all apply with no problem, I also tried to patch -p1 x.patch and that worked to. Maybe I should play a bit with the striplevel? But I do think that yocto should be able to handle it from the point where I gave it the patchdir=.. The default striplevel is 1. If the patch is formatted typically, suspect this means that you'd need patchdir to be set to ../backports - does that not work? Cheers, Paul -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Files/directories were installed but not shipped
I am getting ERROR: QA Issue: Files/directories were installed but not
shipped when I try to build my custom layer. It then list bunch of
directories and files under
/usr/src
/usr/src/debug
...
My do_install looks something like this
do_install () {
Install -d ${D}${libdir}
Install -c -m 555 {S}/path-to-files/libmy.so
}
Nowhere in my do_install function did I try to install files to /usr/src.
Where does this come from? And how can I get rid of it?
Thanks in advance
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Files/directories were installed but not shipped
On 19 May 2015 at 20:31, Cai, Juliet Z juliet.z@intel.com wrote:
I am getting “ERROR: QA Issue: Files/directories were installed but not
shipped” when I try to build my custom layer. It then list bunch of
directories and files under
/usr/src
/usr/src/debug
…
My do_install looks something like this
do_install () {
Install –d ${D}${libdir}
Install –c –m 555 {S}/path-to-files/libmy.so
}
Nowhere in my do_install function did I try to install files to /usr/src.
Where does this come from? And how can I get rid of it?
That's the debug source/symbols splitting happening. That directory is
usually packaged into FILES_${PN}-debug (see meta/conf/bitbake.conf), so
you must be overriding either that value, or PACKAGES so as to not have a
PN-debug package.
Ross
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
