X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f X-Recipient: djgpp-workers AT delorie DOT com Message-ID: <513823DD.1010706@iki.fi> Date: Thu, 07 Mar 2013 07:21:33 +0200 From: Andris Pavenis User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130219 Thunderbird/17.0.3 MIME-Version: 1.0 To: djgpp-workers AT delorie DOT com Subject: Re: gcc-4.8.0 20130202 References: <510E36AE DOT 6060102 AT iki DOT fi> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: djgpp-workers AT delorie DOT com On 03/07/2013 01:29 AM, Rugxulo wrote: > Hi, > > On Tue, Mar 5, 2013 at 4:29 AM, Rugxulo wrote: >> >> On Sun, Feb 3, 2013 at 4:06 AM, Andris Pavenis wrote: >>> >>> Packages of gcc-4.8 20130202 snapshot for DJGPP are >>> available for testing purposes at >>> >>> http://ap1.pp.fi/djgpp/gcc/test/4.8.0-20130202/ >> >> They finally seemed to have gotten rid of all the P1 bugs, so this may >> be finally gearing up for final release soon. Just FYI. > > http://gcc.gnu.org/ml/gcc/2013-03/msg00036.html > > " > We've reached the goal of zero P1 regressions again, and have less > than 100 P1-P3 bugs, but the number of changes going daily is still too > high. If no new P1 appears within a week, I'd like to create first > release candidate in the middle of next week .... > " > I know as I'm getting GCC mailing list contents in e-mail. I guess there should be no problems with build for DJGPP v2.04 current CVS version (simply updating my GIT repo from upstream and after that my own branches, running script to get cross-compiler SRPM, build cross-compiler from that and get gcc480s.zip as side product, build for DJGPP v2.04. Longest time of that takes native build for DJGPP) There will most likely no build for DJGPP v2.03. It is just too old. Andris