Symbol visibility build failure on Solaris

[Daniel Jacobowitz]

On Tue, Jun 17, 2003 at 02:12:46PM -0400, Daniel Jacobowitz wrote:
> On Tue, Jun 17, 2003 at 01:59:27PM -0400, David Edelsohn wrote:
> > >>>>> Daniel Jacobowitz writes:
> > 
> > Daniel> Does this mean that we need to move __eprintf from LIB2FUNCS_ST to
> > Daniel> LIB2FUNCS_2, or that -shared-libgcc should also pull in libgcc.a?
> > 
> > 	Specifying -shared-libgcc and linking with libgcc.a will cause
> > problems on some platforms.
> 
> Thanks.  That's right out, then.
> 
> The current state of the world is that using a 2.95.3-era <assert.h>
> does not mix with -shared-libgcc.  I think that either we need to solve
> it on the one end (stop using assert in libstdc++ and avoid the issue)

I feel pretty dumb, having just noticed that GCC 3.3 no longer uses
assert in libstdc++-v3 headers.  I was building 3.2.2 before moving up
to 3.3.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer