From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7414 invoked by alias); 11 Apr 2010 10:18:20 -0000 Received: (qmail 7363 invoked by uid 48); 11 Apr 2010 10:18:04 -0000 Date: Sun, 11 Apr 2010 10:18:00 -0000 Message-ID: <20100411101804.7362.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug other/42333] complex division failure on darwin10 with -lm In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "iains at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-04/txt/msg01065.txt.bz2 ------- Comment #36 from iains at gcc dot gnu dot org 2010-04-11 10:18 ------- (In reply to comment #33) > (In reply to comment #32) > > Note that when using the patch in comment #22 triggers pr43254: another side > effect of -lm is to prevent the run of dsymutil even with -g. my 0,02 euro... 1. the whole dsymutil thing is a mess and needs sorting out separately - it's not being run at all for Fortran at the moment - and it's inconsistent in any event (not run when only objects are present on the cl, for e.g.) .. I'm going to take a look at that - but need to discuss with people what the 'correct' behavior should be. 2. we should test what is intended: (a) ergo Jack should submit his patch (at comment 23) to DejaGnu - if -lm is not needed on Darwin > x it should not be applied (b) whilst it is "the User's Problem" if they put the wrong libraries on the C/L, IMO we should try to help them .. therefore we should control the placement and/or inclusion of lm (this is already done for Fortran and we have a "" don't include for g++ - so there's a precedent). 3. maybe we need to look at how to work around the debug generation for darwin < 10 ; it's unlikely that dsymutil will be updated on those systems and, as of now, it's not part of the Open Source stuff so we can't fix it ourselves. ===== assuming people agree with the philosophy of 2. --- on the "How To" side. ===== It seems one can't use %