Skip to contentSkip to conversation

Yocto-custom kernel build issue

DISCUSSION Raghavendra Kakarla 9 participants 31 messages Jan 30, 2015 – Apr 3, 2015 2 messages not in the archive

lore
Share & tools
lore
#1 lore raw
In reply to a message not in the archive

Hi,

I am new to yocto project build system. I downloaded the yocto project build system from git. I built for the all qemu architectures(MIPS,ARM,PPC,X86) and ran on qemu.

all are working fine.

Now I need to create a bsp layer for my board which has the mips processor core.

I created the bsp layer with using the yocto-bsp create command.

here I use the my own kernel which is reside at our local git repositery. I gave this path while creating the bsplayer.

After adding my bsp layer to bblayers and my mechine to local.conf i built the kernel using bitbake -k core-image-minimal command.

While building i got the following errors:

Log data follows:

| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function do_configure
| NOTE: make oldnoconfig
| make: *** No rule to make target `oldnoconfig'.  Stop.
| NOTE: make oldconfig
| make: *** No rule to make target `oldconfig'.  Stop.
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_configure (log file is located at /home/testuser/poky/build/tmp/work/mydhanush-poky-linux/linux-yocto-custom/3.10.14+gitAUTOINC+12bbf6468e-r0/temp/log.do_configure.14044)

And also i did not got "src" folder in the following path for my mechine which is there for the qemu mips. /home/testuser/poky/build/tmp/sysroots/mydhanush/usr

could you please help for resolving this issue.

thanks in advance.

Thanks & Regards,
Raghavendra K.

#2 lore raw
Quoted 29 lines · Raghavendra Kakarla

Hi,

I am new to yocto project build system. I downloaded the yocto project build system from git. I built for the all qemu architectures(MIPS,ARM,PPC,X86) and ran on qemu.

all are working fine.

Now I need to create a bsp layer for my board which has the mips processor core.

I created the bsp layer with using the yocto-bsp create command.

here I use the my own kernel which is reside at our local git repositery. I gave this path while creating the bsplayer.

After adding my bsp layer to bblayers and my mechine to local.conf i built the kernel using bitbake -k core-image-minimal command.

While building i got the following errors:

Log data follows:

| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function do_configure
| NOTE: make oldnoconfig
| make: *** No rule to make target `oldnoconfig'.  Stop.
| NOTE: make oldconfig
| make: *** No rule to make target `oldconfig'.  Stop.
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_configure (log file is located at /home/testuser/poky/build/tmp/work/mydhanush-poky-linux/linux-yocto-custom/3.10.14+gitAUTOINC+12bbf6468e-r0/temp/log.do_configure.14044)
Quoted 2 lines

And also i did not got "src" folder in the following path for my mechine which is there for the qemu mips. /home/testuser/poky/build/tmp/sysroots/mydhanush/usr

Is the source directory in /home/testuser/poky/build/tmp/work-shared/<your machine>/kernel-source ?

And if so, is your recipe setting ${S} in any way ?

Bruce

Quoted 11 lines

could you please help for resolving this issue.

thanks in advance.

Thanks & Regards,
Raghavendra K.

#3 lore raw
In reply to Raghavendra Kakarla

Hi,
I want to add my own BSP layer to yocto and also we use our inhouse customizied kernel. I add my BSP layer to yocto using yocto-bsp create command.
I give the our curtomized kernel repositary path to the git path while creating the BSP.

After successfully creating the BSP layer when I run the "bitbake -k core-image-minimal" I got the error as follows.

Log data follows:

| DEBUG: Executing shell function do_kernel_checkout
| ERROR: S is not set to the linux source directory. Check
| ERROR: the recipe and set S to the proper extracted subdirectory
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_kernel_checkout (log file is located at /home/testuser/poky/build/tmp/work/dhruwa-poky-linux/linux-yocto-custom/3.10.14+gitAUTOINC+f91e563c45-r0/temp/log.do_kernel_checkout.11798)

could you please help for resolving this issue.

Thanks and Regards,

Raghavendra.

#4 lore raw

yocto-custom-kernel issue

Hi,
I want to add BSP layer for my mechine and I should take the our own customized kernel source(our kernel source).

For that I add the BSP layer and wrote the recipe for that.

My recipe is as follows:

*******************************************************************************************************************************************************

# This file was derived from the linux-yocto-custom.bb recipe in

