From owner-freebsd-standards Tue Oct 22 13:36:36 2002 Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D67F37B401; Tue, 22 Oct 2002 13:36:35 -0700 (PDT) Received: from flamingo.mail.pas.earthlink.net (flamingo.mail.pas.earthlink.net [207.217.120.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D62643E4A; Tue, 22 Oct 2002 13:36:34 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0482.cvx21-bradley.dialup.earthlink.net ([209.179.193.227] helo=mindspring.com) by flamingo.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 1845lQ-000597-00; Tue, 22 Oct 2002 13:36:32 -0700 Message-ID: <3DB5B688.C3E5520B@mindspring.com> Date: Tue, 22 Oct 2002 13:35:20 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: Ruslan Ermilov , current@FreeBSD.org, standards@FreeBSD.org Subject: Re: libstdc++ does not contain fabsl symbol References: <20021020025400.GA13776@xor.obsecurity.org> <20021022082241.GG3325@sunbay.com> <20021022184605.GA85779@xor.obsecurity.org> <3DB5A9B6.1C2D1684@mindspring.com> <20021022202047.GA88314@xor.obsecurity.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-standards@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kris Kennaway wrote: > Yes, because as it stands this function is supplied by gcc as a > built-in function, and the source tree will not compile without it > (e.g. with a non-gcc compiler). > > > Alternately, the use could avoid adding the "-fno-builtin", and > > the problem would go away. > > -fno-builtin tells gcc to stop using its own builtin functions and use > the FreeBSD version instead. We don't built with it by default, but > we probably should. It's a good idea. See other posting though... I think the problem is that sources are being converted to assume C99 compliance, when FreeBSD is, in fact, not compliant. It would be better if this were a compliance complaint, rather than a "-fno-builtin"; it would be best to tackle all these issues at once, rather than one at a time over a very long time. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message