This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug other/15548] [3.5 Regression] libgfortran in wrong CVS module, breaks build
- From: "wilson at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 18 Aug 2004 03:52:35 -0000
- Subject: [Bug other/15548] [3.5 Regression] libgfortran in wrong CVS module, breaks build
- References: <20040520000700.15548.green@redhat.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From wilson at gcc dot gnu dot org 2004-08-18 03:52 -------
Proposed patch at
http://gcc.gnu.org/ml/gcc-patches/2004-08/msg01301.html
The reason we have a problem here is because of an undocumented feature of cvs.
It uses strncmp (test_dir, ignore_dir, strlen (ignore_dir)), thus putting
!gcc/f in the gcc-core module means that we also lose gcc/fortran even though it
wasn't listed. Maybe they meant to use strlen()+1? Maybe I should report this
as a bug? Anyways, this isn't a serious problem after adding the fortran
support, as we wanted to lose gcc/fortran anyways.
However, I just realized that we are probably also losing gcc/fixinc, and I
forgot to check for that. You probably wouldn't notice if you were on a linux
machine. This could be fixed by explicitly adding this dir after the !gcc/f.
Checking...yes I see it is lost from the gcc-core module. Oh well.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15548