Date: Sun, 9 Jan 2005 17:59:57 +0100 From: Ulrich Spoerlein <q@uni.de> To: "Theodore R. Smith" <theodore@xmule.ws> Cc: lioux@FreeBSD.org Subject: Re: FreeBSD Port: xmule-1.9.4.b_1 Message-ID: <20050109165957.GD828@galgenberg.net> In-Reply-To: <41E15BCE.5070805@xmule.ws> References: <41E15BCE.5070805@xmule.ws>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 09.01.2005 at 10:29:02 -0600, Theodore R. Smith wrote: > Why is xMule 1.9.4b regarded as "broken" by freshports? Because it's "only" broken for 4.x releases of FreeBSD which shipped with gcc 2.95 (and will not be updated). > Judging the content at > http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.4.2005010401/xmule-1.9.4.b_1.log > > It appears as though xMule is being tested with an out-dated compiler, probably > gcc 2.95.x, which is no longer maintained by FSF. Yes, that's the build log for FreeBSD 4.11. This could probably be worked around by explicitely depending on a newer gcc port to be installed. aka USE_GCC= 3.3 > I'm not trying to tell you how to do your job(s)/volunteer work. I am imploring > you to penalize the proper deviants accordingly: the non-ISO-C++-compliant > compiler that tests xMule. Relax, it's only broken for the older 4.x line of FreeBSD and it can probably be fixed very easily by the maintainer. Ulrich Spoerlein -- PGP Key ID: F0DB9F44 Encrypted mail welcome! Fingerprint: F1CE D062 0CA9 ADE3 349B 2FE8 980A C6B5 F0DB 9F44 Ok, which part of "Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn." didn't you understand?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050109165957.GD828>