Version numbers question

2015-06-22 Thread JohnT
I am wondering why it appears that GCC has started drastically raising its
major version number for minor changes, instead of spending several years
on version 3 and 4. 4.0.1, 4.1.1 and 4.12, 4.2.3, 4.3.2, 4.4.5, up through
4.7.0, 4.7.1, 4.7.2, the 4.8 and 4.9 releases, then version 5.1 and
talking about version 6. Little changes should be reflected in minor
version and bugfix numbers, not major version jumps.

John Tellefson
Kansas, where Brownback talks and the wind blows

USA



Re: Version numbers question

2015-06-22 Thread JohnT
Thanks, Andrew, a reasonable reason. Time flies and GCC or its predecessor
has been around for about 25 years. In another 25, hopefully GCC will
still be a leading compiler and the larger numbers won't seem awkward.

Regarding what's a small vs large change, I'd say that building with C++
and newly generated C++ library was worthy of a major version bump, but
that's just my amateur opinion.

John

pins...@gmail.com wrote:
>
>
>
>> On Jun 22, 2015, at 6:55 AM, JohnT  wrote:
>>
>> I am wondering why it appears that GCC has started drastically raising its
>> major version number for minor changes, instead of spending several years
>> on version 3 and 4. 4.0.1, 4.1.1 and 4.12, 4.2.3, 4.3.2, 4.4.5, up through
>> 4.7.0, 4.7.1, 4.7.2, the 4.8 and 4.9 releases, then version 5.1 and
>> talking about version 6. Little changes should be reflected in minor
>> version and bugfix numbers, not major version jumps.
> The simple answer is there is no justification to ever bump the major version 
> any time soon so why not make the major version the one which gets bumped 
> each year. So 5 is the version which is released this year, 6 next year, etc. 
> this is no different from 4.9 last year and 4.8 the year before really. Just 
> it was decided 4.10 does not make sense and is partly confusing to some 
> users; does it come before or after 4.2. Anyways the decision was done to get 
> rid of that confusion and also to avoid having to make a justification of 
> when to bump the major version number. 
>



Please update GNU GCC mirror list

2009-12-16 Thread JohnT
 Some of the sites listed on the mirror list 
http://gcc.gnu.org/mirrors.html aren't up to date and some aren't 
accessible. LaffeyComputer.com doesn't allow access, and used to require 
a password for access. This isn't the way a GNU mirror site ought to 
operate. There should be free public access.


John Tellefson
Salina, KS USA

--
http://www.mozilla.org  Firefox browser, Thunderbird email, Seamonkey 
all-in-one, Sunbird calendar and more. Free open-source software for Windows, 
Linux, Mac OS and other systems



build results for 4.6.3

2012-05-29 Thread JohnT


i686-pc-linux-gnu
Using built-in specs.
COLLECT_GCC=/usr/bin/gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/i686-pc-linux-gnu/4.6.3/lto-wrapper
Target: i686-pc-linux-gnu
Configured with: /usr/local/gcc-4.6.3/configure --prefix=/usr 
--enable-languages=c,c++,ada,fortran,java,lto,objc

Thread model: posix
gcc version 4.6.3 (GCC)
Mandriva 2010.0
Linux localhost 2.6.31.14-desktop-1mnb #1 SMP Wed Nov 24 11:24:43 EST 2010 
i686 AMD Athlon(tm) XP 1900+ GNU/Linux

glibc-2.10.1-6.7mnb2
512 Mb
binutils 2.21.1
ppl-0.12.1
cloog-ppl-0.15.11

Workaround for building this java with an older java (gcj-4.4.1) already 
installed and a bug in gjar that causes a nullpointer exception: remove 
the old java before building, so the build system uses the just-compiled 
gjar to finish the build.


Submitted by John Tellefson

--
http://www.mozilla.org Firefox browser, Thunderbird email, Seamonkey 
all-in-one, Sunbird calendar and more. Free secure open-source software 
for Windows, Linux, Mac OS and other operating systems