do i need to specify some option to include the compiler , architecture and model while building the boost? Please help.i will be really thankful to you. Roland Bock-2 wrote:

manish4gupta wrote:

...

Is boost library 1.39 compatible on ia64 machine(itanium) with compiler gcc 3.4.6 on a Redhat Enterprise Linux 4 Update 5?

The list of *tested* compilers is here:

http://www.boost.org/users/news/version_1_39_0

There is no list of "compatible" compilers that I am aware of. _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

-- View this message in context: http://www.nabble.com/compatibility-of-boost-1.39-tp25696866p25702064.html Sent from the Boost - Users mailing list archive at Nabble.com.

I have updated my compiler to 4.1.2 g++ -v Using built-in specs. Target: ia64-unknown-linux-gnu Configured with: ./configure --prefix=/usr/local/ Thread model: posix gcc version 4.1.2 still i am using boost 1.39 Following program is getting compiled now but when i run it is is getting hang. #include #include #include #include #include <iostream> using namespace boost::interprocess; //Typedefs of allocators and containers typedef managed_shared_memory::segment_manager segment_manager_t; typedef allocator void_allocator; typedef allocator char_allocator; typedef basic_string char_string; //Definition of the map holding a string as key and complex_data as mapped type typedef std::pair map_value_type; typedef allocator map_value_type_allocator; typedef map< char_string, int, std::less, map_value_type_allocator> complex_map_type; int main () { shared_memory_object::remove("MySharedMemory"); //Create shared memory managed_shared_memory segment(create_only,"MySharedMemory", 65536); //An allocator convertible to any allocator type void_allocator alloc_inst (segment.get_segment_manager()); //Construct the shared memory map and fill it complex_map_type *mymap = segment.construct("MyMap")(std::less(), alloc_inst); char_string cs("test", alloc_inst); for(int i = 0; i < 100; ++i) { mymap->insert(std::pair(cs , i)); } return 0; } while on 32 bit machine it is working fine.How can i overcome such pblm? Thanks in advance. _________ Roland Bock-2 wrote:

manish4gupta wrote:

...

do i need to specify some option to include the compiler , architecture and model while building the boost? Please help.i will be really thankful to you.

I don't think so, I never do that, and it works fine for me (Ubuntu-8.04, 64bit). But you have to read the documentation if you want to be sure.

If some boost headers are not compiled on your system, you could update to boost-1.40 as suggested by Sergey Nikulov. See if that works out.

If not, well, the gcc 3.4 is not as good as the 4.x versions. So you might have to think about upgrading your compiler.

Regards,

Roland

...

Roland Bock-2 wrote:

...

manish4gupta wrote:

...

Is boost library 1.39 compatible on ia64 machine(itanium) with compiler gcc 3.4.6 on a Redhat Enterprise Linux 4 Update 5?

The list of *tested* compilers is here:

http://www.boost.org/users/news/version_1_39_0

There is no list of "compatible" compilers that I am aware of. _______________________________________________ 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

-- View this message in context: http://www.nabble.com/compatibility-of-boost-1.39-tp25696866p25709805.html Sent from the Boost - Users mailing list archive at Nabble.com.

Hi, I have installed the new boost library(1_40).still i am getting the same hand error. Now my library are in /usr/local/include and library in /usr/local/lib compilation OK ///// g++ -g3 -O0 -I /usr/local/include boostindex.cpp -o boostindex -L /usr/local/lib -lrt run pblm (getting hang) [manish@synabase-dev1 main]$ gdb boostindex GNU gdb Red Hat Linux (6.3.0.0-1.143.el4rh) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "ia64-redhat-linux-gnu"...Using host libthread_db library "/lib/tls/libthread_db.so.1". (gdb) run Starting program: /data/project/0811_gbrowser/data_repository/main/boostindex Reading symbols from shared object read from target memory...done. Loaded system supplied DSO at 0xa000000000000000 [Thread debugging using libthread_db enabled] [New Thread 2305843009215997536 (LWP 1209)] when i kill it i am getting following error message. Program received signal SIGINT, Interrupt. [Switching to Thread 2305843009215997536 (LWP 1209)] 0xa000000000010641 in __kernel_syscall_via_break () I think there is some threading pblm. I don't know much abt this. How can i solve my pblm. Please help...... Roland Bock-2 wrote:

manish4gupta wrote:

...

I have updated my compiler to 4.1.2 g++ -v Using built-in specs. Target: ia64-unknown-linux-gnu Configured with: ./configure --prefix=/usr/local/ Thread model: posix gcc version 4.1.2 still i am using boost 1.39 Following program is getting compiled now but when i run it is is getting hang.

It also runs fine on my machine (64bit).

I would assume library incompatibilities after the compiler update. Personally, I would run a debugger to see where it hangs. Take a closer look at the respective library.

Maybe it is just a question of LD_LIBRARY_PATH, maybe you'll have to recompile a library with the new compiler (but beware, other programs might depend on the old version!). I guess, you'll have to figure out that one by yourself.

Since such problems are sometimes very hard to solve, I tend to recompile all dependencies (or in your case update to a system which provides the compiler I need).

Regards,

Roland _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

-- View this message in context: http://www.nabble.com/compatibility-of-boost-1.39-tp25696866p25711804.html Sent from the Boost - Users mailing list archive at Nabble.com.

manish4gupta wrote:

Thanks...

May i Know do u have Ia64 machine so that i can again look it into it ..

Intel Xeon QuadCore, DualCore and some 64bit AMD single core machine. I doubt that the processor is to blame in your case. For the debugger: run the process, then attach the debugger to the process and call bt. This will give you the current call stack and hopefully some idea where to look further. Regards, Roland

