All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: "Chatre, Reinette" <reinette.chatre@intel.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: Any hints when building boost-nativesdk?
Date: Thu, 20 Sep 2012 14:32:44 -0700	[thread overview]
Message-ID: <505B8B7C.7080501@linux.intel.com> (raw)
In-Reply-To: <1348166956.16487.26.camel@rchatre.jf.intel.com>

On 09/20/2012 11:50 AM, Chatre, Reinette wrote:
> Hi,
> 
> I am running Yocto 1.2 and would like to include the boost development
> environment in my SDK. I created a bbappend for the boost recipe that
> only contains two lines:
> 
> PR = "${INC_PR}.1"
> BBCLASSEXTEND += "nativesdk"
> 
> When I build with the above I get the following warnings:
> NOTE: multiple providers are available for runtime boost-date-time (boost, boost-nativesdk)
> NOTE: consider defining a PREFERRED_PROVIDER entry to match boost-date-time

Khem, I thought this might be something you were familiar with. Any
thoughts?

--
Darren

> NOTE: multiple providers are available for runtime boost-filesystem (boost, boost-nativesdk)
> NOTE: consider defining a PREFERRED_PROVIDER entry to match boost-filesystem
> NOTE: multiple providers are available for runtime boost-graph (boost, boost-nativesdk)
> NOTE: consider defining a PREFERRED_PROVIDER entry to match boost-graph
> NOTE: multiple providers are available for runtime boost-iostreams (boost, boost-nativesdk)
> NOTE: consider defining a PREFERRED_PROVIDER entry to match boost-iostreams
> NOTE: multiple providers are available for runtime boost-program-options (boost, boost-nativesdk)
> NOTE: consider defining a PREFERRED_PROVIDER entry to match boost-program-options
> NOTE: multiple providers are available for runtime boost-regex (boost, boost-nativesdk)
> NOTE: consider defining a PREFERRED_PROVIDER entry to match boost-regex
> NOTE: multiple providers are available for runtime boost-signals (boost, boost-nativesdk)
> NOTE: consider defining a PREFERRED_PROVIDER entry to match boost-signals
> NOTE: multiple providers are available for runtime boost-system (boost, boost-nativesdk)
> NOTE: consider defining a PREFERRED_PROVIDER entry to match boost-system
> NOTE: multiple providers are available for runtime boost-test (boost, boost-nativesdk)
> NOTE: consider defining a PREFERRED_PROVIDER entry to match boost-test
> NOTE: multiple providers are available for runtime boost-thread (boost, boost-nativesdk)
> NOTE: consider defining a PREFERRED_PROVIDER entry to match boost-thread
> 
> It seems a bit strange that "boost-nativesdk" is seen as a provider for
> any of those runtime components. Any hints what I should change to build
> things correctly?
> 
> Thank you very much
> 
> Reinette
>  
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
> 

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel


  reply	other threads:[~2012-09-20 21:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 18:50 Any hints when building boost-nativesdk? Chatre, Reinette
2012-09-20 21:32 ` Darren Hart [this message]
2012-09-20 21:49   ` Khem Raj
2012-09-20 22:56     ` Chatre, Reinette

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=505B8B7C.7080501@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=reinette.chatre@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.