From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28927 invoked by alias); 20 Dec 2002 16:46:06 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 28913 invoked by uid 71); 20 Dec 2002 16:46:04 -0000 Date: Fri, 20 Dec 2002 08:46:00 -0000 Message-ID: <20021220164604.28912.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Wolfgang Bangerth Subject: Re: c++/7769: using static libraries sometimes loses static initialization Reply-To: Wolfgang Bangerth X-SW-Source: 2002-12/txt/msg01105.txt.bz2 List-Id: The following reply was made to PR c++/7769; it has been noted by GNATS. From: Wolfgang Bangerth To: Hal Black Cc: gcc-bugs@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