This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Patch] bitmap_allocator.


Sorry once again! False alarm! The LD_LIBRARY_PATH on my machine was
pointing to the .so.6 file for gcc3.4, hence the screw up and errors and
stuff!

I wish this linker thing was a bit easier!

Paolo, is the patch Ok?



On Wed, 2004-10-13 at 15:52, Dhruv Matani wrote:
> Ok, I've run into some problems!
> 
> When I run a file compiled using gcc4.0, I get the following error:
> ./a.out: /opt/gcc-3.4/lib/libstdc++.so.6: no version information
> available (required by ./a.out)
> ./a.out: /opt/gcc-3.4/lib/libstdc++.so.6: no version information
> available (required by ./a.out)
> ./a.out: /opt/gcc-3.4/lib/libstdc++.so.6: no version information
> available (required by ./a.out)
> ./a.out: relocation error: ./a.out: symbol
> _ZN9__gnu_cxx9free_list6_M_getEj, version GLIBCXX_3.4.3 not defined in
> file libstdc++.so.6 with link time reference
> 
> I assume that this has something to do with some symbol not defined with
> link-time reference. Probably the lines that I added in linker.map.gnu
> are not sufficient, and I need to add some more? I saw the ones for
> __mt_alloc, and there are 2 for the initialize function. So I suppose
> that I should have the link-time version as well. Now, the question is
> how do I get the names?
> 
> BTW, I got the current names by compiling using -S and seeing the
> generated asm output.
> 
> 
> On Wed, 2004-10-13 at 14:22, Dhruv Matani wrote:
> > Hello,
> > 	I have attached a working patch for the bitmap_allocator. Compiled as
> > default on gcc4.0 x86-Linux.
> > 
> > Could not test using make check because of certain reasosn that I am
> > looking into(the allocator is fine, make check does not work).
> > 
> > Could run make check-performance fine! However, 1 file failed for all
> > the 5 allocators. This probably has nothing to do with the allocator
> > itself. Maybe the file itself is faulty.
-- 
        -Dhruv Matani.
http://www.geocities.com/dhruvbird/

The price of freedom is responsibility, but it's a bargain, because
freedom is priceless. ~ Hugh Downs


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]