# oe-core.
#
# linux-yocto-custom.bb:
#
#   A yocto-bsp-generated kernel recipe that uses the linux-yocto and
#   oe-core kernel classes to apply a subset of yocto kernel
#   management to git managed kernel repositories.
#
# Warning:
#
#   Building this kernel without providing a defconfig or BSP
#   configuration will result in build or boot errors. This is not a
#   bug.
#
# Notes:
#
#   patches: patches can be merged into to the source git tree itself,
#            added via the SRC_URI, or controlled via a BSP
#            configuration.
#
#   example configuration addition:
#            SRC_URI += "file://smp.cfg"
#   example patch addition:
#            SRC_URI += "file://0/home/testuser/yocto.git/android-linux-mti-unif-3.10.14/arch/mips/configs001-linux-version-tweak.patch
#   example feature addition:
#            SRC_URI += "file://feature.scc"
#
inherit kernel
require recipes-kernel/linux/linux-yocto.inc

SRC_URI = "git://192.168.42.75/vineethchowdhary/incdhad1-kernel-3-10.git;protocol=http;bareclone=1"

SRC_URI += "file://defconfig"

SRC_URI += "file://mydhanush.scc \
            file://mydhanush.cfg \
            file://mydhanush-user-config.cfg \
            file://mydhanush-user-patches.scc \
           "

LINUX_VERSION ?= "3.10.14"
LINUX_VERSION_EXTENSION ?= "-custom"

#SRCREV="12bbf6468e2ef179800aaab46c724f523b5002e3" SRCREV="f91e563c45d457aa441f687eda294ad899e2b25f" PR = "r0"
PV = "${LINUX_VERSION}+git${SRCPV}"

#COMPATIBLE_MACHINE_mydhanush = "mydhanush"
COMPATIBLE_MACHINE_mydhanush = "mydhanush"

***************************************************************************************************************************************************************

but I got error as follows:

Log data follows:

| DEBUG: Executing shell function do_kernel_checkout
| ERROR: S is not set to the linux source directory. Check
| ERROR: the recipe and set S to the proper extracted subdirectory
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_kernel_checkout (log file is located at /home/testuser/poky/build/tmp/work/mydhanush-poky-linux/linux-yocto-custom/3.10.14+gitAUTOINC+f91e563c45-r0/temp/log.do_kernel_checkout.11798)

could you please help for resolving this issue.

Thanks and Regards,

Raghavendra.

#5 lore raw

Re: yocto-custom-kernel issue

Hi Raghavendra,

Am 03.02.2015 um 13:40 schrieb Raghavendra Kakarla:

Quoted 40 lines

Hi,
I want to add BSP layer for my mechine and I should take the our own customized kernel source(our kernel source).

For that I add the BSP layer and wrote the recipe for that.

My recipe is as follows:

*******************************************************************************************************************************************************

# This file was derived from the linux-yocto-custom.bb recipe in

# oe-core.
#
# linux-yocto-custom.bb:
#
#   A yocto-bsp-generated kernel recipe that uses the linux-yocto and
#   oe-core kernel classes to apply a subset of yocto kernel
#   management to git managed kernel repositories.
#
# Warning:
#
#   Building this kernel without providing a defconfig or BSP
#   configuration will result in build or boot errors. This is not a
#   bug.
#
# Notes:
#
#   patches: patches can be merged into to the source git tree itself,
#            added via the SRC_URI, or controlled via a BSP
#            configuration.
#
#   example configuration addition:
#            SRC_URI += "file://smp.cfg"
#   example patch addition:
#            SRC_URI += "file://0/home/testuser/yocto.git/android-linux-mti-unif-3.10.14/arch/mips/configs001-linux-version-tweak.patch
#   example feature addition:
#            SRC_URI += "file://feature.scc"
#
inherit kernel
require recipes-kernel/linux/linux-yocto.inc
Quoted 1 line

SRC_URI = "git://192.168.42.75/vineethchowdhary/incdhad1-kernel-3-10.git;protocol=http;bareclone=1"

Why are you doing a bareclone??
Shouldn't it do a checkout to have a working copy that it can compile?

Quoted 24 lines

SRC_URI += "file://defconfig"

SRC_URI += "file://mydhanush.scc \
            file://mydhanush.cfg \
            file://mydhanush-user-config.cfg \
            file://mydhanush-user-patches.scc \
           "

LINUX_VERSION ?= "3.10.14"
LINUX_VERSION_EXTENSION ?= "-custom"

