X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=B+f3QCrlwST8YddPemhV9aU+eT6UAWhWwvJiCEC9ZVI=;
        b=pNiN6gaUTBqfvcY1Q8SsYcqhCpjrCGa5GOb9GNXrmaQ88zwGJiYDXt6n6jOYP0AsgI
         vRY8I2ZDwNEBrjrVVZQD/fKNiQJ/ULbqfv46vYDPo0tIcCwXzM/gwyZgOiuSVZG/fGZ+
         1PcNKdlKVS9IvPvG6WkWkM7hQ5Gex0OJbP7ZY=
MIME-Version: 1.0
Date: Tue, 26 Jul 2011 01:02:17 +0300
Message-ID: <CAA2C=vAhTVc9f3coSdkT_r_fpXo0miZjCCQ1w+Bo6Gmv+t3Upg@mail.gmail.com>
Subject: DJGPP_MINOR no longer defined?
From: Ozkan Sezer <sezeroz AT gmail DOT com>
To: djgpp AT delorie DOT com
Content-Type: text/plain; charset=ISO-8859-1
Reply-To: djgpp AT delorie DOT com

I use __DJGPP_MINOR__ to understand whether I have djgpp>=2.04 or not.
In more recent versions of gcc, specifically starting with gcc>=4.3.0,
DJGPP_MINOR is no longer defined and djgpp.ver is no longer generated.
Is there a specific reason?  (If this is a well known thing, sorry.)

(As a side note, the *s2.zip patch files are no longer provided either,
which is a big unvenience since we have to download 60+ mb of already
patch gcc sources...)

Regards.

--
O.S.