Rogue Wave Knowledge Base
Browse by category:
Knowledgebase | Glossary | Ask a Question |

SourcePro Static build looking for a shared Standard Library version

Article ID: 1363
Last updated: 28 Feb, 2008
Revision: 1
print  Print
share  Share
Views: 2606
Posted: 22 Feb, 2008
by --
Updated: 28 Feb, 2008

I have built the Rogue Wave libraries statically, but  after building my application, I get the following error message:
error while loading shared libraries: cannot open shared object file: No such file or directory


The Apache C++ Standard Library lacks support for build tags. As such, conflicts will occur if multiple versions of the library are built in the same buildspace.  So if you have built both the Static libraries and Shared libraries into the same buildspace, then the last version of the standard library will be used.


The best solution for this case is to export all your diffent buildtypes into unique buildspaces.  You can do this by exporting (headers and source) into a new buildspace location.  For more information on exported builds please see the RCB User Guide.
This article was:   Helpful | Not helpful Report an issue

Also listed in
folder SourcePro -> Core -> Standard C++ Library
folder SourcePro -> Releases -> Edition 10 SP

Prev     Next
Incorrect RCB Compiler & OS Selections in SuSE Linux Enterprise...       Currency Library fails to build on AIX 5.3 with xlC

Others in this category
b Incorrect RCB Compiler & OS Selections in SuSE Linux Enterprise Server (SLES) 9
b Currency Library fails to build on AIX 5.3 with xlC
b SourcePro install problem on Linux platform
b Use Stream Versions to Improve Efficiency or Provide Compatibility
b On AIX 5.3, RCB only generates static libs (*.a) and not dynamic libs (*.so)
b What is a static initialization problem?
b How to create a single SourcePro threads rollup library?
b Display Issues during SourcePro installation
b Problem Installing SourcePro on 64bit Linux