Login or Register to Ask a Question and Join Our Community


Solaris

Sun Studio 10 + Boost 1.36

 
Thread Tools Search this Thread
Operating Systems Solaris Sun Studio 10 + Boost 1.36
Prev   Next
# 3  
Old 05-04-2009
here is the first few error messages that i encountered (there are tonz more). I like to emphasize that i was able to complie the same boost library using sun studio 11 with no problem with the same boost configuration and makefile

"./boost/type_traits/is_array.hpp", line 40: Error: Multiple declaration for boost::is_array.
"./boost/type_traits/is_array.hpp", line 41: Error: Multiple declaration for boost::is_array.
"./boost/type_traits/is_array.hpp", line 42: Error: Multiple declaration for boost::is_array.
"./boost/type_traits/is_array.hpp", line 43: Error: Multiple declaration for boost::is_array.

here are the lines:
BOOST_TT_AUX_BOOL_TRAIT_PARTIAL_SPEC1_1(typename T,is_array,T[],true)
BOOST_TT_AUX_BOOL_TRAIT_PARTIAL_SPEC1_1(typename T,is_array,T const[],true)
BOOST_TT_AUX_BOOL_TRAIT_PARTIAL_SPEC1_1(typename T,is_array,T volatile[],true)
BOOST_TT_AUX_BOOL_TRAIT_PARTIAL_SPEC1_1(typename T,is_array,T const volatile[],true)

here is how i configure it:
./configure --prefix=<boostpath> --with-toolset=sun --with-libraries=thread,filesystem,date_time,system link=static | tee ../configure.log

then i modified the user-config.jam to specify the complier and options:
sun : : <sunCC path> : <compileflags>-library=stlport4 -features=tmplife -features=tmplrefstatic ;

make | tee ../make.log
Last edited by shingpui; 05-04-2009 at 10:07 AM..
 
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. Solaris

Sun One Studio 12

Hi, Do you know where I can get a copy of Sun One Studio 12? I've looked on the Oracle Website but cannot find it to download!:confused: Thanks, Sparcman (1 Reply)
Discussion started by: sparcman
1 Replies

2. Solaris

boost thread not accessible to boost::move error

Hi All I am working unders Sun Solaris and I am not "/opt/boost/boost/thread/detail/thread.hpp", line 344: Error: boost::thread::thread(boost::thread&) is not accessible from boost::move(boost::detail::thread_move_t<boost::thread>). Do you know if there are other solutions other than... (2 Replies)
Discussion started by: manustone
2 Replies

3. Solaris

Whether Sun studio is installed on my Solaris Server?

Hi All I want to confirm the installation of Sun Studio installation on my UNIX development server. Please suggest how to get that. Cheers, Ankur (4 Replies)
Discussion started by: sharmaankur85
4 Replies

4. Solaris

Sun Studio 11 in OpenSolaris

Install Sun Studio 11 on OpenSolaris 2009.06 When run IDE - system return error: touch: cannot change times on /export/home/iktomy/.sunstudio/11-SunOS-i386/system/dontshowisw: Permission denied /opt/SUNWspro/prod/scripts/jdk_chooser: line 131: cat: command not found... (0 Replies)
Discussion started by: Iktomy
0 Replies

5. Solaris

java.lang.OutofMemoryError in Sun Studio 12

Hello everyone, I have installed Sun Studio 12 in my Sun Solaris 10 (x86) OS. At first, there was nothing wrong with it but recently, I couldn't open the Sun Studio IDE. When I try to open it, I keep on getting the following error messages:... (2 Replies)
Discussion started by: wintersakura
2 Replies

6. Solaris

Sun Studio problem

I am using Sun Studio. But there is problem with it. When my PC is connected to INTERNET then there is no problem in starting Sun Studio. But When my PC is not connected to INTERNET then there is problem in starting Sun Studio. With out INTERNET i run sunstudio but after waiting long time nothing... (0 Replies)
Discussion started by: mansoorulhaq
0 Replies
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

bjam

BOOST.BUILD(1)							   User Commands						    BOOST.BUILD(1)

NAME

       Boost.Build - software build tool

