This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
How is aclocal.m4 in gcc maintained?
- From: "H. J. Lu" <hjl at lucon dot org>
- To: gcc at gcc dot gnu dot org
- Cc: green at redhat dot com
- Date: Tue, 2 Jul 2002 20:37:36 -0700
- Subject: How is aclocal.m4 in gcc maintained?
In libffi, I see
dnl aclocal.m4 generated automatically by aclocal 1.4
in aclocal.m4. But when I did
# mv aclocal.m4 aclocal.m4.saved
# cd ....../libffi
# make aclocal.m4
cd /home/hjl/work/gnu/src/tools-3.1/tools/libffi && aclocal
The generated aclocal.m4 is different from the saved aclocal.m4. There
is
2002-01-31 Anthony Green <green@redhat.com>
* configure: Rebuilt.
* configure.in: Replace CHECK_SIZEOF and endian tests with
cross-compiler friendly macros.
* aclocal.m4 (AC_COMPILE_CHECK_SIZEOF, AC_C_BIGENDIAN_CROSS): New
macros.
Why put AC_COMPILE_CHECK_SIZEOF and AC_C_BIGENDIAN_CROSS in a generated
file? There are 3 different copies of AC_COMPILE_CHECK_SIZEOF in the
gcc source tree. Why not just use one copy and fix all diretories,
including fastjar?
H.J.