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

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

[Frederic Dumas]

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

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

[Loren James Rittle]

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

From: Loren James Rittle <rittle@latour.rsch.comm.mot.com>
To: bkoz@gcc.gnu.org, fdumas@ina.fr, gcc-bugs@gcc.gnu.org,
   gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, ljrittle@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, 6 Nov 2002 10:56:22 -0600 (CST)

 >Maybe 'make install' of gcc could set a default dynamic link library
 >path to its install. path?
 
 Just to give you a final response.  The position of the FSF gcc
 mainatiners is to not do this for a wide range of reasons.  However,
 I'm going to have to ask you to review the manual and past list traffic.

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

[ljrittle]

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

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

[paolo]

Synopsis: hash_map  error message at run time about __default_alloc_template/force_new not defined

Responsible-Changed-From-To: unassigned->bkoz
Responsible-Changed-By: paolo
Responsible-Changed-When: Wed Nov  6 04:51:49 2002
Responsible-Changed-Why:
    Linker wizard ;)
State-Changed-From-To: open->analyzed
State-Changed-By: paolo
State-Changed-When: Wed Nov  6 04:51:49 2002
State-Changed-Why:
    Benjamin, I can't reproduce this with mainline/branch and
    glibc2.3.1, binutils2.13.90.0.10.
    Could you possibly have a look?
    Thanks, Paolo.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8475

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

[fdumas]

>Number:         8475
>Category:       libstdc++
>Synopsis:       hash_map  error message at run time about __default_alloc_template/force_new not defined
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Nov 06 04:16:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Frederic Dumas
>Release:        gcc (GCC) 3.3 20021029
>Organization:
>Environment:
linux P4
>Description:
#include <ext/hash_map>
using namespace __gnu_cxx;
template class hash_map< int, int >;
int main() { };

> g++ -O3 test_hash.cpp -o test_hash
> ./test_hash
./test_hash: relocation error: ./test_hash: symbol _ZNSt24__default_alloc_templateILb1ELi0EE12_S_force_newE, version GLIBCPP_3.2 not defined in file libstdc++.so.5 with link time reference

>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: