This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Problem with shared libraries, exceptions, and global constructors
- From: Geoff Keating <geoffk at geoffk dot org>
- To: David Edelsohn <dje at watson dot ibm dot com>
- Cc: Richard Henderson <rth at redhat dot com>, Bernd Schmidt <bernds at redhat dot com>, gcc at gcc dot gnu dot org
- Date: 18 Aug 2003 16:55:23 -0700
- Subject: Re: Problem with shared libraries, exceptions, and global constructors
- References: <gdr@integrable-solutions.net><200308181841.OAA29606@makai.watson.ibm.com>
David Edelsohn <dje@watson.ibm.com> writes:
> [Sorry for the previous reply.]
>
> >>>>> Gabriel Dos Reis writes:
>
> Gaby> Pardon the question: It is a feature? I'm pretty sure I'm seen many
> Gaby> bug reports where the symptoms described by Bernd were reported.
> Gaby> What I'm saying is that, in the small your advice it quite
> Gaby> straightforward to follow. For a large project however, I think that
> Gaby> quickly gets out of hand. Isn't there anything that can be done?
>
> I am aware of some projects that explicitly do not link with all
> dependent libraries due to circular dependencies.
That's not really a reason, because you can always create stub
libraries for bootstrapping purposes, and so long as you're careful
about the order you link everything you can get a predictable startup
sequence.
--
- Geoffrey Keating <geoffk@geoffk.org>