This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug ada/14350] New: libada/configure.in should not hardcode GCC version
- From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 29 Feb 2004 21:37:18 -0000
- Subject: [Bug ada/14350] New: libada/configure.in should not hardcode GCC version
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
libada/configure.in says:
# Please keep the version number in sync with the general GCC version.
AC_INIT([GCC libada],[experimental pre-3.5])
This additional place with a version number hardcoded is a regression from
3.4. We've carefully reduced the number of such places to just two,
gcc/version.c and gcc/doc/include/gcc-common.texi, which are documented in
branching.html and releasing.html. This additional place - not documented
in the place RMs will look - is an unwanted addition. No version number at
all should be hardcoded here that appears anywhere else.
(The GCC version number is of course an entirely separate matter from the
*library* ABI version numbers, which need to be maintained independently
when the ABI changes. But ada/Makefile.in takes care to extract the library
version number from gnatvsn.ads rather than duplicating it; this file should
not duplicate the library version number either, which should remain kept
in exactly one place.)
--
Summary: libada/configure.in should not hardcode GCC version
Product: gcc
Version: 3.5.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ada
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jsm28 at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14350