All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Abernathy <jfabernathy@gmail.com>
To: yocto@yoctoproject.org
Subject: Building crownbay from master
Date: Thu, 04 Oct 2012 14:36:51 -0400	[thread overview]
Message-ID: <506DD743.6030204@gmail.com> (raw)

I successfully build the meta-crownbay BSP using the latest pull from 
master branch.  I did get some warning, that I wonder what they mean or 
the significance of them:

NOTE: preferred version 7.11 of mesa-dri not available (for item 
virtual/libgl)
NOTE: versions of mesa-dri available: 2:8.0.4 
2:8.0.4+git1+c1f4867c89adb1a6b19d66ec8ad146115909f0a7
NOTE: preferred version 7.11 of mesa-dri not available (for item mesa-dri)
NOTE: versions of mesa-dri available: 2:8.0.4 
2:8.0.4+git1+c1f4867c89adb1a6b19d66ec8ad146115909f0a7
NOTE: preferred version 7.11 of mesa-dri not available (for item 
mesa-dri-dev)
NOTE: versions of mesa-dri available: 2:8.0.4 
2:8.0.4+git1+c1f4867c89adb1a6b19d66ec8ad146115909f0a7
NOTE: preferred version 7.11 of mesa-dri not available (for item mesa-dri)
NOTE: versions of mesa-dri available: 2:8.0.4 
2:8.0.4+git1+c1f4867c89adb1a6b19d66ec8ad146115909f0a7


WARNING: bzip2: No generic license file exists for: bzip2 in any provider
WARNING: bzip2-native: No generic license file exists for: bzip2 in any 
provider
WARNING: emgd-driver-bin: No generic license file exists for: 
Intel-binary-only in any provider
WARNING: busybox: No generic license file exists for: bzip2 in any provider

Also a number of warning about the recipe trying to install files into a 
shared area when those files already existed.

Jim A



                 reply	other threads:[~2012-10-04 18:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=506DD743.6030204@gmail.com \
    --to=jfabernathy@gmail.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.