From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] boost: update to 1.59.0
Date: Fri, 18 Dec 2015 14:57:26 +0200 [thread overview]
Message-ID: <567402B6.8060907@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LZkPQgzt6Kttmg4sWrXQk_m+iT9qLK1sR-ftkMBZxK0YA@mail.gmail.com>
On 12/17/2015 10:35 PM, Burton, Ross wrote:
> Due to the version update, the two patches previously backported in
> this recipe are now dropped. The actual status of the
> arm-intrinsics.patch (reported with Upstream-Status: Backport)
> is unknown to the committer, and hence, that patch is kept in the
> recipe, even if it is possibly not required anymore. A deeper
> analysis is required to determine need and status of that patch.
>
>
> This adds a new library so the packaging needs to be updated to reflect
> that. The obvious problem is that the development/debug/test packages
> are all called libboost-timer after this upgrade.
>
> Once fixed (extend BOOST_LIBS) it would be good to set FILES_${PN} to ""
> so this can't happen in the future, and instead you'd get
> installed-not-shipped errors.
Also, the latest upstream is 1.60.0.
Alex
next prev parent reply other threads:[~2015-12-18 12:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 11:45 [PATCH] boost: update to 1.59.0 Lukas Bulwahn
2015-12-17 20:35 ` Burton, Ross
2015-12-18 12:57 ` Alexander Kanavin [this message]
2015-12-18 13:11 ` Alexander Kanavin
2016-01-05 9:32 ` [PATCH v2 1/2] boost: ensure boost to remain an empty metapackage Lukas Bulwahn
2016-01-05 9:32 ` [PATCH v2 2/2] boost: update to 1.60.0 Lukas Bulwahn
2016-01-05 17:31 ` Burton, Ross
2016-01-11 21:06 ` Khem Raj
2016-01-06 17:31 ` [PATCH v3] " Lukas Bulwahn
2016-01-06 21:03 ` Burton, Ross
2016-01-11 20:51 ` [PATCH v2 1/2] boost: ensure boost to remain an empty metapackage Khem Raj
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=567402B6.8060907@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox