All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yu, Mingli" <mingli.yu@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] boost.inc: make libboost_python3.so available
Date: Thu, 18 Oct 2018 10:28:12 +0800	[thread overview]
Message-ID: <5BC7EFBC.9070105@windriver.com> (raw)
In-Reply-To: <CAJTo0LaYemE+q9=n0LTET2DzsQgGQPWSH+bmaM0k4ifa9oRM+A@mail.gmail.com>



On 2018年10月17日 17:39, Burton, Ross wrote:
> On Wed, 17 Oct 2018 at 06:48, Yu, Mingli <mingli.yu@windriver.com> wrote:
>> I'm fine not add the the hack fix from boost side, but as I know there
>> is another package camera-calibration-parsers which has the same problem
>> as below apart from cv-bridge. BTW, there may some other package also
>> has this kind of problem. This to say we need to fix the issue for the
>> this kind of packages one by one.
>
> Yes, it will need to be fixed one by one, but everyone will have to do
> this because this is what Boost is now doing.  This isn't a change to
> boost that we introduced, upstream changed the library names so
> everyone who uses boost will be fixing their code.

Many thanks for Ross's clarification!
If we need to fix the packages one by one, but not add the hack at boost 
side, then https://bugzilla.yoctoproject.org/show_bug.cgi?id=12833 
should be invalid.

Thanks,

>
> Ross
>


  reply	other threads:[~2018-10-18  2:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-16  9:00 [PATCH] boost.inc: make libboost_python3.so available mingli.yu
2018-10-16 10:00 ` richard.purdie
2018-10-16 10:38   ` Burton, Ross
2018-10-16 11:18     ` Burton, Ross
2018-10-16 12:05       ` Burton, Ross
2018-10-17  5:46         ` Yu, Mingli
2018-10-17  9:39           ` Burton, Ross
2018-10-18  2:28             ` Yu, Mingli [this message]
2018-10-18  9:22               ` Burton, Ross

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=5BC7EFBC.9070105@windriver.com \
    --to=mingli.yu@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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.