Re: Questions from a greenhorn about build problems

[William Mills <wmills@ti.com>]

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