On Tue, Aug 20, 2013 at 4:17 PM, Marshall Clow <email@example.com> wrote:On Aug 19, 2013, at 11:58 PM, Bioxydyn Dev <firstname.lastname@example.org> wrote:On Tue, Aug 20, 2013 at 7:34 AM, Bioxydyn Dev <email@example.com> wrote:
On Mon, Aug 19, 2013 at 4:57 PM, Steven Watanabe <firstname.lastname@example.org> wrote:
use toolset=darwin, not toolset=gcc.
On 08/19/2013 08:19 AM, Bioxydyn Dev wrote:
> I'm trying to build boost 1.54 on OSX 10.8.4. I'm a newbie at building on
> OSX and also at building custom boost binaries.
> I followed the instructions at
> to and including section 4. I then installed boost build as described
> section 5.2.1.
> To keep things simple I thought I'd just build the thread library for now
> as follows:
> /usr/local/bin/boost-build/bin/b2 install
> --prefix=~/development/cots/boost/ --build-dir=/tmp/build-boost stage
> --with-thread toolset=gcc-4.5 variant=debug --layout=versioned
> --build-type=complete -q
Please explain. Why would I do that when I've installed gcc separately and not using what came installed on the machine?From the boost build documentation:Apple Darwin gcc
darwinmodule supports the version of gcc that is modified and provided by Apple. The configuration is essentially identical to that of the gcc module.
The darwin toolset can generate so called "fat" binariesóbinaries that can run support more than one architecture, or address mode. To build a binary that can run both on Intel and PowerPC processors, specify
architecture=combined. To build a binary that can run both in 32-bit and 64-bit modes, specify
address-model=32_64. If you specify both of those properties, a "4-way" fat binary will be generated.I've installed gcc separately. I'm not using Apple's modified version.But I suspect that you _are_ using Apple's linker (ld), and it does not understand -h.Why do you suspect that Apple's linker is being invoked?
And why would it not invoke GCC's linker when I've specified the toolset=gcc?