Boost 1.36.0 with Linux 64bits
Hi all, I would like to know if the boost 1.36.0 is working well with Linux 64 bits. If I want to compile with boost 1.36.0 and Linux 64 bits, how should I install the boost 1.36.0? Is it the same to 32 bits machine? Please, if someone knows that, let me know. Thanks,
On Thursday 21 January 2010 15:46:13 JongKwan Kim wrote:
I would like to know if the boost 1.36.0 is working well with Linux 64 bits.
Yes, but using 1.42 (to be released in a few days) will likely save you headaches in the future since there have a been a large number of bug-fixes since 1.36.
If I want to compile with boost 1.36.0 and Linux 64 bits, how should I install the boost 1.36.0?
http://www.boost.org/doc/libs/1_36_0/more/getting_started/unix-variants.html Regards, Ravi
Thanks for your answer.
I need to use the Boost 1.36.0, but I have still problems.
In fact, I have already run my code with Boost 1.36.0 with 32 bits machine.
To run my code with 64 bits computer, I follow your comment.
1. download Boost1.36.0.tar.bz2 and unzip this
2. download pre-compiled bjam and move it to Boost1.36.0 directory
3. $cd /Boost1.36.0
4. $ ./bjam --build-dir=/build-boost --toolset=gcc --build-type=complete
stage
So, the Boost Library is installed, I think....
But, I do not know how can I use this.
When I install with simple way, there are only 2 directory - include and
lib, but using ./bjam there are lots of directories /boost/bin.v2/libs/.....
Do I have to assign each path separately?
Thanks,
On Sat, Jan 23, 2010 at 2:53 PM, Ravi
On Thursday 21 January 2010 15:46:13 JongKwan Kim wrote:
I would like to know if the boost 1.36.0 is working well with Linux 64 bits.
Yes, but using 1.42 (to be released in a few days) will likely save you headaches in the future since there have a been a large number of bug-fixes since 1.36.
If I want to compile with boost 1.36.0 and Linux 64 bits, how should I install the boost 1.36.0?
http://www.boost.org/doc/libs/1_36_0/more/getting_started/unix-variants.html
Regards, Ravi
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
On Fri, Jan 29, 2010 at 12:55 AM, JongKwan Kim
Thanks for your answer.
I need to use the Boost 1.36.0, but I have still problems. In fact, I have already run my code with Boost 1.36.0 with 32 bits machine.
To run my code with 64 bits computer, I follow your comment. 1. download Boost1.36.0.tar.bz2 and unzip this 2. download pre-compiled bjam and move it to Boost1.36.0 directory 3. $cd /Boost1.36.0 4. $ ./bjam --build-dir=/build-boost --toolset=gcc --build-type=complete stage
So, the Boost Library is installed, I think.... But, I do not know how can I use this.
When I install with simple way, there are only 2 directory - include and lib, but using ./bjam there are lots of directories /boost/bin.v2/libs/.....
Do I have to assign each path separately?
Let's assume you had extracted Boost compressed file to
/home/yourname/boost_1_36_0 (let's call it Boost_Root_Path).
1) Under Boost_Root_Path, were you able to find a "boost" directory tree
with various library header files? For compiling my C++ program, I will set
Boost_Root_Path as header files searching path
(-I/home/yourname/boost_1_36_0), while my program's code will include those
header files by specifying thing similar to the following line:
#include
Thanks,
On Sat, Jan 23, 2010 at 2:53 PM, Ravi
wrote: On Thursday 21 January 2010 15:46:13 JongKwan Kim wrote:
I would like to know if the boost 1.36.0 is working well with Linux 64 bits.
Yes, but using 1.42 (to be released in a few days) will likely save you headaches in the future since there have a been a large number of bug-fixes since 1.36.
If I want to compile with boost 1.36.0 and Linux 64 bits, how should I install the boost 1.36.0?
http://www.boost.org/doc/libs/1_36_0/more/getting_started/unix-variants.html
Regards, Ravi
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
Thank you for your comment.
It is linked to my code, but I still have a "Segmentation fault". I do not
know why.....
As I said before, I am trying to my code on 64 bits computer.
My code was running well on 32 bits machine with Boost Library 1.36.0 and
GSLibrary, but it has a "Segmentation fault" on 64 bits machine.
I have modify the argument to
LDFLAGS="-m64",CFLAGS="-m64",CXXFLAGS="-m64",FFLAGS="-m64".
Do you have any idea to solve this?
If you have one, please let me know that.
Thanks,
On Thu, Jan 28, 2010 at 10:25 AM, Shiou Ming Lee
On Fri, Jan 29, 2010 at 12:55 AM, JongKwan Kim
wrote: Thanks for your answer.
I need to use the Boost 1.36.0, but I have still problems. In fact, I have already run my code with Boost 1.36.0 with 32 bits machine.
To run my code with 64 bits computer, I follow your comment. 1. download Boost1.36.0.tar.bz2 and unzip this 2. download pre-compiled bjam and move it to Boost1.36.0 directory 3. $cd /Boost1.36.0 4. $ ./bjam --build-dir=/build-boost --toolset=gcc --build-type=complete stage
So, the Boost Library is installed, I think.... But, I do not know how can I use this.
When I install with simple way, there are only 2 directory - include and lib, but using ./bjam there are lots of directories /boost/bin.v2/libs/.....
Do I have to assign each path separately?
Let's assume you had extracted Boost compressed file to /home/yourname/boost_1_36_0 (let's call it Boost_Root_Path). 1) Under Boost_Root_Path, were you able to find a "boost" directory tree with various library header files? For compiling my C++ program, I will set Boost_Root_Path as header files searching path (-I/home/yourname/boost_1_36_0), while my program's code will include those header files by specifying thing similar to the following line: #include
2) Under Boost_Root_Path, did your Boost build produce a "stage/lib" directory with library binary files? If yes, then you can specify it as your library searching path (-L/home/yourname/boost_1_36_0/stage/lib).
Thanks,
On Sat, Jan 23, 2010 at 2:53 PM, Ravi
wrote: On Thursday 21 January 2010 15:46:13 JongKwan Kim wrote:
I would like to know if the boost 1.36.0 is working well with Linux 64 bits.
Yes, but using 1.42 (to be released in a few days) will likely save you headaches in the future since there have a been a large number of bug-fixes since 1.36.
If I want to compile with boost 1.36.0 and Linux 64 bits, how should I install the boost 1.36.0?
http://www.boost.org/doc/libs/1_36_0/more/getting_started/unix-variants.html
Regards, Ravi
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
Mika Heiskanen wrote:
JongKwan Kim wrote:
It is linked to my code, but I still have a "Segmentation fault". I do not know why.....
Use valgrind or some other memory debugging tool to find out where the program does the segmentation fault.
valgrind is somewhat of an overkill as first measure. I'd recommend using a debugger, for a start. And, unless debugger shows something strange, I'd assume this is not a problem with how Boost is build, or with 32/64 modes. - Volodya
Vladimir Prus wrote:
Mika Heiskanen wrote:
It is linked to my code, but I still have a "Segmentation fault". I do not know why..... Use valgrind or some other memory debugging tool to find out where the
JongKwan Kim wrote: program does the segmentation fault.
valgrind is somewhat of an overkill as first measure. I'd recommend using a debugger, for a start. And, unless debugger shows something strange, I'd assume this is not a problem with how Boost is build, or with 32/64 modes.
In my experience for example gdb is not as reliable as valgrind for showing the exact line where the segmentation fault occurs, I've gotten segmentation fault notices in gdb in incorrect places several times, usually not distant from the actual location, but nevertheless the exact line reported by valgrind is much more useful information. --> Mika
participants (5)
-
JongKwan Kim
-
Mika Heiskanen
-
Ravi
-
Shiou Ming Lee
-
Vladimir Prus