Re: libstdc++/8475: hash_map error message at run time about __default_alloc_template/force_new not defined

[Frederic Dumas <fdumas at ina dot fr>]

The following reply was made to PR libstdc++/8475; it has been noted by GNATS.

From: Frederic Dumas <fdumas@ina.fr>
To: ljrittle@gcc.gnu.org, bkoz@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc: paolo@gcc.gnu.org
Subject: Re: libstdc++/8475: hash_map  error message at run time about 
 __default_alloc_template/force_new not defined
Date: Wed, 06 Nov 2002 17:01:41 +0100

 ljrittle@gcc.gnu.org wrote:
 > 
 > Synopsis: hash_map  error message at run time about __default_alloc_template/force_new not defined
 > 
 > State-Changed-From-To: analyzed->closed
 > State-Changed-By: ljrittle
 > State-Changed-When: Wed Nov  6 06:17:38 2002
 > State-Changed-Why:
 >     Not a bug.  Please ensure that you have built and then
 >     run against the same library.  I can "reproduce" your
 >     PR if I compile and link your example against
 >     g++ 3.3 but then attempt to run-time link against the
 >     3.2.1 version of libstdc++-v3.  This can happen if, e.g.
 >     you installed 3.2.1 in /usr/local but 3.3 somewhere else.
 > 
 >     If the above doesn't cover your situation, then:
 >     Benjamin installed a patch to properly export
 >     __default_alloc_template::_S_force_new on 2002-11-04
 >     which was before the date of your snapshot.
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8475
 
 That was it, thanks. An earlier libstdc++ was in /usr/lib whereas the
 correct one was in /usr/local/lib. I set LD_LIBRARY_PATH to
 /usr/local/lib and it works fine now (with the last mainline/branch that
 I installed meanwhile).
 Maybe 'make install' of gcc could set a default dynamic link library
 path to its install. path?
 Best regards,
 Frederic