X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Received:	by 10.66.146.227 with SMTP id tf3mr16933628pab.21.1440867625080;
	Sat, 29 Aug 2015 10:00:25 -0700 (PDT)
X-Received:	by 10.182.60.168 with SMTP id i8mr55562obr.37.1440867625041; Sat,
	29 Aug 2015 10:00:25 -0700 (PDT)
Newsgroups:	comp.os.msdos.djgpp
Date:	Sat, 29 Aug 2015 10:00:24 -0700 (PDT)
In-Reply-To:	<55E1DCBA.4010103@iki.fi>
Complaints-To:	groups-abuse AT google DOT com
Injection-Info:	glegroupsg2000goo.googlegroups.com; posting-host=134.3.144.13; posting-account=OsAajgoAAADdKJnkJkmhzqP0jo6I_P_0
NNTP-Posting-Host:	134.3.144.13
References:	<201506091634 DOT t59GY0Bk000493 AT delorie DOT com> <55E17D7D DOT 4030406 AT gmx DOT de>
	<55E1891C DOT 1070303 AT iki DOT fi> <a136ae5a-33ba-434b-9f69-290e6638eeb7 AT googlegroups DOT com>
	<55E1DCBA DOT 4010103 AT iki DOT fi>
User-Agent:	G2/1.0
MIME-Version:	1.0
Message-ID:	<55c03acb-475b-4dc9-b4e3-0986e6e24ce9@googlegroups.com>
Subject:	Re: ANNOUNCE: DJGPP 2.05 release candidate
From:	"Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
Injection-Date:	Sat, 29 Aug 2015 17:00:25 +0000
Bytes:	3139
Lines:	47
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

Am Samstag, 29. August 2015 18:24:43 UTC+2 schrieb Andris Pavenis (andris DOT pavenis AT iki DOT fi) [via djgpp AT delorie DOT com]:
> On 08/29/2015 03:46 PM, Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de) [via djgpp AT delorie DOT com] wrote:
> > Am Samstag, 29. August 2015 12:27:59 UTC+2 schrieb Andris Pavenis (andris DOT pavenis AT iki DOT fi) [via djgpp AT delorie DOT com]:
> >> On 08/29/2015 12:38 PM, Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de) [via djgpp AT delorie DOT com] wrote:
> > [snip]
> >> About GCC versions:
> >> - 3.4.6, 4.7.4, 4.8.5, 4.9.3 and 5.2.0 should be in new current directory (that includes also
> >> gpc-3.4.6)
> >> All gcc builds older than from this year can go to ftp/deleted/...
> >>
> >> GMP, MPFR and MPC - perhaps only newest version should be kept
> >>
> >> I should also sometimes build binutils-2.25 RPMs for /pub/ftp/rpms
> >>
> >> Andris
> >
> > OFYI, this is the list of compilers that the script would hace copied to /current:
> > gcc323, gcc336, gcc346
> > gcc401, gcc412, gcc423, gcc432, gcc444, gcc453, gcc464, gcc474, gcc485, gcc493
> > gcc510, gcc520
> >
> > gpc323, gpc346
> >
> > Of course, gcc means all (ada*, gfor*, etc).  If all these versions are still
> > required needs to be decide by someone else.
> >
> >
> gcc-3.2.3, gcc-3.3.6 - do not copy
> gpc-3.2.3 - do not copy
> 
> gcc-3.4.6 - copy
> gpc-3.4.6 - copy
> 
> gcc-4.X.Y where X < 7 - do not copyopy
> 
> gcc-4.7.4, gcc-4.8.5, gcc-4.9.3 - to new current
> 
> gcc-5.2.0 - to new current
> 
> gcc-5.1.0 - no one has complained about regressions against it for gcc-5.2.0. . And it is not 
> removed irrecoverably, so let's leave it out
> 
> Andris

Do you remeber what binutils are required for those compiler versions.  Currently the script would "delete" all binutils except the last port, hopping that it is good for all compilers.

Regards,
Juan M. Guerrero

- Raw text -