From: Jean-Claude Monnin <jc_monnin@emailplus.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] boost: version bump 1.51.0 -> 1.55.0
Date: Fri, 7 Mar 2014 11:13:58 +0100 [thread overview]
Message-ID: <40EC22FD-6FE8-4E8F-892D-95EDA896D3A7@emailplus.org> (raw)
In-Reply-To: <2b0af83d757c8897e1e54eff9ae2f07d@idefix.lespocky.dyndns.org>
On 07 Mar 2014, at 09:54, Alexander Dahl <post@lespocky.de> wrote:
> Am 2014-02-03 09:13, schrieb Michael Olbrich:
>> On Fri, Dec 20, 2013 at 02:55:27PM +0100, Jean-Claude Monnin wrote:
>>> Hi everyone,
>>>
>>> On 21 Nov 2013, at 10:42, Jean-Claude Monnin <jc_monnin@emailplus.org> wrote:
>>>> Boost realease notes: http://www.boost.org/users/history/version_1_55_0.html
>>>> Help text is updated with description from project page with respect to C++11.
>>>> Menu options for new libraries are added (atomic, coroutine, log).
>>>>
>>>> Signed-off-by: Jean-Claude Monnin <jc_monnin@emailplus.org>
>>>> ---
>>>> rules/boost.in | 30 +++++++++++++++++++++++++-----
>>>> rules/boost.make | 7 +++++--
>>>> 2 files changed, 30 insertions(+), 7 deletions(-)
>>>
>>> I saw that the version bump was not part of PTXdist 2013.12.0. Obviously it's
>>> not a problem to keep the patched file local to my project, but I was
>>> wondering about the reasons. Are there some issues with my patch or boost
>>> version 1.55.0?
>>
>> It just got lost. I've applied it now.
>
> Sorry for digging in old mails. We came across a dependency problem with
> the new boost libraries. We have selected chrono, filesystem,
> serialization, system, thread and timer. After compiling stuff with
> boost 1.55 executing stuff on the target failed because atomic was
> missing on the target. To me it seems some boost library depends on
> atomic which is not reflected in the boost.in rule. Does anyone know
> which one and could fix this?
I could be boost thread. I just saw following in the doc:
http://www.boost.org/doc/libs/1_55_0/doc/html/thread/build.html#thread.build.configuration.move0
It looks like boost thread depends on atomic on posix. Before submitting the patch I tested the compile, but haven't tested the use of boost thread (I don't use this part in my projects). I cannot investigate and test this right now, but it seems that boost thread should probably add a dependency to boost atomic.
Jean-Claude
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2014-03-07 10:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 9:42 Jean-Claude Monnin
2013-12-20 13:55 ` Jean-Claude Monnin
2014-02-03 8:13 ` Michael Olbrich
2014-03-07 8:54 ` Alexander Dahl
2014-03-07 9:54 ` Michael Olbrich
2014-03-07 10:12 ` Alexander Dahl
2014-03-21 9:06 ` Michael Olbrich
2014-03-21 9:30 ` Alexander Dahl
2014-03-07 10:13 ` Jean-Claude Monnin [this message]
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=40EC22FD-6FE8-4E8F-892D-95EDA896D3A7@emailplus.org \
--to=jc_monnin@emailplus.org \
--cc=ptxdist@pengutronix.de \
/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