This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Symbol visibility build failure on Solaris
- From: Richard Henderson <rth at redhat dot com>
- To: gcc at gcc dot gnu dot org
- Date: Tue, 17 Jun 2003 15:50:08 -0700
- Subject: Re: Symbol visibility build failure on Solaris
- References: <20030617175510.GA5940@nevyn.them.org>
On Tue, Jun 17, 2003 at 01:55:10PM -0400, Daniel Jacobowitz wrote:
> - My installed GCC is 2.95.3. It has an <assert.h> which references
> __eprintf.
...
> - stl-inst.o, when compiled, has two calls to assert which reference
> __eprintf. But it's linked with -shared-libgcc, so they are unresolved.
So why is the build of stl-inst.o picking up 2.95's assert.h?
You *should* be picking up /usr/include/assert.h, which should
not reference __eprintf.
> Does this mean that we need to move __eprintf from LIB2FUNCS_ST to
> LIB2FUNCS_2, or that -shared-libgcc should also pull in libgcc.a?
Absolutely not.
r~