From: "Eric Bénard" <eric@eukrea.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: X11 on i.MX5
Date: Tue, 29 Jul 2014 22:10:56 +0200 [thread overview]
Message-ID: <20140729221056.5fda40a7@e6520eb> (raw)
In-Reply-To: <53D7D14C.6000607@mlbassoc.com>
Le Tue, 29 Jul 2014 10:52:28 -0600,
Gary Thomas <gary@mlbassoc.com> a écrit :
>
> On 2014-07-29 10:37, Eric Bénard wrote:
> > Hi Gary,
> >
> > Le Tue, 29 Jul 2014 10:05:30 -0600,
> > Gary Thomas <gary@mlbassoc.com> a écrit :
> >
> >> Any ideas what I need to do to get X11 running on this target?
> >>
> > it seems this package is missing on your target : libgsl-fsl-mx51
>
> Interesting - the recipe
> meta-fsl-arm/recipes-graphics/amd-gpu-x11-bin/amd-gpu-x11-bin-mx51_11.09.01.bb
> was built, but there were no libgsl-fsl-mx* packages produced? Here's
> all I have:
>
> $ find tmp/deploy/ipk/ -name "libgsl*"
> tmp/deploy/ipk/armv7a-vfp-neon-mx5/libgsl-fsl-dev_11.09.01-r12.0_armv7a-vfp-neon-mx5.ipk
> tmp/deploy/ipk/armv7a-vfp-neon-mx5/libgsl-fsl-dbg_11.09.01-r12.0_armv7a-vfp-neon-mx5.ipk
> tmp/deploy/ipk/armv7a-vfp-neon-mx5/libgsl-fsl1_11.09.01-r12.0_armv7a-vfp-neon-mx5.ipk
>
> Any ideas why I don't have any of the rest produced by that recipe?
>
may you please send the result of bitbake -e amd-gpu-x11-bin-mx51 ?
Eric
next prev parent reply other threads:[~2014-07-29 20:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 16:05 X11 on i.MX5 Gary Thomas
2014-07-29 16:37 ` Eric Bénard
2014-07-29 16:52 ` Gary Thomas
2014-07-29 19:47 ` Otavio Salvador
2014-07-29 20:11 ` Eric Bénard
2014-07-29 20:12 ` Otavio Salvador
2014-07-29 20:32 ` Eric Bénard
2014-07-29 20:10 ` Eric Bénard [this message]
2014-07-29 20:26 ` Eric Bénard
2014-07-29 22:28 ` Gary Thomas
2014-08-01 16:31 ` Gary Thomas
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=20140729221056.5fda40a7@e6520eb \
--to=eric@eukrea.com \
--cc=gary@mlbassoc.com \
--cc=meta-freescale@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.