From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] boost: version bump 1.51.0 -> 1.55.0
Date: Fri, 21 Mar 2014 10:30:32 +0100 [thread overview]
Message-ID: <7facbc38fd4ff794cc3fa6b86dd03c48@idefix.lespocky.dyndns.org> (raw)
In-Reply-To: <20140321090624.GN23331@pengutronix.de>
Hei hei,
Am 2014-03-21 10:06, schrieb Michael Olbrich:
> On Fri, Mar 07, 2014 at 11:12:50AM +0100, Alexander Dahl wrote:
>> Am 2014-03-07 10:54, schrieb Michael Olbrich:
>> > What exactly is the error you get? None of the libraries seem to be linked
>> > to the atomic boost library. Is that a runtime error?
>>
>> It is:
>>
>> error while loading shared libraries: libboost_atomic-mt.so.1.55.0:
>> cannot open shared object file: No such file or directory
>>
>> According to ldd libboost_thread-mt.so.1.55.0 is the only one on my
>> target linking against libboost_atomic-mt.so.1.55.0.
>
> Hmm, I didn't see that here. Maybe this is ARMv5 or something like that?
> I'd speculate that libboost_atomic is needed when the CPU has no atomic
> instructions.
The target is indeed ARMv5, but I didn't dig into Boost code for this.
Greets
Alex
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 ***
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-03-21 9:30 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 [this message]
2014-03-07 10:13 ` Jean-Claude Monnin
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=7facbc38fd4ff794cc3fa6b86dd03c48@idefix.lespocky.dyndns.org \
--to=post@lespocky.de \
--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