From: Rainer Koenig <Rainer.Koenig@ts.fujitsu.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Questions from a greenhorn about build problems
Date: Wed, 19 Oct 2011 14:43:25 +0200 [thread overview]
Message-ID: <4E9EC5ED.6050503@ts.fujitsu.com> (raw)
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
next reply other threads:[~2011-10-19 12:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 12:43 Rainer Koenig [this message]
2011-10-19 13:01 ` Questions from a greenhorn about build problems Jack Mitchell
2011-10-19 14:06 ` Jack Mitchell
2011-10-19 14:59 ` Khem Raj
2011-10-19 15:49 ` William Mills
2011-10-20 7:15 ` Rainer Koenig
2011-10-20 10:01 ` William Mills
2011-10-20 10:17 ` Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E9EC5ED.6050503@ts.fujitsu.com \
--to=rainer.koenig@ts.fujitsu.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.