Questions from a greenhorn about build problems

Hi all,

I'm using yoctoproject since one week now and got the latest yocto-1.1/edison-6.0 git tree. I have been able to build core-image-sato for the Beagleboard xM rev. A and the image works fine.

Now my next goal is to build an image for the TI 8148 EVM board. Since Yocto is based on OE-core I thought it was a good idea to get the meta-texasinstruments layer that is listed in the OE wiki:
http://www.openembedded.org/wiki/LayerIndex

So I cloned my git tree for meta-texasinstruments from
git://git.angstrom-distribution.org/meta-texasinstruments

and looked a bit around in that. conf/machine shows a conf for c6a814x-evm so I replaced the machine "beagleboard" with "c6a814x-evm" in my local conf.

I started bitbake -k core-image-sato and after builing around 4100 of the 4221 recipes I got an error on a kernel tree from the arago-project and from the u-boot compilation. I guess the second error occurs because of the first error, so I had a better look at the first error.

The buildstats for this packet show, that fetch failed. I tried to fetch the SRC_URL by hand and it worked without any problem. Note: I'm behind a firewall, so to clone git://... I need to go over a SOCKS proxy. Therefore I created an /etc/gitconfig that works fine and the downloads show, that lots of git-repos from the yocto recipes worked without any probem, but now those from the meta-texasinstruments layer seem not to work. I tried a bit around with bitbake -b -D and saw long commandlines with lots of export before.

It exports a GIT_CONFIG which points to
poky/tmp/sysroots/x86_64linux/usr/etc/gitconfig.

First I replaced this gitconfig with my own gitconfig from /etc, but that didn't work. Looking at the file structure there it seems that ../sysroots/x86_64linux/ is chroot'ed somehow so I put gitconfig under that chroot's /etc and now it seems that fetch is working.

So stupid question: Is there a documentation that explains how that build process is working on the machine/script level and why are the recipes from yocto behaving different than to the ones that I imported with the meta-texasinstruments layer?

Best regards
Rainer

Quoted 40 lines · Rainer Koenig

Hi all,

I'm using yoctoproject since one week now and got the latest yocto-1.1/edison-6.0 git tree. I have been able to build core-image-sato for the Beagleboard xM rev. A and the image works fine.

Now my next goal is to build an image for the TI 8148 EVM board. Since Yocto is based on OE-core I thought it was a good idea to get the meta-texasinstruments layer that is listed in the OE wiki:
http://www.openembedded.org/wiki/LayerIndex

So I cloned my git tree for meta-texasinstruments from
git://git.angstrom-distribution.org/meta-texasinstruments

and looked a bit around in that. conf/machine shows a conf for c6a814x-evm so I replaced the machine "beagleboard" with "c6a814x-evm" in my local conf.

I started bitbake -k core-image-sato and after builing around 4100 of the 4221 recipes I got an error on a kernel tree from the arago-project and from the u-boot compilation. I guess the second error occurs because of the first error, so I had a better look at the first error.

The buildstats for this packet show, that fetch failed. I tried to fetch the SRC_URL by hand and it worked without any problem. Note: I'm behind a firewall, so to clone git://... I need to go over a SOCKS proxy. Therefore I created an /etc/gitconfig that works fine and the downloads show, that lots of git-repos from the yocto recipes worked without any probem, but now those from the meta-texasinstruments layer seem not to work. I tried a bit around with bitbake -b -D and saw long commandlines with lots of export before.

It exports a GIT_CONFIG which points to
poky/tmp/sysroots/x86_64linux/usr/etc/gitconfig.

First I replaced this gitconfig with my own gitconfig from /etc, but that didn't work. Looking at the file structure there it seems that ../sysroots/x86_64linux/ is chroot'ed somehow so I put gitconfig under that chroot's /etc and now it seems that fetch is working.

Quoted 7 lines

So stupid question: Is there a documentation that explains how that build process is working on the machine/script level and why are the recipes from yocto behaving different than to the ones that I imported with the meta-texasinstruments layer?

Best regards
Rainer

Hi Rainer,

Welcome to Yocto, I'm pleased you took my advice and are having a bit more luck than you were with pure openembedded! There is a Wiki article with some information about building behind a proxy (https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy) this has been discussed in length recently and lots of changes have come into place. I am sure someone more knowlegdeable then me will be along soon but there is lots of discussion on the subject here on the mailing list and elsewhere.

Cheers,
Jack.
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Hi all,

I'm using yoctoproject since one week now and got the latest yocto-1.1/edison-6.0 git tree. I have been able to build core-image-sato for the Beagleboard xM rev. A and the image works fine.

Now my next goal is to build an image for the TI 8148 EVM board. Since Yocto is based on OE-core I thought it was a good idea to get the meta-texasinstruments layer that is listed in the OE wiki:
http://www.openembedded.org/wiki/LayerIndex

So I cloned my git tree for meta-texasinstruments from
git://git.angstrom-distribution.org/meta-texasinstruments

and looked a bit around in that. conf/machine shows a conf for c6a814x-evm so I replaced the machine "beagleboard" with "c6a814x-evm" in my local conf.

I started bitbake -k core-image-sato and after builing around 4100 of the 4221 recipes I got an error on a kernel tree from the arago-project and from the u-boot compilation. I guess the second error occurs because of the first error, so I had a better look at the first error.

The buildstats for this packet show, that fetch failed. I tried to fetch the SRC_URL by hand and it worked without any problem. Note: I'm behind a firewall, so to clone git://... I need to go over a SOCKS proxy. Therefore I created an /etc/gitconfig that works fine and the downloads show, that lots of git-repos from the yocto recipes worked without any probem, but now those from the meta-texasinstruments layer seem not to work. I tried a bit around with bitbake -b -D and saw long commandlines with lots of export before.

It exports a GIT_CONFIG which points to
poky/tmp/sysroots/x86_64linux/usr/etc/gitconfig.

First I replaced this gitconfig with my own gitconfig from /etc, but that didn't work. Looking at the file structure there it seems that ../sysroots/x86_64linux/ is chroot'ed somehow so I put gitconfig under that chroot's /etc and now it seems that fetch is working.

So stupid question: Is there a documentation that explains how that build process is working on the machine/script level and why are the recipes from yocto behaving different than to the ones that I imported with the meta-texasinstruments layer?

Best regards
Rainer

Hi all,

I'm using yoctoproject since one week now and got the latest yocto-1.1/edison-6.0 git tree. I have been able to build core-image-sato for the Beagleboard xM rev. A and the image works fine.

Now my next goal is to build an image for the TI 8148 EVM board. Since Yocto is based on OE-core I thought it was a good idea to get the meta-texasinstruments layer that is listed in the OE wiki:
http://www.openembedded.org/wiki/LayerIndex

So I cloned my git tree for meta-texasinstruments from
git://git.angstrom-distribution.org/meta-texasinstruments

and looked a bit around in that. conf/machine shows a conf for c6a814x-evm so I replaced the machine "beagleboard" with "c6a814x-evm" in my local conf.

I started bitbake -k core-image-sato and after builing around 4100 of the 4221 recipes I got an error on a kernel tree from the arago-project and from the u-boot compilation. I guess the second error occurs because of the first error, so I had a better look at the first error.

The buildstats for this packet show, that fetch failed. I tried to fetch the SRC_URL by hand and it worked without any problem. Note: I'm behind a firewall, so to clone git://... I need to go over a SOCKS proxy. Therefore I created an /etc/gitconfig that works fine and the downloads show, that lots of git-repos from the yocto recipes worked without any probem, but now those from the meta-texasinstruments layer seem not to work. I tried a bit around with bitbake -b -D and saw long commandlines with lots of export before.

It exports a GIT_CONFIG which points to
poky/tmp/sysroots/x86_64linux/usr/etc/gitconfig.

First I replaced this gitconfig with my own gitconfig from /etc, but that didn't work. Looking at the file structure there it seems that ../sysroots/x86_64linux/ is chroot'ed somehow so I put gitconfig under that chroot's /etc and now it seems that fetch is working.

So stupid question: Is there a documentation that explains how that build process is working on the machine/script level and why are the recipes from yocto behaving different than to the ones that I imported with the meta-texasinstruments layer?

Best regards
Rainer

I think your probably running a bit ahead of us.

Keep in mind that at this point meta-texasinstruments has not been tested with the poky layer stack. It is a work in progress and is being tested with a layer stack that includes oe-core + meta-oe + meta-angstrom.

It is certainly in scope for meta-ti (new name) to work w/ a stock poky release or snapshot, were just not verified that yet. As of now our plan includes building and testing the following layer combinations:

