This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: autoconf for type sizes


 > From: Alexandre Oliva <aoliva@redhat.com>
 > 
 > On Mar 13, 2001, "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu> wrote:
 > 
 > > Let me know when the snapshot is ready and I'll start testing with
 > > my private sources first.
 > 
 > That's the way to go.  We should not bump the AC_PREREQ of GCC, not
 > even in mainline, unless there's a pressing need to do so.  At least
 > not before autoconf 2.50 is released.
 > 
 > I'm pretty sure there will be a number of issues to resolve before we
 > can actually start using autoconf 2.50 (pre- or release) in GCC.  And
 > then, after we do, there's no reason to force everybody to have
 > autoconf 2.50 handy.

The "pressing need" is that we want to make use of the new features.
Otherwise there is no reason to upgrade and add the instability
inherent in any new release.

Once we start using the new features, by definition we can't make it
work with 2.13.

The only time it should work with both versions is during the cutover
process.  It should be shown to work with both as a proof-of-concept
that the cutover has been done correctly.  But right after that we
should bump the prereq and start using the new features.

Now regarding waiting until 2.50 is released, I don't see a need for
that.  In the past we used a snapshot for a long time before 2.13 was
released.  (Well we had no choice since there was no maintainer at the
time.)  But since only developers regen configure, and we've done it
before, I don't understand why we can't do it again (use a snapshot
that is.)

		--Kaveh
--
Kaveh R. Ghazi			Engagement Manager / Project Services
ghazi@caip.rutgers.edu		Qwest Internet Solutions


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]