From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: build error pandaboard on master
Date: Fri, 03 Aug 2012 07:24:54 -0600 [thread overview]
Message-ID: <501BD126.5060100@mlbassoc.com> (raw)
In-Reply-To: <CANwz6nwYGvD2Mn9grjTDp2D9BpD7Uv218-noNtRTMYLQSA4EKQ@mail.gmail.com>
On 2012-08-03 07:19, Edward Vidal wrote:
> Hello,
> I too am interested in the pandaboard with yacto.
> I added meta-ti to conf/bblayes.conf
> I have tried master and git branch 30fb40.
> Did you have to make any changes to meta-ti?
> I get the following
> MACHINE=pandaboard bitbake -v core-image-sato
> Pseudo is not present but is required, building this first before the main build
> DEBUG: Removed the following variables from the environment: LESSOPEN, CVS_RSH, XDG_SEAT, XDG_VTNR, CCACHE_HASHDIR, SHLVL, HISTSIZE, BBFETCH2, XDG_RUNTIME_DIR,
> QT_GRAPHICSSYSTEM_CHECKED, XDG_SESSION_ID, BUILDDIR, HOSTNAME, HISTCONTROL, MAIL, LS_COLORS
> DEBUG: Found bblayers.conf (/home/ame/poky/build/conf/bblayers.conf)
> DEBUG: LOAD /home/ame/poky/build/conf/bblayers.conf
> DEBUG: Adding layer /home/vidal/poky/meta
> DEBUG: LOAD /home/vidal/poky/meta/conf/layer.conf
> DEBUG: Adding layer /home/vidal/poky/meta-yocto
> DEBUG: LOAD /home/vidal/poky/meta-yocto/conf/layer.conf
> DEBUG: Adding layer /home/vidal/poky/meta-ti
> DEBUG: LOAD /home/vidal/poky/meta-ti/conf/layer.conf
> ERROR: Unable to parse /home/vidal/poky/meta-ti/conf/layer.conf: [Errno 2] No such file or directory: '/home/vidal/poky/meta-ti/conf/layer.conf'
> Any help will be appreciated.
> thanks
Did you actually download meta-ti into your /home/vidal/poky tree?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2012-08-03 13:24 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 13:19 build error pandaboard on master Edward Vidal
2012-08-03 13:24 ` Gary Thomas [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-03 14:37 Edward Vidal
2012-08-03 15:08 ` Edward Vidal
2012-08-03 13:59 Edward Vidal
2012-08-03 14:06 ` Gary Thomas
2012-08-02 17:07 maniacbug
2012-08-02 17:21 ` Jim Abernathy
2012-08-02 20:22 ` Elvis Dowson
2012-08-01 18:59 maniacbug
2012-08-02 12:47 ` Jim Abernathy
2012-08-02 15:03 ` Jim Abernathy
2012-07-30 12:53 Jim Abernathy
2012-07-30 13:00 ` Martin Jansa
2012-07-30 13:06 ` Jim Abernathy
2012-07-30 13:19 ` Martin Jansa
2012-07-30 13:21 ` Martin Jansa
2012-07-30 13:57 ` Jim Abernathy
2012-07-30 13:15 ` Gary Thomas
2012-07-30 13:48 ` Jim Abernathy
2012-07-30 13:56 ` Gary Thomas
2012-07-30 14:11 ` Jim Abernathy
2012-07-30 14:21 ` Gary Thomas
2012-07-30 14:31 ` Jim Abernathy
2012-07-30 16:50 ` Jim Abernathy
2012-07-30 16:57 ` Gary Thomas
2012-07-30 17:09 ` Jim Abernathy
2012-07-30 17:16 ` Gary Thomas
2012-07-30 18:49 ` Jim Abernathy
2012-07-30 19:11 ` Gary Thomas
2012-07-31 11:25 ` Gary Thomas
2012-07-31 11:47 ` Jim Abernathy
2012-07-31 11:49 ` Martin Jansa
2012-07-31 11:53 ` Gary Thomas
2012-07-31 12:00 ` Jim Abernathy
2012-07-31 12:14 ` Gary Thomas
2012-07-31 13:33 ` Jim Abernathy
2012-07-31 17:12 ` William Mills
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=501BD126.5060100@mlbassoc.com \
--to=gary@mlbassoc.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.