Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <42491C9C.5000906@familiehaase.de> Date: Tue, 29 Mar 2005 11:15:08 +0200 From: "Gerrit P. Haase" Organization: Esse keine toten Tiere User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.7.3) Gecko/20040910 MIME-Version: 1.0 To: Norton Allen CC: cygwin@cygwin.com Subject: Re: gcc 3.3.3, const symbols and shared libraries References: <4246D5A0.4070409@huarp.harvard.edu> In-Reply-To: <4246D5A0.4070409@huarp.harvard.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Norton Allen wrote: > I have seen the discussions at > > http://sourceware.org/ml/cygwin/2004-09/msg01101.html > > referenced at > > http://cygwin.com/ml/cygwin/2005-03/msg00048.html > > regarding gcc 3.3.3's placement of const symbols into > rdata which then cannot be properly initialized. > This problem seems pretty fundamental. Can anyone > tell me whether there has been any followup to > this? Is it considered a cygwin problem or a > gcc problem? Has it been addressed in 3.4.1? > What are developers doing? Going back to 3.3.1? The rule is to not use const symbols in shared libraries if they are not really const;) > I ask because I just spent two days trying to > compile a number of libraries, and ran into > problems at every turn due to this bug. Gerrit -- =^..^= Action Soccer: http://www.action-soccer.de/?lv=de&id=505 (german online game) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/