Re: [Boost-users] [Context] Errors compiling Boost.Log on OS X

Subject: Re: [Boost-users] [Context] Errors compiling Boost.Log on OS X
From: Oliver Kowalke (oliver.kowalke_at_[hidden])
Date: 2013-04-29 09:51:46

Am 29.04.2013 14:50 schrieb "Nat Linden" <nat_at_[hidden]>:
>
> [Adding [Context] to subject line to catch Oliver's attention]
>
> On Sun, Apr 28, 2013 at 5:18 PM, Rich E <reakinator_at_[hidden]> wrote:
> >
> > On Sun, Apr 28, 2013 at 10:37 AM, Nat Linden <nat_at_[hidden]> wrote:
> >>
> >> I'm using Xcode 4.3.3, gcc 4.2.1, these commands:
> >>
> >> ./b2 variant=debug address-model=32 architecture=x86 link=static
> >> threading=multi libs/context/test
> >> ./b2 variant=debug address-model=32 architecture=x86 link=static
> >> threading=multi libs/context/example
> >
> > Sorry, I should have been clearer in that I'm using clang with libc++
> > (current Xcode version, 4.6.2), as this is now standard on OS X and
required
> > by our software framework.
>
> My situation is the opposite of yours: I can't yet upgrade.
>
> > I have the following in my user-config.jam:
> >
> > using clang : osx
> > : xcrun clang -stdlib=libc++ -std=c++11
> > ;
> >
> > To just build context, I do:
> >
> > ./bootstrap.sh --with-libraries=context
> > ./b2 -a toolset=clang-osx link=static threading=multi stage
>
> With Xcode 4.3.3, the above produces warnings but no errors.
>
> > lang-darwin.compile.c++
> >
bin.v2/libs/context/build/clang-darwin-osx/release/link-static/threading-multi/unsupported.o
> > libs/context/src/unsupported.cpp:7:2: error: "platform not supported"
> > #error "platform not supported"
> >  ^
> > 1 error generated.
>
> Unfortunately this source file tells me nothing about the conditions
> that lead to its being compiled. I see in
> libs/context/build/Jamfile.v2 the following:
>
> alias asm_context_sources
>    : unsupported.cpp
>    ;
>
> (the only reference I found to 'unsupported' in boost/context or
> libs/context). bjam is a black box to me. I must defer to those who do
> understand it.

seams that multi-lib should be build - AFAIK boost.build doesn't support it
yet.