Date: Fri, 18 Jul 2003 20:00:02 +0200 From: Michael Nottebrock <michaelnottebrock@gmx.net> To: "Jacques A. Vidrine" <nectar@FreeBSD.org> Cc: freebsd-current@FreeBSD.org Subject: Re: gcc-3.3 issues Message-ID: <200307182000.05215.michaelnottebrock@gmx.net> In-Reply-To: <20030718172335.GA70231@madman.celabo.org> References: <1058366903.81198.18.camel@skeeve> <200307181812.18604.michaelnottebrock@gmx.net> <20030718172335.GA70231@madman.celabo.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
On Friday 18 July 2003 19:23, Jacques A. Vidrine wrote:
> Even when libstdc++ is updated, we'll still be left with warnings from
> C-derived headers, such as the `long long' stuff.
Warnings are perfectly fine with me, since they don't break anything. Putting
bandaid around ports to avoid _errors_ in libstdc++ on the other hand doesn't
strike me as productive.
--
Michael Nottebrock \ KDE on FreeBSD \ ,ww
\ --- \ ,wWWCybaWW_)
\ http://freebsd.kde.org \ `WSheepW' free
\ II II node
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)
iD8DBQA/GDWlXhc68WspdLARAs/4AJ9HDKWTXnGh5tAHPVSDwSVTb+mUDgCfWlqP
hF62ANtXitZmPu7qYcQtRQ8=
=1Jtl
-----END PGP SIGNATURE-----
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200307182000.05215.michaelnottebrock>