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]

gcc gcc-3_3-branch has configure.in newer than configure


In the gcc 3.3 branch, several people have committed changes to
the top-level configure.in without regenerating the top-level configure.

  [mgnu at berman gcc]$ ls -l configure configure.in
  -rwxr-xr-x    1 mgnu     mgnu        49628 Sep 29 12:11 configure
  -rw-r--r--    1 mgnu     mgnu        52656 Nov 28 15:27 configure.in

Is this normal?  It seems strange to me.

In particular, 'configure.in' has code to set gxx_include_dir,
but 'configure' has not been regenerated to use that code.

I believe this is the heart of pr gcc/10018, which is why I care.

Michael C


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