From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29070 invoked by alias); 27 Mar 2012 09:29:11 -0000 Received: (qmail 29054 invoked by uid 22791); 27 Mar 2012 09:29:10 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from mel.act-europe.fr (HELO mel.act-europe.fr) (194.98.77.210) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 27 Mar 2012 09:28:57 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-smtp.eu.adacore.com (Postfix) with ESMTP id 64578290079; Tue, 27 Mar 2012 11:29:00 +0200 (CEST) Received: from mel.act-europe.fr ([127.0.0.1]) by localhost (smtp.eu.adacore.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id awIupHs0fOBh; Tue, 27 Mar 2012 11:29:00 +0200 (CEST) Received: from ulanbator.act-europe.fr (ulanbator.act-europe.fr [10.10.1.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mel.act-europe.fr (Postfix) with ESMTP id 270AC290074; Tue, 27 Mar 2012 11:29:00 +0200 (CEST) Subject: Re: [Patch V2] libgfortran: do not assume libm Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: text/plain; charset=us-ascii From: Tristan Gingold In-Reply-To: Date: Tue, 27 Mar 2012 09:29:00 -0000 Cc: Tobias Burnus , GCC Patches , fortran@gcc.gnu.org Content-Transfer-Encoding: quoted-printable Message-Id: <6C5A80FF-4B39-449A-B015-00D537483F08@adacore.com> References: <20120320094857.GB27039@physik.fu-berlin.de> <4F6AF98F.1000005@redhat.com> <1CF02DE4-A03A-4435-BF26-5C21673B1DA5@adacore.com> To: Janne Blomqvist X-IsSubscribed: yes Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2012-03/txt/msg01711.txt.bz2 On Mar 27, 2012, at 10:38 AM, Janne Blomqvist wrote: > On Tue, Mar 27, 2012 at 11:01, Tristan Gingold wrot= e: >> Hi, >>=20 >> this patch fixes this issue. Is it OK ? >=20 > Ok. No check-gfortran regressions on x86_64-darwin, committed. >> Maybe we should include the AC_DEFINE action within GCC_CHECK_MATH_FUNC.= Will try to do that. >=20 > That looks like a cleaner solution, yes, and less chance for typos to sne= ak in. >=20 >> Sorry for not having noticed this issue before. >=20 > No problem. Thanks for fixing it quickly. You're welcome! Tristan.