Problems building boost 1.36
Hi folks, I'm a systems administrator trying to build boost 1.36 for some of our engineers here who have been using version 1.35 for a while. The new version builds just fine (gcc 4.2.2 on RHEL3) without so much as an error. However, after the install we have far fewer libraries installed than we did with 1.35. The lib directory of the new version only contains 108 files as opposed to 423 in the previous version. Specifically, only the multi-threaded libs seems to get built with the new version...there are no single-threaded libraries at all. I can't find any mention of how to build these libraries in any of the documentation. Can anyone tell me if this is by design in this new version, or if I need to do anything special in order to get these to build? When building, we're not doing anything different than we did when building the previous version. Any help would be greatly appreciated. Thanks. -- Steve Gilbert Engineering Support NVIDIA Corporation ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----------------------------------------------------------------------------------
AMDG Steve Gilbert wrote:
I'm a systems administrator trying to build boost 1.36 for some of our engineers here who have been using version 1.35 for a while. The new version builds just fine (gcc 4.2.2 on RHEL3) without so much as an error. However, after the install we have far fewer libraries installed than we did with 1.35. The lib directory of the new version only contains 108 files as opposed to 423 in the previous version. Specifically, only the multi-threaded libs seems to get built with the new version...there are no single-threaded libraries at all. I can't find any mention of how to build these libraries in any of the documentation.
Can anyone tell me if this is by design in this new version, or if I need to do anything special in order to get these to build? When building, we're not doing anything different than we did when building the previous version.
To build everything use bjam --build-type=complete ... To build specific libraries use combinations of the following: debug release link=static,shared runtime-link=static,shared threading=single,multi For example bjam release link=static,shared threading=single ... builds two libraries, * single threaded release static lib * single threaded release dynamic lib In Christ, Steven Watanabe
Thank you so much! This seems to have built everything now...I'll add this to our internal documentation. Can I get a pointer on the correct way to install these? "make install" doesn't seem to know about them. Can I just copy them into the lib directory? Anything else involved? Thanks again! -- Steve Gilbert Engineering Support NVIDIA Corporation -----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Steven Watanabe Sent: Thursday, September 04, 2008 5:30 PM To: boost-users@lists.boost.org Subject: Re: [Boost-users] Problems building boost 1.36 AMDG Steve Gilbert wrote:
I'm a systems administrator trying to build boost 1.36 for some of our engineers here who have been using version 1.35 for a while. The new version builds just fine (gcc 4.2.2 on RHEL3) without so much as an error. However, after the install we have far fewer libraries installed than we did with 1.35. The lib directory of the new version only contains 108 files as opposed to 423 in the previous version. Specifically, only the multi-threaded libs seems to get built with the new version...there are no single-threaded libraries at all. I can't find any mention of how to build these libraries in any of the documentation.
Can anyone tell me if this is by design in this new version, or if I need to do anything special in order to get these to build? When building, we're not doing anything different than we did when building the previous version.
To build everything use bjam --build-type=complete ... To build specific libraries use combinations of the following: debug release link=static,shared runtime-link=static,shared threading=single,multi For example bjam release link=static,shared threading=single ... builds two libraries, * single threaded release static lib * single threaded release dynamic lib In Christ, Steven Watanabe _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----------------------------------------------------------------------------------
Hi Steve.
Can I get a pointer on the correct way to install these? "make install" doesn't seem to know about them. Can I just copy them into the lib directory? Anything else involved?
For example... to get the libraries built into the boost-root/stage/lib folder and not get the headers (you have them in your boost-root/boost folder anyway) copied anywhere use the command:
bjam stage --build-type=complete [...whatever-else-you-need...]
To get the libraries built into xxx/lib where xxx is some folder of your choice do the following:
bjam stage --stagedir=xxx --build-type=complete [...whatever-else-you-need...]
To get the libraries and headers installed into some location use the 'install' target instead of 'stage' and --prefix=xxx to choose where to install them. Run 'bjam --help' from your boost root folder or look into Boost's Jamroot file to see a more detailed of these options and more... Hope this helps. Best regards, Jurko Gospodnetić
participants (3)
-
Jurko Gospodnetić -
Steve Gilbert -
Steven Watanabe