On 4/04/2013 12:18 p.m., Alex Rousskov wrote:
On 04/03/2013 07:57 AM, Kinkie wrote:
Hi all,
Amos asked me to look into compiler-detection issues in autoconf
(e.g. http://bugs.squid-cache.org/show_bug.cgi?id=3674)
I'm working to improve compiler detection macros (see the bug for a
status update on that), but at the same time I'm wondering whether
it's a good idea to also deprecate older compilers such as gcc 2.X and
refuse to build (or at least require an explicit flag be passed from
the user) if we detect such an ancient compiler (I'd say any gcc 2
version).
I doubt Squid can be built using GCC2. If it actually helps you
accomplish something, I think it is OK to refuse GCC2. Otherwise, there
is probably no reason to add explicit restrictions.
HTH,
Alex.
I have not heard of anyone even trying to build it on GCC 2.x recently.
The FreeBSD which shipped with it were deprecated many years back so the
whole if-statement which triggered the bug report can probably be erased.
I've +1 the patch in the bug report as it will fix the bug as stated
with minimal change. Although if you wish to modify it slightly to drop
the GCC 1.x test entirely I'll also +1 that.
PS. The "official" line from me is that we require 4.x to build
Squid-3.1 and later. Squid-3.2 requires a recent 4.6+ version to build
reliably due to the increasing amount of C++11 support in use.
Amos
