public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Frederic Dumas <fdumas@ina.fr> To: bkoz@gcc.gnu.org Cc: gcc-prs@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 08:16:00 -0000 [thread overview] Message-ID: <20021106161606.21938.qmail@sources.redhat.com> (raw) 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
next reply other threads:[~2002-11-06 16:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-06 8:16 Frederic Dumas [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-06 9:06 Loren James Rittle 2002-11-06 6:17 ljrittle 2002-11-06 4:51 paolo 2002-11-06 4:16 fdumas
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20021106161606.21938.qmail@sources.redhat.com \ --to=fdumas@ina.fr \ --cc=bkoz@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).