Questions from a greenhorn about build problems

Questions from a greenhorn about build problems

[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.

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
-- 
Dipl.-Inf. (FH) Rainer Koenig
Project Manager Linux Clients
Dept. PDG WPS R&D SW OSE

Fujitsu Technology Solutions
Bürgermeister-Ullrich-Str. 100
86199 Augsburg
Germany

Telephone: +49-821-804-3321
Telefax:   +49-821-804-2131
Mail:      mailto:Rainer.Koenig@ts.fujitsu.com

Internet         ts.fujtsu.com
Company Details  ts.fujitsu.com/imprint.html

Re: Questions from a greenhorn about build problems

[Jack Mitchell]

On 19/10/2011 13:43, Rainer Koenig wrote:
> 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 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.

Re: Questions from a greenhorn about build problems

[Jack Mitchell]

On 19/10/2011 14:01, Jack Mitchell wrote:
> On 19/10/2011 13:43, Rainer Koenig wrote:
>> 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 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
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Further reading: 
http://www.yoctoproject.org/blogs/sgarman/2011/proxy-problem

Re: Questions from a greenhorn about build problems

[Khem Raj]

On 10/19/2011 5:43 AM, Rainer Koenig wrote:
> 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?

they should not behave differently but since kernels and uboot are 
machine specific they will be different and might have fetching problems

Read through meta/conf/site.conf.sample there it lists how to use SOCKS


>
> Best regards
> Rainer

Re: Questions from a greenhorn about build problems

[William Mills]

On 10/19/2011 08:43 AM, Rainer Koenig wrote:
> 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.

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

[layer names and order not to scale]

We will keep a mirror of meta-ti active at the angstrom URL are using so 
no worries.  We are also working to publish a mirror on yoctoproject.org.

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

https://lists.yoctoproject.org/listinfo/

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.

>
> 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

Re: Questions from a greenhorn about build problems

[Rainer Koenig]

Hi William,

> 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.

> 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.

> 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.

> 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.

> 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
-- 
Dipl.-Inf. (FH) Rainer Koenig
Project Manager Linux Clients
Dept. PDG WPS R&D SW OSE

Fujitsu Technology Solutions
Bürgermeister-Ullrich-Str. 100
86199 Augsburg
Germany

Telephone: +49-821-804-3321
Telefax:   +49-821-804-2131
Mail:      mailto:Rainer.Koenig@ts.fujitsu.com

Internet         ts.fujtsu.com
Company Details  ts.fujitsu.com/imprint.html

Re: Questions from a greenhorn about build problems

[William Mills]

On 10/20/2011 03:15 AM, Rainer Koenig wrote:
> Hi William,
>
>> 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.
>
>> 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.
>
>> 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.

For you or any one else listing I should mention that TI SDKs today are 
still based on oe classic.  The layers we use for these are always 
publicly available at http://arago-project.org

If you need something that has been tested by TI today, you may want to 
look there.  If your willing to work through a few bumps and want to 
start on the new baseline then we would be happy to work with you on 
poky/oe-core + meta-ti.

We expect meta-ti to have some boards tested to the above layer stacks 
in November and most/all boards working by the end of the year.  The 
first TI SDKs built from the new structure will be in Q1 2012.

>
>> 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.
>
>> 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.
>

Humm,  I need to be careful or I may sound like I know what I am doing. 
  However, a quick look[1] makes me think that AM8148 should be using 
u-boot_2010.06-psp.

[1] 
http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/recipes-bsp/u-boot/u-boot_2010.06-psp.bb

There are few things that could be going wrong.  Why don't you move this 
thread to meta-ti and Denys and Koen should be able to help you.

> 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

Re: Questions from a greenhorn about build problems

[Richard Purdie]

On Wed, 2011-10-19 at 14:43 +0200, Rainer Koenig wrote:
> 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?

The Yocto recipes are mirrored on the Yocto servers and can be fetched
over http://. Its likely the build therefore actually needed to touch
the git protocol. In the case of the TI layer, those recipes are not
cached on the Yocto mirror and hence it needed to fetch them over git.

That would at least explain the change in behaviour.

Cheers,

Richard