Thank you... I would seem that the iostreams fall over on a zlib dependency. Not positive we'll need it straight off, but given our size constraints (embedded ARM device), it's not a far stretch, it's quite plausible we would want to zlib-compress data along the way. That said... What are my options? The simplest answer, I've read, is to find zlib and provide this? Do we need to build that separately for ARM? Or does that get included with the boost build? Regards, Michael Powell On Fri, Mar 29, 2013 at 9:01 PM, Steven Watanabe wrote:

AMDG

On 03/29/2013 12:14 PM, Michael Powell wrote:

...

On Fri, Mar 29, 2013 at 1:19 PM, Michael Powell wrote:

...

Hello,

I believe we're on the home stretch building boost and getting productive with it. But I have a couple of questions.

At the moment, it is mostly building. I do get an installed outcome. However, minus one target: failed updating 1 target.

Which target? No idea how critical that target is to what we want to accomplish.

I suggest you re-run b2. It should only try to update the target that failed, so you can see what it is. (When you're building from scratch and you want to see errors, either use -q to stop on errors or capture the output in a file.)

In Christ, Steven Watanabe

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

On Sat, Mar 30, 2013 at 10:49 AM, Lars Viklund wrote:

On Sat, Mar 30, 2013 at 10:40:47AM -0500, Michael Powell wrote:

...

Thank you...

I would seem that the iostreams fall over on a zlib dependency. Not positive we'll need it straight off, but given our size constraints (embedded ARM device), it's not a far stretch, it's quite plausible we would want to zlib-compress data along the way.

That said... What are my options? The simplest answer, I've read, is to find zlib and provide this? Do we need to build that separately for ARM? Or does that get included with the boost build?

The Iostreams library can either use an existing ZLib library and headers, or build a private internal variant of ZLib if you point out a ZLib source tree.

Got it. Downloaded the zlib sources into my workspace tools and built it for the ARM target. The boost-build example I'm working from specifies the zlib include and linker options. Adapting that into our workspace, work (well, "builds") like a champ. Thank ye.

It's likely analogous for the BZip2 parts of Iostreams.

(fun fact -- Boost list policy mandates in-line bottom-posting)

My mistake. Blessings.

...

On Fri, Mar 29, 2013 at 9:01 PM, Steven Watanabe wrote:

...

AMDG

On 03/29/2013 12:14 PM, Michael Powell wrote:

...

On Fri, Mar 29, 2013 at 1:19 PM, Michael Powell wrote:

...

Hello,

I believe we're on the home stretch building boost and getting productive with it. But I have a couple of questions.

At the moment, it is mostly building. I do get an installed outcome. However, minus one target: failed updating 1 target.

Which target? No idea how critical that target is to what we want to accomplish.

I suggest you re-run b2. It should only try to update the target that failed, so you can see what it is. (When you're building from scratch and you want to see errors, either use -q to stop on errors or capture the output in a file.)

In Christ, Steven Watanabe

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

---

Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

-- Lars Viklund | zao@acc.umu.se _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users