This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: multiple definition of `std::__default_alloc_template<(bool)1,(int)0>::allocate(unsigned)'
- From: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- To: Benjamin Kosnik <bkoz at redhat dot com>
- Cc: libstdc++ at gcc dot gnu dot org
- Date: Wed, 1 May 2002 20:43:25 +0200 (CEST)
- Subject: Re: multiple definition of `std::__default_alloc_template<(bool)1,(int)0>::allocate(unsigned)'
On Wed, 1 May 2002, Benjamin Kosnik wrote:
>> I'm seeing this on i386-unknown-freebsd4.5 (GNU ld 2.11.2) as well as
>> i686-pc-linux-gnu (GNU ld 2.11.92.0.10, SuSE 8.0).
> %ld --version
> GNU ld version 2.12.90 20020428
>
> Can you try with newer binutils and see if the problem goes away?
binutils 2.12 don't work either, sigh.
/files/pfeifer/gcc/lib/gcc-lib/i386-unknown-freebsd4.5/3.1/../../../libstdc++.a(c++locale.o): In function `void std::__convert_to_v<long double>(char const*, long double&, std::_Ios_Iostate&, int* const&, int)':
/files/pfeifer/OBJ/i386-unknown-freebsd4.5/libstdc++-v3/include/bits/ios_base.h:123: undefined reference to `finitef'
The problem, as far as I can see, is that currently FreeBSD 4.5, SuSE
Linux 8.0, and also most probably also Debian GNU/Linux 2.2 are broken
when using default ld.
> I cannot reproduce your behavior on linux.
Does this mean you have a (small) test case that you believe will
fail for me? That would be very useful!
Else I can send you the sources where I'm seeing this problem.
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/