#SRCREV="12bbf6468e2ef179800aaab46c724f523b5002e3" SRCREV="f91e563c45d457aa441f687eda294ad899e2b25f" PR = "r0"
PV = "${LINUX_VERSION}+git${SRCPV}"

#COMPATIBLE_MACHINE_mydhanush = "mydhanush"
COMPATIBLE_MACHINE_mydhanush = "mydhanush"

***************************************************************************************************************************************************************

Quoted 6 lines

but I got error as follows:

Log data follows:

| DEBUG: Executing shell function do_kernel_checkout
| ERROR: S is not set to the linux source directory. Check
| ERROR: the recipe and set S to the proper extracted subdirectory

This states, that it doesn't find the source directory where it is expected. If "bareclone=1" has the effect I think it has, this is normal as there will probably only be a bare git repository insted of it's working copy.

Quoted 9 lines

| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_kernel_checkout (log file is located at /home/testuser/poky/build/tmp/work/mydhanush-poky-linux/linux-yocto-custom/3.10.14+gitAUTOINC+f91e563c45-r0/temp/log.do_kernel_checkout.11798)

could you please help for resolving this issue.

Thanks and Regards,

Raghavendra.

Cheers,
Sven

#6 lore raw

Re: yocto-custom-kernel issue

In reply to Raghavendra Kakarla
Quoted 67 lines · Raghavendra Kakarla

Hi,
I want to add BSP layer for my mechine and I should take the our own customized kernel source(our kernel source).

For that I add the BSP layer and wrote the recipe for that.

My recipe is as follows:

*******************************************************************************************************************************************************

# This file was derived from the linux-yocto-custom.bb recipe in

# oe-core.
#
# linux-yocto-custom.bb:
#
#   A yocto-bsp-generated kernel recipe that uses the linux-yocto and
#   oe-core kernel classes to apply a subset of yocto kernel
#   management to git managed kernel repositories.
#
# Warning:
#
#   Building this kernel without providing a defconfig or BSP
#   configuration will result in build or boot errors. This is not a
#   bug.
#
# Notes:
#
#   patches: patches can be merged into to the source git tree itself,
#            added via the SRC_URI, or controlled via a BSP
#            configuration.
#
#   example configuration addition:
#            SRC_URI += "file://smp.cfg"
#   example patch addition:
#            SRC_URI += "file://0/home/testuser/yocto.git/android-linux-mti-unif-3.10.14/arch/mips/configs001-linux-version-tweak.patch
#   example feature addition:
#            SRC_URI += "file://feature.scc"
#
inherit kernel
require recipes-kernel/linux/linux-yocto.inc

SRC_URI = "git://192.168.42.75/vineethchowdhary/incdhad1-kernel-3-10.git;protocol=http;bareclone=1"

SRC_URI += "file://defconfig"

SRC_URI += "file://mydhanush.scc \
             file://mydhanush.cfg \
             file://mydhanush-user-config.cfg \
             file://mydhanush-user-patches.scc \
            "

LINUX_VERSION ?= "3.10.14"
LINUX_VERSION_EXTENSION ?= "-custom"

#SRCREV="12bbf6468e2ef179800aaab46c724f523b5002e3" SRCREV="f91e563c45d457aa441f687eda294ad899e2b25f" PR = "r0"
PV = "${LINUX_VERSION}+git${SRCPV}"

#COMPATIBLE_MACHINE_mydhanush = "mydhanush"
COMPATIBLE_MACHINE_mydhanush = "mydhanush"

***************************************************************************************************************************************************************

but I got error as follows:

Quoted 8 lines

Log data follows:

| DEBUG: Executing shell function do_kernel_checkout
| ERROR: S is not set to the linux source directory. Check
| ERROR: the recipe and set S to the proper extracted subdirectory
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_kernel_checkout (log file is located at /home/testuser/poky/build/tmp/work/mydhanush-poky-linux/linux-yocto-custom/3.10.14+gitAUTOINC+f91e563c45-r0/temp/log.do_kernel_checkout.11798)

could you please help for resolving this issue.

And if dump the bitbake environment for your kernel build, what is S set to ? And when you go to that same directory on your build machine, what do you see ?

The checkout code is telling you that it doesn't see a Makefile in the source directory, so where ever it is pointing isn't valid.

Cheers,

Bruce

Quoted 5 lines

Thanks and Regards,

Raghavendra.

#7 lore raw

MIPS32r2 little endian bsp

In reply to Raghavendra Kakarla

Hi,

