This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: c++/7769: using static libraries sometimes loses staticinitialization
- From: Wolfgang Bangerth <bangerth at ticam dot utexas dot edu>
- To: nobody at gcc dot gnu dot org
- Cc: gcc-prs at gcc dot gnu dot org,
- Date: 20 Dec 2002 16:46:04 -0000
- Subject: Re: c++/7769: using static libraries sometimes loses staticinitialization
- Reply-to: Wolfgang Bangerth <bangerth at ticam dot utexas dot edu>
The following reply was made to PR c++/7769; it has been noted by GNATS.
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: Hal Black <black@ieee.org>
Cc: gcc-bugs@gcc.gnu.org, <hablack@vt.edu>, <gcc-gnats@gcc.gnu.org>
Subject: Re: c++/7769: using static libraries sometimes loses static
initialization
Date: Fri, 20 Dec 2002 10:41:00 -0600 (CST)
On Thu, 19 Dec 2002, Hal Black wrote:
> > This is not a bug. When you want that a particular
> > object file (possibly within an archive) is pulled into you
> > executable for sure, then you have to reference an object
> > inside it.
>
> This is a bug.
> [...]
> Correct, the compiler is fine, it is the linker that is not working
> correctly under the circumstances described above.
This is just how Unix has worked forever. If you want that changed, file a
report with the binutils people, but I think this is just how it is.
W.
-------------------------------------------------------------------------
Wolfgang Bangerth email: bangerth@ticam.utexas.edu
www: http://www.ticam.utexas.edu/~bangerth