From: Joshua Lock <josh@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: build failure on crownbay with EMGD
Date: Wed, 09 Nov 2011 11:17:16 -0800 [thread overview]
Message-ID: <4EBAD1BC.4060103@linux.intel.com> (raw)
In-Reply-To: <1320861083.16608.45.camel@elmorro>
On 09/11/11 09:51, Tom Zanussi wrote:
> On Wed, 2011-11-09 at 09:41 -0800, James Abernathy wrote:
>> In the past I've built the crownbay-noemgd successfully, using the
>> Development Manual Appendix A corrected instructions that have been
>> patched. I thought I'd try my hand at building the crownbay with EMGD
>> this time. Following the instructions in the Appendix A, but using
>> the opposite instructions related to EMGD, plus installing EMGD per
>> the instructions in the README file in the meta-crownbay directory, I
>> got a long way into the build, but failed toward the end in what looks
>> like a dependance issue. Can someone spot what I need to change???
>>
>
> Yes, you've hit the missing step added to the update release notes here:
>
> http://www.yoctoproject.org/download/bsp/intel-atom-processor-e660-intel-platform-controller-hub-eg20t-development-kit-1
>
>
> 7. Remove the following unused file from the emgd binaries in order to
> avoid a packaging error at build-time:
> $ rm
> meta-intel/common/recipes-graphics/xorg-xserver/emgd-driver-bin-1.8/lib/dri/emgd_drv_video.so
What prevents us doing this in the recipe?
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-11-09 19:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 17:41 build failure on crownbay with EMGD James Abernathy
2011-11-09 17:51 ` Tom Zanussi
2011-11-09 17:56 ` James Abernathy
2011-11-09 18:24 ` James Abernathy
2011-11-09 19:43 ` Tom Zanussi
2011-11-09 20:03 ` James Abernathy
2011-11-09 20:16 ` Tom Zanussi
2011-11-09 20:44 ` James Abernathy
2011-11-09 19:53 ` Tom Zanussi
2011-11-09 19:17 ` Joshua Lock [this message]
2011-11-09 19:50 ` Tom Zanussi
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=4EBAD1BC.4060103@linux.intel.com \
--to=josh@linux.intel.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.