From: Gary Thomas <gary@mlbassoc.com>
To: Denys Dmytriyenko <denys@ti.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: Can't build recipes-graphics/xorg-xserver/xf86-video-omap_git.bb
Date: Wed, 28 Nov 2012 10:29:31 -0700 [thread overview]
Message-ID: <50B649FB.30609@mlbassoc.com> (raw)
In-Reply-To: <20121128171902.GB7172@edge>
On 2012-11-28 10:19, Denys Dmytriyenko wrote:
> http://thread.gmane.org/gmane.linux.embedded.yocto.meta-ti/1196
Bottom line: I should just use the latest Poky/Yocto tree? I just updated
the meta-ti(master) and the quoted patches don't seem to have been applied
(the xf86-video-omap_git.bb is still present)
>
> On Wed, Nov 28, 2012 at 10:18:10AM -0700, Gary Thomas wrote:
>> When trying to build this recipe, I get this error:
>>
>> configure: error: Package requirements (xorg-server >= 1.3 xproto fontsproto libdrm >= 2.4.36 libdrm_omap xf86driproto randrproto renderproto videoproto xextproto) were not met:
>> No package 'libdrm_omap' found
>>
>> Where can I find this package?
>>
>> Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2012-11-28 17:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 17:18 Can't build recipes-graphics/xorg-xserver/xf86-video-omap_git.bb Gary Thomas
2012-11-28 17:19 ` Denys Dmytriyenko
2012-11-28 17:29 ` Gary Thomas [this message]
2012-11-28 17:31 ` Nicolas Dechesne
2012-11-28 17:34 ` Denys Dmytriyenko
2012-11-28 17:38 ` Nicolas Dechesne
2012-11-28 19:58 ` Gary Thomas
2012-11-28 20:17 ` Denys Dmytriyenko
2012-11-28 20:47 ` Gary Thomas
2012-11-28 20:50 ` Nicolas Dechesne
2012-11-29 15:01 ` Gary Thomas
2012-11-29 22:05 ` Nicolas Dechesne
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=50B649FB.30609@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=denys@ti.com \
--cc=meta-ti@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.