Date: Mon, 24 Jan 2000 20:50:21 +0100 From: Alexander Langer <alex@big.endian.de> To: "David O'Brien" <obrien@FreeBSD.ORG> Cc: ports@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0-release (ports) schedule Message-ID: <20000124205021.B24975@cichlids.cichlids.com> In-Reply-To: <20000124103710.B75151@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Mon, Jan 24, 2000 at 10:37:10AM -0800 References: <200001241436.GAA23651@silvia.hip.berkeley.edu> <20000124103710.B75151@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake David O'Brien (obrien@FreeBSD.ORG): > I would be happy to look review fixes or consult the maintainers. Hello David, compiler-maintainer ;-) I noticed that many ports are broken because the compiler handles ANSI-C++ violations too strict. That means, if you do, as an example: const fubar = 10; the build _FAILS_. Other compilers implicy type "int" here, that's why many ports are broken for -current only. Just FYI, maybe you can do something against this strict handling. Or not, I don't know. Somehow, it's very good that the compiler does this... Alex -- I doubt, therefore I might be. 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?20000124205021.B24975>