- 385.5K All Categories
- 5.1K Data
- 2.5K Big Data Appliance
- 2.5K Data Science
- 453.4K Databases
- 223.2K General Database Discussions
- 47 Multilingual Engine
- 606 MySQL Community Space
- 486 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.2K ORDS, SODA & JSON in the Database
- 585 SQLcl
- 4K SQL Developer Data Modeler
- 188K SQL & PL/SQL
- 21.5K SQL Developer
- 46 Data Integration
- 46 GoldenGate
- 298.4K Development
- 4 Application Development
- 20 Developer Projects
- 166 Programming Languages
- 295K Development Tools
- 150 DevOps
- 3.1K QA/Testing
- 646.7K Java
- 37 Java Learning Subscription
- 37.1K Database Connectivity
- 201 Java Community Process
- 108 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.4K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 176 Java 8 Questions
- 86K Java Programming
- 82 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 208 Java User Groups
- 667 LiveLabs
- 41 Workshops
- 10.3K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 6K Other Languages
- 2.3K Chinese
- 207 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 474 Portuguese
Problem building Boost 1.64.0 with Developer Studio 12.6
I have a set of libraries which I build on various platforms. This set of libraries requires the Boost C++ Libraries.
I attempted to build Boost 1.64.0 on Solaris 11.3 x86_64 using Developer Studio 12.6 without success. These are the command lines used to invoke the build:
./bootstrap.sh --prefix=/export/home/dev3rd/boost_1_64_0 --with-toolset=sun
./b2 link=shared runtime-link=shared address-model=64 threading=multi variant=release cxxflags="-std=c++14" linkflags="-std=c++14" install
FYI, I have successfully performed the same build on two other platforms, namely:
1. Fedora 26 using GCC 7.1.
2. Windows 7 using Visual Studio 2017.
I have also raised the same issues with Boost but I have not received any feedback yet.
It seems that there are 3 main issues with the build, namely:
1. Problem with Boost.Log library with this error message:
>> Assertion: (../lnk/initializer.cc, line 1865)
while processing ./boost/log/expressions/message.hpp at line 98.
It appears that this has something to do with initializer lists. Are you able to confirm that this is a compiler issue or should I be pursuing it with Boost?
2. Another problem with Boost.Log library with this error message:
"libs/log/src/named_scope.cpp", line 118: Error: Use of overloaded binary operator '=' is ambiguous.
"./boost/optional/optional.hpp", line 900: Note: Viable candidate 'boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>& boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>::operator=<boost::log::v2_mt_posix::attributes::named_scope_list&>(boost::log::v2_mt_posix::attributes::named_scope_list&)'.
"./boost/optional/optional.hpp", line 962: Note: Viable candidate 'boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>& boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>::operator=<boost::log::v2_mt_posix::attributes::named_scope_list&>(boost::log::v2_mt_posix::attributes::named_scope_list&)'.
It is possible that this is a Boost configuration issue since two member functions with the same signature are being seen by the compiler. However, it is also possible that this is a std::enable_if<> issue. Can you please comment.
3. Problem with Boost.Python with this error message:
"libs/python/src/numpy/dtype.cpp", line 61: Error: NPY_FLOAT16 is not defined.
It appears that this might be a package installation issue to do with Python-related packages. FYI, I'm only running Solaris 11.3 x86_64 on a VMware virtual machine without a support contract thus I'm having issues installing the required Python packages possibly due to unapplied required updates of the operating system. I'm hoping that if someone from Oracle performed the same build you wouldn't be having this problem. Is this a fair enough assumption?