From: GNUtoo <GNUtoo@no-log.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: patch to boost package
Date: Sun, 28 Jun 2009 03:46:13 +0200 [thread overview]
Message-ID: <1246153579.32326.3.camel@port4> (raw)
In-Reply-To: <6a1b49480906251521w364bce23o2dd5f921a468474c@mail.gmail.com>
On Fri, 2009-06-26 at 00:21 +0200, Frank Black wrote:
> I tried building boost 1.36.0 for my armv5te processor. Problem is there is
> no support for the function "__sync_add_and_fetch" called from
> detail/atomic_count_sync.hpp. There are two patches which both fails to
> resolve this for me.
>
> 1: arm-instrinct.patch. This requires __ARM_ARCH_7A__ to be defined, which
> is not good for me on an armv5te.
> 2: atomic_count_gcc_atomicity.patch: Works, however problem is that
> atomic_count.hpp contains #defines that always #includes
> atomic_count_sync.hpp instead of atomic_count_gcc.hpp, so the patch has no
> effect
>
> I solved this by applying a really ugly patch (see below) that makes sure
> atomic_count_sync.hpp is never used. Im sure therre is a better way to do it
> but I'm not at all familiar what kind of ARM-specific defines you got to
> play around with. Maybe someone has more in-depth knowledge abot this?
>
>
>
> --- boost_1_33_1.orig/boost/detail/atomic_count.hpp 2007-11-23
> 18:03:14.000000000 +0100
> +++ boost_1_33_1/boost/detail/atomic_count.hpp 2009-06-25
> 23:07:10.000000000 +0200
> @@ -101,10 +101,10 @@
>
> # include <boost/detail/atomic_count_win32.hpp>
>
> -#elif defined( __GNUC__ ) && ( __GNUC__ * 100 + __GNUC_MINOR__ >= 401 )
> +/*#elif defined( __GNUC__ ) && ( __GNUC__ * 100 + __GNUC_MINOR__ >= 401 )
>
> # include <boost/detail/atomic_count_sync.hpp>
> -
> +*/
> #elif defined(__GLIBCPP__) || defined(__GLIBCXX__)
>
> # include <boost/detail/atomic_count_gcc.hpp>
>
>
> / Rolle
yes there is:
I've put the boost work I did with the help of other people here:
http://gnutoo.homelinux.org/open_embedded/boost.tar.bz2
I didn't have the time to finish my work because I had a segmentation
fault in boost with wesnoth-1.6x so I didn't commit it yet because of
the lack of skills and time to debug it(I don't know C++,I just learned
it a bit for this precise problem)
Denis.
prev parent reply other threads:[~2009-06-28 1:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 22:21 patch to boost package Frank Black
2009-06-28 1:46 ` GNUtoo [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=1246153579.32326.3.camel@port4 \
--to=gnutoo@no-log.org \
--cc=openembedded-devel@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