Date: 17 Jul 2003 22:07:37 +0200 From: Peter Kadau <peter.kadau@tuebingen.mpg.de> To: Michael Nottebrock <michaelnottebrock@gmx.net> Cc: freebsd-current@freebsd.org Subject: Re: gcc-3.3 issues Message-ID: <1058472457.12586.30.camel@straycat> In-Reply-To: <200307162209.22237.michaelnottebrock@gmx.net> References: <1058366903.81198.18.camel@skeeve> <20030716110743.1e44c8e0.ak03@gte.com> <200307162209.22237.michaelnottebrock@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi ! > > s/gcc-3.3/ports/ issues and we are in agreement. alright, `port compile issues raised with the adoption of gcc-3.3' > > Patches to fix broken ports are welcome. Looking at AbiWord2 I suspect this has to be pushed upstream in some cases. OK, here is a - ahem - patch for aspell: --- prog/checker_string.hpp.orig Tue Sep 24 03:34:52 2002 +++ prog/checker_string.hpp Thu Jul 17 20:02:58 2003 @@ -5,6 +5,7 @@ // it at http://www.gnu.org/. #include <stdio.h> +#include <g++/cassert> #include "aspell.h" It works on my colleague's and my current and my stable. But maybe it's not the right way (tm) (to 'do-it) :-) But should I post that on -ports, -current or send it to the ports maintainer ? I'd rather avoid tracking -ports... > Is something like this expected, i.e., certain combinations of -W* and > -pedantic to produce errors when they didn't before? Yes, though -ansi and -pedantic are not that troublesome I think. A real killer is -Werror. But -W* is not the only source of compile errors - see above. Cheers Peter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1058472457.12586.30.camel>