DESCRIPTION

       Boost.Build 2011.04-svn

       Project-specific help:

	      Project has jamfile at Jamroot

       Usage:

	      bjam [options] [properties] [install|stage]

	      Builds and installs Boost.

       Targets and Related Options:

       install
	      Install headers and compiled library files to the

       =======
	      configured locations (below).

       --prefix=<PREFIX>
	      Install architecture independent files here.  Default; C:Boost on Win32 Default; /usr/local on Unix. Linux, etc.

       --exec-prefix=<EPREFIX> Install architecture dependent files here.
	      Default; <PREFIX>

       --libdir=<DIR>
	      Install library files here.  Default; <EPREFIX>/lib

       --includedir=<HDRDIR>
	      Install header files here.  Default; <PREFIX>/include

       stage  Build and install only compiled library files

       =====  to the stage directory.

       --stagedir=<STAGEDIR>
	      Install library files here Default; ./stage

       Other Options:

       --build-type=<type>
	      Build the specified pre-defined set of variations of the libraries. Note, that which variants get built depends on what each library
	      supports.

	      minimal (default) - Builds a minimal set of variants. On Windows, these are static multithreaded	libraries  in  debug  and  release
	      modes, using shared runtime. On Linux, these are static and shared multithreaded libraries in release mode.

	      complete - Build all possible variations.

       --build-dir=DIR
	      Build in this location instead of building within the distribution tree. Recommended!

       --show-libraries
	      Displays the list of Boost libraries that require build and installation steps, then exit.

       --layout=<layout>
	      Determines  whether  to  choose library names and header locations such that multiple versions of Boost or multiple compilers can be
	      used on the same system.

	      versioned - Names of boost binaries include the Boost version number, name and version of the compiler and encoded build properties.
	      Boost headers are installed in a subdirectory of <HDRDIR> whose name contains the Boost version number.

	      tagged  -- Names of boost binaries include the encoded build properties such as variant and threading, but do not including compiler
	      name and version, or Boost version. This option is useful if you build several variants of Boost, using the same compiler.

	      system - Binaries names do not include the Boost version number or the name and version number of the compiler.  Boost  headers  are
	      installed directly into <HDRDIR>.  This option is intended for system integrators who are building distribution packages.

	      The default value is 'versioned' on Windows, and 'system' on Unix.

       --buildid=ID
	      Adds the specified ID to the name of built libraries.  The default is to not add anything.

       --python-buildid=ID
	      Adds the specified ID to the name of built libraries that depend on Python.  The default is to not add anything. This ID is added in
	      addition to --buildid.

       --help This message.

       --with-<library>
	      Build and install the specified <library> If this option is used, only libraries specified using this option will be built.

       --without-<library>
	      Do not build, stage, or install the specified <library>. By default, all libraries are built.

       Properties:

       toolset=toolset
	      Indicates the toolset to build with.

       variant=debug|release
	      Select the build variant

       link=static|shared
	      Whether to build static or shared libraries

       threading=single|multi
	      Whether to build single or multithreaded binaries

	      runtime-link=static|shared

	      Whether to link to static or shared C and C++ runtime.

       Configuration help:

	      Configuration file at /build/other/boost1.49-1.49.0/tools/build/v2/user-config.jam

	      This file is used to configure your Boost.Build installation. You can modify

       this file in place, or you can place it in a permanent location so that it does not get	overwritten  should  you  get  a  new  version	of
       Boost.Build. See:

	      http://www.boost.org/boost-build2/doc/html/bbv2/overview/configuration.html

       for documentation about possible permanent locations.

       General command line usage:

	      bjam [options] [properties] [targets]

	      Options, properties and targets can be specified in any order.

       Important Options:

	      *  --clean  Remove  targets instead of building * -a Rebuild everything * -n Don't execute the commands, only print them * -d+2 Show
	      commands as they are executed * -d0 Supress all informational messages * -q Stop at first  error	*  --debug-configuration  Diagnose
	      configuration  *	--debug-building  Report  which  targets  are  built  with  what properties * --debug-generator Diagnose generator
	      search/execution

       Further Help:

	      The following options can be used to obtain additional documentation.

	      *  --help-options  Print	more  obscure  command	line  options.	 *  --help-internal   Boost.Build   implementation   details.	 *
	      --help-doc-options Implementation details doc formatting.

       ...found 1 target...

Boost.Build 2011.04-svn 					   February 2013						    BOOST.BUILD(1)