oe-core + meta-ti
oe-core + meta-ti + meta-openembedded + meta-angstrom poky + meta-ti
oe-core + meta-ti + meta-openembedded + meta-arago <= TI SDKs

I would encourage you to subscribe to our brand spanking new meta-ti mailing list to discuss, monitor and prod.

I don't think any of this explains why you are having proxy issues and we will let the rest of the thread play out for that. I just wanted to set your expectations.

Hi William,

Quoted 1 line

I think your probably running a bit ahead of us.

Yes, looks like. :-) Well, my goal is to be able to build a small embedded Linux distribution for ARM based SoC boards. Currently we have the Beagleboard and the TI 8148 EVM to test, but sooner or later there will be another board available.

Quoted 3 lines

Keep in mind that at this point meta-texasinstruments has not been tested with the poky layer stack. It is a work in progress and is being tested with a layer stack that includes oe-core + meta-oe + meta-angstrom.

Yes. I just tried out and ran into problems, that's what makes a developers life challenging. ;-) I really don't mind about problems as long as I have hope to fix them.

Quoted 8 lines

It is certainly in scope for meta-ti (new name) to work w/ a stock poky release or snapshot, were just not verified that yet. As of now our plan includes building and testing the following layer combinations:

oe-core + meta-ti
oe-core + meta-ti + meta-openembedded + meta-angstrom poky + meta-ti
oe-core + meta-ti + meta-openembedded + meta-arago<= TI SDKs

Looks good, even that I faild in playing around with oe-core. One thing that made me fail could be the SOCKS problem that I solved now. Maybe I give it another test run. Anyway, yocto seems to fit perfectly for my needs since its well documented and gave me some success events.

Quoted 3 lines

I would encourage you to subscribe to our brand spanking new meta-ti mailing list to discuss, monitor and prod.

Ok, I subscribed to that list too.

Quoted 3 lines

I don't think any of this explains why you are having proxy issues and we will let the rest of the thread play out for that. I just wanted to set your expectations.

That's ok. Looks like the proxy issue is solved and my next obstacle in the way to success is called u-boot_git.bb. So far I see that this recipe fails during configure because it wants to make with a rule "ti8148_evm_config_nand" that is not available in the u-boot sources that we currently get from git.denx.de.

On the other hand I have the TI EZSDK kit available and there is an u-boot version shipped that covers the TI8148 EVM board, so I guess all I have to do is to include those sources in the meta-ti layer so that u-boot will also build for my TI8148 EVM.

Well, I keep on testing and trying things out. Still new to the embedded world after many years of desktop Linux.

Regards
Rainer

I'm using yoctoproject since one week now and got the latest yocto-1.1/edison-6.0 git tree. I have been able to build core-image-sato for the Beagleboard xM rev. A and the image works fine.

Now my next goal is to build an image for the TI 8148 EVM board. Since Yocto is based on OE-core I thought it was a good idea to get the meta-texasinstruments layer that is listed in the OE wiki:
http://www.openembedded.org/wiki/LayerIndex

So I cloned my git tree for meta-texasinstruments from
git://git.angstrom-distribution.org/meta-texasinstruments

and looked a bit around in that. conf/machine shows a conf for c6a814x-evm so I replaced the machine "beagleboard" with "c6a814x-evm" in my local conf.

I started bitbake -k core-image-sato and after builing around 4100 of the 4221 recipes I got an error on a kernel tree from the arago-project and from the u-boot compilation. I guess the second error occurs because of the first error, so I had a better look at the first error.

The buildstats for this packet show, that fetch failed. I tried to fetch the SRC_URL by hand and it worked without any problem. Note: I'm behind a firewall, so to clone git://... I need to go over a SOCKS proxy. Therefore I created an /etc/gitconfig that works fine and the downloads show, that lots of git-repos from the yocto recipes worked without any probem, but now those from the meta-texasinstruments layer seem not to work. I tried a bit around with bitbake -b -D and saw long commandlines with lots of export before.

It exports a GIT_CONFIG which points to
poky/tmp/sysroots/x86_64linux/usr/etc/gitconfig.

First I replaced this gitconfig with my own gitconfig from /etc, but that didn't work. Looking at the file structure there it seems that ../sysroots/x86_64linux/ is chroot'ed somehow so I put gitconfig under that chroot's /etc and now it seems that fetch is working.

So stupid question: Is there a documentation that explains how that build process is working on the machine/script level and why are the recipes from yocto behaving different than to the ones that I imported with the meta-texasinstruments layer?