This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/61485] "Please use exactly Autoconf 2.64 instead of 2.69" due to hardcoded autoconf/autom4te
- From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 12 Jun 2014 14:12:58 +0000
- Subject: [Bug other/61485] "Please use exactly Autoconf 2.64 instead of 2.69" due to hardcoded autoconf/autom4te
- Auto-submitted: auto-generated
- References: <bug-61485-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61485
--- Comment #3 from Vincent LefÃvre <vincent-gcc at vinc17 dot net> ---
(In reply to Richard Biener from comment #1)
> Why would you do autoreconf?
With most projects, this is needed with svn working copies, otherwise some
files may become obsolete and one gets weird errors.
> The supported way of doing this is to put the exact versions in your PATH.
This would mean using a specific PATH to build GCC, which is bad.