As suggested i put bt option still .. #0 0xa000000000010641 in __kernel_syscall_via_break () #1 0x20000000004ddfa0 in sched_yield () from /lib/tls/libc.so.6.1 #2 0x400000000002c3b0 in boost::interprocess::detail::thread_yield () at /usr/local/include/boost/interprocess/detail/os_thread_functions.hpp:145 #3 0x400000000002c4f0 in boost::interprocess::interprocess_mutex::lock ( this=0x2000000000700050) at /usr/local/include/boost/interprocess/sync/emulation/interprocess_mutex.hpp:39 #4 0x40000000000375b0 in boost::interprocess::interprocess_recursive_mutex::lock (this=0x2000000000700050) at /usr/local/include/boost/interprocess/sync/emulation/interprocess_recursive_mutex.hpp:54 #5 0x40000000000376c0 in scoped_lock (this=0x60000fffffffa730, m=@0x2000000000700050) at /usr/local/include/boost/interprocess/sync/scoped_lock.hpp:78 #6 0x400000000003b250 in boost::interprocess::segment_manager, boost::interprocess::iset_index>::priv_generic_named_construct<char> (this=0x2000000000700010, type=1, name=0x4000000000040030 "MyMap", num=1, try2find=false, dothrow=true, table=@0x60000fffffffa8c0, index=@0x2000000000700068, is_intrusive= {> = {static value = <optimized out>}, static value = <optimized out>}) ---Type <return> to continue, or q <return> to quit--- at /usr/local/include/boost/interprocess/segment_manager.hpp:1071 #7 0x400000000003bfb0 in boost::interprocess::segment_manager, boost::interprocess::iset_index>::priv_generic_construct (this=0x2000000000700010, name=0x4000000000040030 "MyMap", num=1, try2find=false, dothrow=true, table=@0x60000fffffffa8c0) at /usr/local/include/boost/interprocess/segment_manager.hpp:743 #8 0x400000000003c0f0 in boost::interprocess::segment_manager, boost::interprocess::iset_index>::generic_construct, boost::interprocess::iset_index> > >, boost::interprocess_container::basic_string, boost::interprocess::iset_index> > >, std::less, boost::interprocess::iset_index> > > >, boost::interprocess::allocator, boost::interprocess::iset_index> > > const, boost::interprocess_container::basic_string, boost::interprocess::iset_index> > > >, boost::interprocess::segment_manager, boost::interprocess::iset_index> > > > (this=0x2000000000700010, name=0x4000000000040030 "MyMap", num=1, try2find=false, dothrow=true, table=@0x60000fffffffa8c0) at /usr/local/include/boost/interprocess/segment_manager.hpp:684 #9 0x400000000003c280 in boost::interprocess::detail::named_proxy, boost::interprocess::iset_index>, boost::interprocess_container::multimap, boost::interprocess::iset_index> > >, boost::interprocess_container::basic_string, boost::interprocess::iset_index> > >, std::less, boost::interprocess::iset_index> > > >, boost::interprocess::allocator, boost::interprocess::iset_index> > > const, boost::interprocess_container::basic_string, boost::interprocess::iset_index> > > >, boost::interprocess::segment_manager, boost::interprocess::iset_index> > >, false>::operator(), boost::interprocess::iset_index> > > >, boost::interprocess::allocator---Type <return> to continue, or q <return> to quit--- , boost::interprocess::iset_index> > > (this=0x60000fffffffa9b8, p0=@0x60000fffffffa9a9, p1=@0x60000fffffffa9d8) at /usr/local/include/boost/preprocessor/iteration/detail/local.hpp:40 #10 0x4000000000002f00 in main (argc=1, argv=0x60000fffffffb8a8) at boostindex.cpp:24 I am getting the above on keeping bt.Please suggest what can i do. Since this is beyond my understanding. manish4gupta wrote:

Ok I will try but still i feel the process u are using are all x86. As far as doc is concerned for x86 we do have example while building like address model and architecture but for ia64 no such example.Any as u suggested to recompile with debugger using bt option, I will follow that.

Roland Bock-2 wrote:

...

manish4gupta wrote:

...

Thanks...

May i Know do u have Ia64 machine so that i can again look it into it ..

Intel Xeon QuadCore, DualCore and some 64bit AMD single core machine. I doubt that the processor is to blame in your case.

For the debugger:

run the process, then attach the debugger to the process and call bt. This will give you the current call stack and hopefully some idea where to look further.

Regards,

Roland _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

-- View this message in context: http://www.nabble.com/compatibility-of-boost-1.39-tp25696866p25745829.html Sent from the Boost - Users mailing list archive at Nabble.com.

I have another machine with Red hat 5. There i installed the boost and it is working fine. Thank you very much for your suggestion for troubleshooting my pblm. regards Roland Bock-2 wrote:

manish4gupta wrote:

...

As suggested i put bt option still ..

As I said earlier, this is going to be tough to figure out and I don't know what next steps you should take on your system.

But just to be sure: this is what you get when run run the program, wait a few seconds, then attach the debugger and then type bt? Try

thread apply all bt (this shows the backtrace for all threads)

If that is still not giving more hints, I can't help in this direction.

What you could do: Either install a more recent version of Linux 64bit on your machine or install VMWare or something similar with a more recent Linux version. If either of it runs, fine. Otherwise, maybe there is a problem with the processor (but I still doubt that).

To solve this in a more deductive way, you will have to learn a lot more about how (dynamic) linking works. I can't help here.

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

-- View this message in context: http://www.nabble.com/compatibility-of-boost-1.39-tp25696866p25746953.html Sent from the Boost - Users mailing list archive at Nabble.com.