Hi all, I'm hadn't been following the development of Boost's installation process and just went from 1.38 to 1.39 and realized the steps that I had written down no longer work. :-) I'm glad that the process was being looked into, but could someone help me with a couple of things? First, I use mpi and use to edit $BOOST/user-config.jam and put "using mpi ;" at the end to get it to compile. I didn't do this and I got a similar warning as before even though I ran: ./bootstrap.sh --with-libraries=graph,mpi,program_options,serialization Does "mpi" in it have no effect? After it finished, it seems the other 3 were made, but not mpi. Should I add "using mpi ;" still? [In $BOOST, I now notice there is no user-config.jam but a project-config.jam.] And the other thing I use to do was to edit the Makefile by adding "--layout=system" so that the generated libraries do not indicate the compiler version. (I did read the discussion earlier this month and I'm now wondering if it's bad practice to do this? I would like libboost_program_options-mt.so instead of libboost_program_options-gcc43-mt.so .) How do I do this with bootstrap.sh/bjam? Thank you! Ray
Raymond Wan wrote:
Hi all,
I'm hadn't been following the development of Boost's installation process and just went from 1.38 to 1.39 and realized the steps that I had written down no longer work. :-) I'm glad that the process was being looked into, but could someone help me with a couple of things?
First, I use mpi and use to edit $BOOST/user-config.jam and put "using mpi ;" at the end to get it to compile. I didn't do this and I got a similar warning as before even though I ran:
./bootstrap.sh --with-libraries=graph,mpi,program_options,serialization
Does "mpi" in it have no effect? After it finished, it seems the other 3 were made, but not mpi. Should I add "using mpi ;" still? [In $BOOST, I now notice there is no user-config.jam but a project-config.jam.]
You should edit either user-config.jam placed in your home directory, or edit project-config.jam that is in boost root directory.
And the other thing I use to do was to edit the Makefile by adding "--layout=system" so that the generated libraries do not indicate the compiler version. (I did read the discussion earlier this month and I'm now wondering if it's bad practice to do this? I would like libboost_program_options-mt.so instead of libboost_program_options-gcc43-mt.so .)
How do I do this with bootstrap.sh/bjam?
At present, you have to pass --layout=system to bjam invocation. Specifying the value of --layout option inside project-config.jam is not presently possible; planned for 1.40. - Volodya
Hi Volodya, Vladimir Prus wrote:
Does "mpi" in it have no effect? After it finished, it seems the other 3 were made, but not mpi. Should I add "using mpi ;" still? [In $BOOST, I now notice there is no user-config.jam but a project-config.jam.]
You should edit either user-config.jam placed in your home directory, or edit project-config.jam that is in boost root directory.
And the other thing I use to do was to edit the Makefile by adding "--layout=system" so that the generated libraries do not indicate the
[...]
At present, you have to pass --layout=system to bjam invocation. Specifying the value of --layout option inside project-config.jam is not presently possible; planned for 1.40.
Thank you for your help! Both did the trick! By the way, not a big problem, but the libraries are being placed in /lib, despite me using --prefix in both the bootstrap.sh command and bjam (I tried both because doing it for either one wasn't working :-) ). In both cases, I did: --prefix=/usr/local/boost_1_39_0 . Is this a bug that I should report or does this switch do something else? Thank you! Ray
Raymond Wan wrote:
Hi Volodya,
Vladimir Prus wrote:
Does "mpi" in it have no effect? After it finished, it seems the other 3 were made, but not mpi. Should I add "using mpi ;" still? [In $BOOST, I now notice there is no user-config.jam but a project-config.jam.]
You should edit either user-config.jam placed in your home directory, or edit project-config.jam that is in boost root directory.
And the other thing I use to do was to edit the Makefile by adding "--layout=system" so that the generated libraries do not indicate the
[...]
At present, you have to pass --layout=system to bjam invocation. Specifying the value of --layout option inside project-config.jam is not presently possible; planned for 1.40.
Thank you for your help! Both did the trick!
By the way, not a big problem, but the libraries are being placed in /lib, despite me using --prefix in both the bootstrap.sh command and bjam (I tried both because doing it for either one wasn't working :-) ). In both cases, I did: --prefix=/usr/local/boost_1_39_0 . Is this a bug that I should report or does this switch do something else?
It is a known bug, fixed in SVN; passing additional --libdir option is the workaround. - Volodya
Hi Volodya, Vladimir Prus wrote:
By the way, not a big problem, but the libraries are being placed in /lib, despite me using --prefix in both the bootstrap.sh command and bjam (I tried both because doing it for either one wasn't working :-) ). In both cases, I did: --prefix=/usr/local/boost_1_39_0 . Is this a bug that I should report or does this switch do something else?
It is a known bug, fixed in SVN; passing additional --libdir option is the workaround.
Ah, I see; I'll give the --libdir option a try rather than retrieving from the SVN repository. Thank you! Ray
participants (2)
-
Raymond Wan -
Vladimir Prus