Boost logo

Boost-Build :

Subject: Re: [Boost-build] building*
From: Paul Hatton (P.S.HATTON_at_[hidden])
Date: 2015-10-19 15:07:49

Many thanks; I *was* missing the obvious. Amongst all of the files I hadn't realised that

[lib 19:55] $ ll *
ls: cannot access * No such file or directory

tells me that there are *no* * but the expected *-s.a. Not sure why graph-tool was trying to link against this, but that's not for this list.

As an aside, graph-tool linked OK against the system boost which has /usr/lib64/libboost*.so but no static libraries, so I need to work out the CXXFLAGS for the graph-tool build to stop it trying to link with the static library. This all started since graph-tool needs the C++14 extensions and our /usr/lib64/ is too old so I'm (trying to) build all the dependency chain with a locally-built gcc 5.2. Anyhow, that's not for this list.

Thanks again.

Paul Hatton
High Performance Computing and Visualisation Specialist
IT Services, The University of Birmingham
Ph: 0121-414-3994  Mob:07785 977340  Skype:P.S.Hatton
[Service Manager, Birmingham Environment for Academic Research]
[Also Technical Director, IBM Visual and Spatial Technology Centre]
-----Original Message-----
From: Boost-build [mailto:boost-build-bounces_at_[hidden]] On Behalf Of Steven Watanabe
Sent: 19 October 2015 18:53
To: Boost.Build developer's and user's list
Subject: Re: [Boost-build] building*
On 10/19/2015 10:12 AM, Paul Hatton wrote:
> Apologies for missing the obvious (I must be); I've also tried the list archives but can't find this mentioned.
> <snip>
> Can anyone give me a pointer as to why this specific shared library is not built when the static one is?
  The -s in the name indicates that it links to
the static C++ runtime.  When you're building
a shared library, you need to use a shared
runtime as well.
In Christ,
Steven Watanabe
Unsubscribe & other changes:

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at