Building Boost with PathScale compiler
I am trying to build the Boost 1.31.0 libraries on an AMD Opteron platform using PathScale C++ 1.2. There is no toolset for this compiler, which looks something like a MipsPro compiler and something like a g++ compiler. Has anyone created a toolset for it? If not, how do I build a new toolset, or is there an easier way to build and install the libraries? -- Dick Hadsell 914-259-6320 Fax: 914-259-6499 Reply-to: hadsell@blueskystudios.com Blue Sky Studios http://www.blueskystudios.com 44 South Broadway, White Plains, NY 10601
Richard Hadsell wrote:
I am trying to build the Boost 1.31.0 libraries on an AMD Opteron platform using PathScale C++ 1.2. There is no toolset for this compiler, which looks something like a MipsPro compiler and something like a g++ compiler. Has anyone created a toolset for it? If not, how do I build a new toolset, or is there an easier way to build and install the libraries?
No help for me? How do you Boost experts develop a toolset for a new compiler? -- Dick Hadsell 914-259-6320 Fax: 914-259-6499 Reply-to: hadsell@blueskystudios.com Blue Sky Studios http://www.blueskystudios.com 44 South Broadway, White Plains, NY 10601
Richard Hadsell <hadsell@blueskystudios.com> writes:
Richard Hadsell wrote:
I am trying to build the Boost 1.31.0 libraries on an AMD Opteron platform using PathScale C++ 1.2. There is no toolset for this compiler, which looks something like a MipsPro compiler and something like a g++ compiler. Has anyone created a toolset for it? If not, how do I build a new toolset, or is there an easier way to build and install the libraries?
No help for me? How do you Boost experts develop a toolset for a new compiler?
Use tools/build/v1/gcc-tools.jam as a working example and tools/build/v1/gcc-tools.html to understand it. Don't write lines like: flags gcc GCC_BIN_DIRECTORY : $(GCC_BIN_DIRECTORY) ; flags gcc GCC_INCLUDE_DIRECTORY : $(GCC_INCLUDE_DIRECTORY) ; flags gcc GCC_STDLIB_DIRECTORY : $(GCC_STDLIB_DIRECTORY) ; These are a mistake (they prevent customization of multiple versions of the toolset), but they keep creeping back into toolset files for some reason, even though I keep taking them out. See http://www.boost.org/tools/build/v1/build_system.htm#toolset_description for other help. We know the docs are not great, but we're going to retire this version of the build system ASAP so a big investment in docs is unwarranted. HTH, -- Dave Abrahams Boost Consulting http://www.boost-consulting.com
David Abrahams wrote:
Use tools/build/v1/gcc-tools.jam as a working example and tools/build/v1/gcc-tools.html to understand it.
See http://www.boost.org/tools/build/v1/build_system.htm#toolset_description for other help.
Thanks for the help. I have made some progress at creating a pathscale-tools.jam, starting from mipspro-tools.jam (but keeping my eye on gcc-tools.jam, in case of link problems). I can't figure out a couple of things about the output. Due to compiler problems I haven't finished a build, but I can see that the output files in the stage directory are being named this way: libboost_date_time-pathscale-1_31.a When building for the intel-linux toolset, I see 2 copies of the equivalent file: libboost_date_time-il-1_31.a libboost_date_time-il.a I would like to know (a) how to abbreviate 'pathscale' to 'ps' in the file names and (b) how to make a second copy of each file without the Boost version in the name. (Perhaps (b) will take care of itself, if the build ever finishes successfully.) -- Dick Hadsell 914-259-6320 Fax: 914-259-6499 Reply-to: hadsell@blueskystudios.com Blue Sky Studios http://www.blueskystudios.com 44 South Broadway, White Plains, NY 10601
Richard Hadsell <hadsell@blueskystudios.com> writes:
David Abrahams wrote:
Use tools/build/v1/gcc-tools.jam as a working example and tools/build/v1/gcc-tools.html to understand it.
See http://www.boost.org/tools/build/v1/build_system.htm#toolset_description for other help.
Thanks for the help. I have made some progress at creating a pathscale-tools.jam, starting from mipspro-tools.jam (but keeping my eye on gcc-tools.jam, in case of link problems).
I can't figure out a couple of things about the output. Due to compiler problems I haven't finished a build, but I can see that the output files in the stage directory are being named this way:
libboost_date_time-pathscale-1_31.a
When building for the intel-linux toolset, I see 2 copies of the equivalent file:
libboost_date_time-il-1_31.a libboost_date_time-il.a
I would like to know (a) how to abbreviate 'pathscale' to 'ps' in the file names and (b) how to make a second copy of each file without the Boost version in the name. (Perhaps (b) will take care of itself, if the build ever finishes successfully.)
I got this from Rene, who knows: HTH, -- Dave Abrahams Boost Consulting http://www.boost-consulting.com
David Abrahams wrote:
I got this from Rene, who knows:
(a) You need to change the rule common-variant-tag in boost-base.jam.
Thank you. I found a 'switch $(toolset)' statement that inserts the toolset-dependent string into 'toolset-tag'. That ought to work. -- Dick Hadsell 914-259-6320 Fax: 914-259-6499 Reply-to: hadsell@blueskystudios.com Blue Sky Studios http://www.blueskystudios.com 44 South Broadway, White Plains, NY 10601
participants (2)
-
David Abrahams -
Richard Hadsell