I need to create a bsp layer for my board which is having mips32r2 little endian processor.

I gone through the YOCTO BSP user manual bit there is no information for little endian.

When I create with the yoct-bsp command is taking the mips32 big endian only.

Could you please help me in resolving this issue.

Thanks and regards,

Raghavendra.

#8 lore raw

Re: MIPS32r2 little endian bsp

Quoted 9 lines · Raghavendra Kakarla

Hi,

I need to create a bsp layer for my board which is having mips32r2 little endian processor.

I gone through the YOCTO BSP user manual bit there is no information for little endian.

When I create with the yoct-bsp command is taking the mips32 big endian only.

Could you please help me in resolving this issue.

You will need to define a BSP that is little endian capable.

The BSP should define:

DEFAULTTUNE ?= "mips32r2el"

You can verify the setting using bitbake -e and inspecting the value of DEFAULTTUNE. The BSP should set that value -before- the necessary line:

require conf/machine/include/tune-mips32r2.inc

(Note, Little endian is not nearly as well tested as big endian for mips. I expect you will find some bugs, we'll be happy to take back any fixes for those issues.)

--Mark

Quoted 5 lines

Thanks and regards,

Raghavendra.

#9 lore raw
In reply to Raghavendra Kakarla

Hi,

I am built the yocto for my custom machine. After booting a login prompt was came. For that I tried the "root" as user name but it did not take it.

Could please tell me where i can get the login and password details for yocto rootfs.

Thanks and Regards,

Raghavendra.

#10 lore raw
Quoted 5 lines · On Tuesday 10 February 2015 13:47:45 Raghavendra Kakarla wrote:

I am built the yocto for my custom machine. After booting a login prompt was came. For that I tried the "root" as user name but it did not take it.

Could please tell me where i can get the login and password details for yocto rootfs.

The default is root with no password. If that doesn't work, do you have "debug-tweaks" in your EXTRA_IMAGE_FEATURES? It should be there by default.

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#12 lore raw
In reply to a message not in the archive

Please keep replies on the mailing list, thanks.

Is this perhaps because you extracted the files onto an SD card / other storage device as a non-root user?

Cheers,
Paul

Quoted 32 lines · On Tuesday 10 February 2015 17:55:25 Raghavendra Kakarla wrote:

Hi Paul Eggleton,

Thank you for your response.

It is the rootfs permissions issue.

I give the "chown -R root rfs" to my rfs then it is working.

Thanks and Regards,

Raghavendra.

----- Original Message -----
From: "Paul Eggleton" <[email protected]>
To: "Raghavendra Kakarla" <[email protected]>
Cc: [email protected]
Sent: Tuesday, February 10, 2015 4:30:19 PM
Subject: Re: [yocto] Yocto-custom kernel build issue

Quoted 6 lines · On Tuesday 10 February 2015 13:47:45 Raghavendra Kakarla wrote:

I am built the yocto for my custom machine. After booting a login prompt was came. For that I tried the "root" as user name but it did not take it.

Could please tell me where i can get the login and password details for yocto rootfs.

The default is root with no password. If that doesn't work, do you have "debug-tweaks" in your EXTRA_IMAGE_FEATURES? It should be there by default.

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#13 lore raw

Yes I extracted the files on to the SD card.

I have one issue now.

I want to build some packages from openWRT which are not in YOCTO in yocto build system.

For this I download the package tar files from openwrt wrote the recipe for building this tar files. Building the tar files is completed without any errors but when installing this package in the image it give some error like following.
ERROR: hostapd not found in the base feeds (dhruwa_ioe mips32r2el mips32el mipsel noarch any all).

Could you plese help in resolving this isssue.

Thanks and Regards,
Raghavendra.

----- Original Message -----
From: "Paul Eggleton" <[email protected]>
To: "Raghavendra Kakarla" <[email protected]>, [email protected]
Sent: Tuesday, February 10, 2015 7:06:37 PM
Subject: Re: [yocto] Yocto-custom kernel build issue

Please keep replies on the mailing list, thanks.

Is this perhaps because you extracted the files onto an SD card / other storage device as a non-root user?

Cheers,
Paul

Quoted 32 lines · On Tuesday 10 February 2015 17:55:25 Raghavendra Kakarla wrote:

Hi Paul Eggleton,

Thank you for your response.

It is the rootfs permissions issue.

I give the "chown -R root rfs" to my rfs then it is working.

Thanks and Regards,

Raghavendra.

----- Original Message -----
From: "Paul Eggleton" <[email protected]>
To: "Raghavendra Kakarla" <[email protected]>
Cc: [email protected]
Sent: Tuesday, February 10, 2015 4:30:19 PM
Subject: Re: [yocto] Yocto-custom kernel build issue

Quoted 6 lines · On Tuesday 10 February 2015 13:47:45 Raghavendra Kakarla wrote:

I am built the yocto for my custom machine. After booting a login prompt was came. For that I tried the "root" as user name but it did not take it.

Could please tell me where i can get the login and password details for yocto rootfs.

The default is root with no password. If that doesn't work, do you have "debug-tweaks" in your EXTRA_IMAGE_FEATURES? It should be there by default.

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#14 lore raw
Quoted 1 line · On Wednesday 11 February 2015 10:25:51 Raghavendra Kakarla wrote:

Yes I extracted the files on to the SD card.

Right, and the lesson is you must do that as root, not as a normal user.

Quoted 8 lines

I want to build some packages from openWRT which are not in YOCTO in yocto build system.

For this I download the package tar files from openwrt wrote the recipe for building this tar files. Building the tar files is completed without any errors but when installing this package in the image it give some error like following. ERROR: hostapd not found in the base feeds (dhruwa_ioe mips32r2el mips32el mipsel noarch any all).

My advice here is to use the recipe we already have in the community to build this:

http://layers.openembedded.org/layerindex/branch/master/recipes/?q=hostapd

In general the OE layer index is the best place to find layers providing recipes to build anything that isn't already supplied in Poky/OE-core by default.

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#15 lore raw

Thanks Paul,

I will make use of hostapd recipe present in the openembedded layer.

cheers,
Raghavendra.

----- Original Message -----
From: "Paul Eggleton" <[email protected]>
To: "Raghavendra Kakarla" <[email protected]>
Cc: [email protected]
Sent: Wednesday, February 11, 2015 3:00:57 PM
Subject: Re: [yocto] Yocto-custom kernel build issue

Quoted 1 line · On Wednesday 11 February 2015 10:25:51 Raghavendra Kakarla wrote:

Yes I extracted the files on to the SD card.

Right, and the lesson is you must do that as root, not as a normal user.

Quoted 8 lines

I want to build some packages from openWRT which are not in YOCTO in yocto build system.

For this I download the package tar files from openwrt wrote the recipe for building this tar files. Building the tar files is completed without any errors but when installing this package in the image it give some error like following. ERROR: hostapd not found in the base feeds (dhruwa_ioe mips32r2el mips32el mipsel noarch any all).

My advice here is to use the recipe we already have in the community to build this:

http://layers.openembedded.org/layerindex/branch/master/recipes/?q=hostapd

In general the OE layer index is the best place to find layers providing recipes to build anything that isn't already supplied in Poky/OE-core by default.

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#16 lore raw

SDK generation issue

Hi Paul Eggleton,
Thanks for your help in the solving the issue for adding the bsp to yocto. Now I am working on the yocto sdk generation.

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

but i got the following errors:
**************************************************************************************************************************************************
/opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find crt1.o: No such file or directory /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find crti.o: No such file or directory /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find crtbegin.o: No such file or directory /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find -lgcc /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find -lgcc_s /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find -lc /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find -lgcc /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find -lgcc_s /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find crtend.o: No such file or directory /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find crtn.o: No such file or directory
collect2: error: ld returned 1 exit status

***********************************************************************************************************************************************************
Please help me to resolving this issue.

Thanks in advance.

Cheers,

Raghavendra Kakarla.

#17 lore raw

Re: SDK generation issue

Quoted 12 lines · 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.

Quoted 8 lines

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

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#18 lore raw

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 <[email protected]>
Sent: Tuesday, March 3, 2015 3:07 PM
To: Raghavendra Kakarla
Cc: [email protected]
Subject: Re: SDK generation issue

Quoted 12 lines · 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.

Quoted 8 lines

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

#19 lore raw

Re: SDK generation issue

Quoted 5 lines · On Tuesday 03 March 2015 10:26:46 Raghavendra Kakarla wrote:

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)

