This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/20237] Problem with order of destruction in shared object.
- From: "james dot kanze at free dot fr" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 3 Apr 2005 11:04:39 -0000
- Subject: [Bug c++/20237] Problem with order of destruction in shared object.
- References: <20050227185715.20237.james.kanze@free.fr>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From james dot kanze at free dot fr 2005-04-03 11:04 -------
Subject: Re: Problem with order of destruction in shared object.
pinskia at gcc dot gnu dot org wrote:
> ------- Additional Comments From pinskia at gcc dot gnu dot org
2005-02-27 19:45 -------
> How did you configure gcc? Did you use --enable-__cxa_atexit?
Sorry for the delay in the response. I didn't actually know how
the gcc was set up, since it was installed as part of my Linux
distribution. Since I wanted to upgrade anyway, I decided to
wait until I upgraded, use --enable-__cax_atexit for the
upgrade, and report back.
With 3.4.3 and --enable-__cax_atexit, it works.
So I guess you can mark the error as "resolved: user error."
(One might ask why a Linux distribution is so configured, but
that's Linux for you.)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20237