Date: Fri, 18 Jul 2003 21:41:28 +0200 From: Michael Nottebrock <michaelnottebrock@gmx.net> To: Alexander Kabaev <ak03@gte.com> Cc: freebsd-current@freebsd.org Subject: Re: gcc-3.3 issues Message-ID: <200307182141.36299.michaelnottebrock@gmx.net> In-Reply-To: <20030718191649.GB84963@freefall.freebsd.org> References: <20030718191649.GB84963@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
On Friday 18 July 2003 21:16, Alexander Kabaev wrote:
> On Fri, Jul 18, 2003 at 07:07:55PM +0200, Michael Nottebrock wrote:
> Content-Description: signed data
>
> > On Friday 18 July 2003 18:14, Alexander Kabaev wrote:
> > > Configure ailing due to warnings is a real bug.
> >
> > What do you mean now? Configure is not failing because of warnings, it is
> > failing because of _ERRORS_, errors occur in gcc's libstdc++ bits. They
> > _used to be warnings_ before the import.
>
> Then configure runs gcc with wrong parameters. In GCC 3.3 -pedantic implies
> -pedantic-error, unless -fpermissive is specified too.
That's perfectly fine for configure to do, since it would work if gcc wouldn't
shoot its own foot by failing in libstdc++. What's the rationale of changing
around these commandline parameters anyway I'm asking myself. But that's
offtopic.
--
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/GE1wXhc68WspdLARAlUvAJ4q/UL37KF9vNsd7IxLD5Gneo596QCfceLm
YKTS08mEFdlQMTEwru3WxlY=
=yI0W
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200307182141.36299.michaelnottebrock>