Date: Tue, 22 Oct 2002 13:35:20 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Kris Kennaway <kris@obsecurity.org> Cc: Ruslan Ermilov <ru@FreeBSD.org>, current@FreeBSD.org, standards@FreeBSD.org Subject: Re: libstdc++ does not contain fabsl symbol Message-ID: <3DB5B688.C3E5520B@mindspring.com> References: <20021020025400.GA13776@xor.obsecurity.org> <20021022082241.GG3325@sunbay.com> <20021022184605.GA85779@xor.obsecurity.org> <3DB5A9B6.1C2D1684@mindspring.com> <20021022202047.GA88314@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DB5B688.C3E5520B>