Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
I am running Solaris 10 on an UltraSPARC platform. I have successfully built a 32-bit version of boost using the gcc compiler version 3.4.3. This was accomplished with the following command.
bjam “-sTOOLS=gcc” install
We typically use the Sunstudio 11 C++ 5.8 compiler to build our projects. However, we’ve been unsuccessful at getting Boost to build with this particular compiler. Hence, the reason for attempting to use gcc.
I’m very familiar with the flags we use with the Sun compiler when building our own projects. Everything we build is 64-bit. Typically, among other flags, we use –xtarget=ultra –xarch=v9 –xcode=pic32 to build a 64-bit library or executable.
Since I am not familiar at all with the gcc flags, I’m not entirely sure exactly which flags to use to build a 64-bit version for the Sun platform. Furthermore, I’ve looked through the documentation on building Boost, and can’t seem to figure out exactly what the syntax is when appling multiple compiler flags to the bjam command. Here are some samples of what I’ve tried.
bjam “-sTOOLS=gcc” “-sBUILD=<cxxflags>-mcpu=v9 –m64” install
bjam “-sTOOLS=gcc” “-sBUILD=<cxxflags>-mcpu=v9 <cxxflags>–m64” install
bjam “-sTOOLS=gcc” “-sBUILD=<cxxflags>-mcpu=v9” “-sBUILD=<cxxflags>–m64” install
bjam “-sTOOLS=gcc” “-sBUILD=<cxxflags>-mcpu=v9,–m64” install
I’m not even sure if these are the correct flags to be using, and obviously the syntax is incorrect since the output from bjam doesn’t show both of these flags on the compile lines. So, here are my questions.
1. Exactly what gcc compiler flags are necessary to build a 64-bit version for a generic sparc platform?
2. What is the exact syntax for the bjam command when applying multiple compiler flags?
Any help would be greatly appreciated. Thank you.