This is the mail archive of the gcc@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]
Other format: [Raw text]

Should gcc use maintainer-mode?


binutils use maintainer-mode and warns about version requirements for
automake, autoconf, libtool and gettext. gcc doesn't use maintainer-
mode. As the result, I got

# cd gcc
# cvs update -dP
...
M fastjar/Makefile.in
M fastjar/configure
cvs server: Updating gcc
P gcc/ChangeLog
P gcc/Makefile.in
P gcc/alias.c
P gcc/config.gcc
M gcc/configure
...

although I didn't change any of those files and I don't even know if
the versions of those tools on my machine are compatible. But automake
and autoconf were run anyway. Even if my tools are ok, when I check out
from CVS in the future, I may get conflicts if those files are changed
in CVS and generated by different vesions of those tools. Why doesn't
gcc use maintainer-mode?


H.J.


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