The SDK will contain all libraries, headers and debugging symbols for the contents of the image specified with -c populate_sdk. It won't contain any documentation by default, though you could add it by setting SDKIMAGE_FEATURES e.g.

SDKIMAGE_FEATURES = "dev-pkgs dbg-pkgs doc-pkgs"

(the default value set with ??= is "dev-pkgs dbg-pkgs")

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#20 lore raw

Re: SDK generation issue

In reply to Raghavendra Kakarla

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: [email protected]
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 <[email protected]>
Sent: Tuesday, March 3, 2015 3:07 PM
To: Raghavendra Kakarla
Cc: [email protected]
Subject: Re: SDK generation issue

Quoted 12 lines · 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.

Quoted 8 lines

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

#21 lore raw

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. <sdk-install-dir>/sysroots/<your-machine-arch>/usr/share/doc/

Quoted 70 lines · 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: [email protected]
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 <[email protected]>
Sent: Tuesday, March 3, 2015 3:07 PM
To: Raghavendra Kakarla
Cc: [email protected]
Subject: Re: SDK generation issue

Quoted 13 lines · 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.

Quoted 8 lines

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

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#22 lore raw

Re: SDK generation issue

Hi Paul Eggleton,

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

Regards,
Raghavendra.
________________________________________
From: Paul Eggleton <[email protected]>
Sent: Tuesday, March 3, 2015 5:40 PM
To: Raghavendra Kakarla
Cc: [email protected]
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. <sdk-install-dir>/sysroots/<your-machine-arch>/usr/share/doc/

