This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/28377] unresolved symbols in libstdc++, shared lib link strategy of libgcc.a
- From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 14 Jul 2006 09:14:33 -0000
- Subject: [Bug other/28377] unresolved symbols in libstdc++, shared lib link strategy of libgcc.a
- References: <bug-28377-3337@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #3 from ebotcazou at gcc dot gnu dot org 2006-07-14 09:14 -------
> The test case is the build of gcc 4.0.3 on Solaris 8, including the
> libstdc++.so build.
This is known to work, e.g. http://gcc.gnu.org/gcc-4.0/buildstat.html
> env LD_LIBRARY_PATH=<path-where-libgcc_s.so-is> ldd -r -v .../libstdc++-IFX.so
>
> and you will see __eprintf unresolved.
>
> I will try to put together a test case to build a shared lib from C source
> code that contains #include <assert.h> and some assertion to demonstrate the
> the resulting libXXX.so has an unresolved reference to __eprintf.
This one is more annoying. You should make sure that you don't have an "old"
<assert.h> lying around somewhere. Which compiler do you start from? Do you
bootstrap or only build the new compiler?
--
ebotcazou at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ebotcazou at gcc dot gnu dot
| |org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28377