Quoted 62 lines · 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: [email protected]
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 <[email protected]>
Sent: Tuesday, March 3, 2015 3:07 PM
To: Raghavendra Kakarla
Cc: [email protected]
Subject: Re: SDK generation issue

Quoted 13 lines · 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.

Quoted 8 lines

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.

Quoted 8 lines

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre

--

Paul Eggleton
Intel Open Source Technology Centre

#23 lore raw

Re: SDK generation issue

Maybe, it depends on the individual projects. We haven't embarked upon any documentation standardisation effort.

Quoted 96 lines · On Tuesday 03 March 2015 12:17:45 Raghavendra Kakarla wrote:

Hi Paul Eggleton,

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

Regards,
Raghavendra.
________________________________________
From: Paul Eggleton <[email protected]>
Sent: Tuesday, March 3, 2015 5:40 PM
To: Raghavendra Kakarla
Cc: [email protected]
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. <sdk-install-dir>/sysroots/<your-machine-arch>/usr/share/doc/

Quoted 65 lines · 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: [email protected]
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 <[email protected]>
Sent: Tuesday, March 3, 2015 3:07 PM
To: Raghavendra Kakarla
Cc: [email protected]
Subject: Re: SDK generation issue

Quoted 19 lines · 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.

Quoted 4 lines

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.

Quoted 8 lines

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre

--

Paul Eggleton
Intel Open Source Technology Centre

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#32 lore raw

Re: SDK generation issue

In reply to Raghavendra Kakarla

Try doing:

${CC} test.c

This will invoke the cross compiler with all the compilation flags required to produce an executable for the target, using libraries on the target root file system.

________________________________________
From: Raghavendra Kakarla [[email protected]]
Sent: Monday, March 02, 2015 10:41 PM
To: Paul Eggleton
Cc: [email protected]
Subject: [yocto] SDK generation issue

Hi Paul Eggleton,
Thanks for your help in the solving the issue for adding the bsp to yocto. Now I am working on the yocto sdk generation.

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

but i got the following errors:
**************************************************************************************************************************************************
/opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find crt1.o: No such file or directory /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find crti.o: No such file or directory /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find crtbegin.o: No such file or directory /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find -lgcc /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find -lgcc_s /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find -lc /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find -lgcc /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find -lgcc_s /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find crtend.o: No such file or directory /opt/poky/1.7/sysroots/x86_64-pokysdk-linux/usr/libexec/mipsel-poky-linux/gcc/mipsel-poky-linux/4.9.1/ld: cannot find crtn.o: No such file or directory
collect2: error: ld returned 1 exit status

***********************************************************************************************************************************************************
Please help me to resolving this issue.

Thanks in advance.

Cheers,

Raghavendra Kakarla.

#24 lore raw

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

In reply to 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: [email protected]
Subject: RE: SDK generation issue

Hi Paul Eggleton,

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

Regards,
Raghavendra.
________________________________________
From: Paul Eggleton <[email protected]>
Sent: Tuesday, March 3, 2015 5:40 PM
To: Raghavendra Kakarla
Cc: [email protected]
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. <sdk-install-dir>/sysroots/<your-machine-arch>/usr/share/doc/

Quoted 62 lines · 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: [email protected]
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 <[email protected]>
Sent: Tuesday, March 3, 2015 3:07 PM
To: Raghavendra Kakarla
Cc: [email protected]
Subject: Re: SDK generation issue

Quoted 13 lines · 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.

Quoted 8 lines

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.

Quoted 8 lines

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre

--

Paul Eggleton
Intel Open Source Technology Centre

#25 lore raw

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

Quoted 9 lines · 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.

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.

Quoted 107 lines

Thanks and Regards,
Raghavendra Kakarla__________________________________
______
From: Raghavendra Kakarla
Sent: Tuesday, March 3, 2015 5:47 PM
To: Paul Eggleton
Cc: [email protected]
Subject: RE: SDK generation issue

Hi Paul Eggleton,

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

Regards,
Raghavendra.
________________________________________
From: Paul Eggleton <[email protected]>
Sent: Tuesday, March 3, 2015 5:40 PM
To: Raghavendra Kakarla
Cc: [email protected]
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. <sdk-install-dir>/sysroots/<your-machine-arch>/usr/share/doc/

Quoted 62 lines · 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: [email protected]
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 <[email protected]>
Sent: Tuesday, March 3, 2015 3:07 PM
To: Raghavendra Kakarla
Cc: [email protected]
Subject: Re: SDK generation issue

Quoted 13 lines · 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.

Quoted 8 lines

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.

Quoted 8 lines

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre

--

Paul Eggleton
Intel Open Source Technology Centre

Signature · 4 lines
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
#26 lore raw

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

Quoted 26 lines · Khem Raj
Quoted 4 lines

On Mar 9, 2015, at 9:21 PM, Raghavendra Kakarla

Quoted 3 lines · <[email protected]> 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?

Quoted 2 lines

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.

Quoted 10 lines

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.

Quoted 3 lines

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

Quoted 119 lines
Quoted 19 lines

From: Raghavendra Kakarla
Sent: Tuesday, March 3, 2015 5:47 PM
To: Paul Eggleton
Cc: [email protected]
Subject: RE: SDK generation issue

Hi Paul Eggleton,

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

Regards,
Raghavendra.
________________________________________
From: Paul Eggleton <[email protected]>
Sent: Tuesday, March 3, 2015 5:40 PM
To: Raghavendra Kakarla
Cc: [email protected]
Subject: Re: SDK generation issue

Quoted 27 lines

Assuming you built the SDK you had installed with "doc-pkgs" in SDKIMAGE_FEATURES, they would be in the target sysroot i.e. <sdk-install-dir>/sysroots/<your-machine-arch>/usr/share/doc/

Quoted 22 lines · 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: [email protected]
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.

Quoted 1 line
Quoted 1 line

With which i am able to build the applications for my platform. I

wanted to

Quoted 1 line
Quoted 1 line

confirm, whether SDK means a toolchain to build the applications or

is

Quoted 1 line
Quoted 1 line

there something more (such as documentation, libraries, etc

generated for

Quoted 11 lines
Quoted 11 lines

our platform)

Regards,
Raghavendra.

From: Paul Eggleton <[email protected]>
Sent: Tuesday, March 3, 2015 3:07 PM
To: Raghavendra Kakarla
Cc: [email protected]
Subject: Re: SDK generation issue

Quoted 3 lines
Quoted 3 lines · On Tuesday 03 March 2015 05:41:43 Raghavendra Kakarla wrote:
Quoted 2 lines

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

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

to
generte the installation script file and .manifest file.

I run the installation script file. After running installation

script file

Quoted 9 lines
Quoted 9 lines
Quoted 9 lines

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

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

the correct path.

After this i built wrote a small example and try to build with the

sdk

Quoted 5 lines
Quoted 5 lines
Quoted 3 lines

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

Quoted 20 lines
Quoted 10 lines

options.

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre

--

Paul Eggleton
Intel Open Source Technology Centre

Signature · 4 lines
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Signature · 4 lines
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Signature · 1 line
Sent from my Android device with K-9 Mail. Please excuse my brevity.
#27 lore raw

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

In reply to Raghavendra Kakarla

Hi Paul Eggleton,

Is it kernel is must be a git repository code for building in the yocto?

When i gave my custom kernel which is not a git repository code and it is in my development PC, i got invalid SRCREV number error. But when give the same kernel from the git repository it is working.
Can you please help me in resolving this error.

Cheers,
Raghavendra K.
________________________________________
From: Raghavendra Kakarla
Sent: Tuesday, March 10, 2015 9:51 AM
To: Paul Eggleton
Cc: [email protected]
Subject: Difference b/w yocto kernels and normal linux.org kernels

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: [email protected]
Subject: RE: SDK generation issue

Hi Paul Eggleton,

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

Regards,
Raghavendra.
________________________________________
From: Paul Eggleton <[email protected]>
Sent: Tuesday, March 3, 2015 5:40 PM
To: Raghavendra Kakarla
Cc: [email protected]
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. <sdk-install-dir>/sysroots/<your-machine-arch>/usr/share/doc/

Quoted 62 lines · 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: [email protected]
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 <[email protected]>
Sent: Tuesday, March 3, 2015 3:07 PM
To: Raghavendra Kakarla
Cc: [email protected]
Subject: Re: SDK generation issue

Quoted 13 lines · 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.

Quoted 8 lines

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.

Quoted 8 lines

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre

--

Paul Eggleton
Intel Open Source Technology Centre

#28 lore raw

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

Quoted 6 lines · On Friday 13 March 2015 08:14:13 Raghavendra Kakarla wrote:

Is it kernel is must be a git repository code for building in the yocto?

When i gave my custom kernel which is not a git repository code and it is in my development PC, i got invalid SRCREV number error. But when give the same kernel from the git repository it is working. Can you please help me in resolving this error.

If you want to use your own non-git sources you are moving further away from how the linux-yocto recipe works. If you have not already I would suggest using linux-yocto-custom as described in our kernel development manual:

http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#working-with-your-own-sources

Note that you must not have SRCPV included in the recipe's value of PV, or you will get the error you mentioned.

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#29 lore raw

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

Hi Paul,

I hope you don't mind me asking a question slightly out of topic. I would like to know if there is a recipe for linux kernel 3.19 for dizzy branch (intel x64). Thanks.

Regards,
Albert.

Quoted 29 lines · Paul Eggleton
Quoted 6 lines · On Friday 13 March 2015 08:14:13 Raghavendra Kakarla wrote:

Is it kernel is must be a git repository code for building in the yocto?

When i gave my custom kernel which is not a git repository code and it is in my development PC, i got invalid SRCREV number error. But when give the same kernel from the git repository it is working. Can you please help me in resolving this error.

If you want to use your own non-git sources you are moving further away from how the linux-yocto recipe works. If you have not already I would suggest using linux-yocto-custom as described in our kernel development manual:

http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#working-with-your-own-sources

Note that you must not have SRCPV included in the recipe's value of PV, or you will get the error you mentioned.

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#30 lore raw

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

Quoted 3 lines · On Friday 13 March 2015 17:05:29 Albert K wrote:

I hope you don't mind me asking a question slightly out of topic. I would like to know if there is a recipe for linux kernel 3.19 for dizzy branch (intel x64). Thanks.

No, not out of the box - 3.19 wasn't available at the time dizzy (1.7) was branched and we don't generally backport upgrades. That said it should be fairly easy to build your own newer kernel by adding your own recipe to do so (though there may possibly be user-space compatibility issues you need to resolve as a result - I'm no expert there).

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#31 lore raw

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

In reply to Paul Eggleton

Hi Paul Eggleton,

I have some doubts on the SDK and build errors.

Could you please clarify my doubts.

1. Can we get the consolidated log/file for total installed packages for corresponding SDK. If user wants to know what packages are included in the SDK.

2. When trying to build the images always getting a error saying that clean things in kernel path in build error log, then we goto that path run command "make mrproper" then it is working fine.

Thanks and Regards,
Raghavendra K.

________________________________________
From: Paul Eggleton <[email protected]>
Sent: Friday, March 13, 2015 2:23 PM
To: Raghavendra Kakarla
Cc: [email protected]
Subject: Re: Difference b/w yocto kernels and normal linux.org kernels

Quoted 6 lines · On Friday 13 March 2015 08:14:13 Raghavendra Kakarla wrote:

Is it kernel is must be a git repository code for building in the yocto?

When i gave my custom kernel which is not a git repository code and it is in my development PC, i got invalid SRCREV number error. But when give the same kernel from the git repository it is working. Can you please help me in resolving this error.

If you want to use your own non-git sources you are moving further away from how the linux-yocto recipe works. If you have not already I would suggest using linux-yocto-custom as described in our kernel development manual:

http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#working-with-your-own-sources

Note that you must not have SRCPV included in the recipe's value of PV, or you will get the error you mentioned.

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre