This is the mail archive of the gcc-bugs@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]

[Bug fortran/45827] mio_component_ref(): Component not found when mixing f90 and f03 in large projects


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45827

--- Comment #22 from Hans-Werner Boschmann <boschmann at tp1 dot physik.uni-siegen.de> 2010-10-24 10:17:00 UTC ---
Yes, I still get the error with later revisions. I am using an amd64 machine
with open SuSE 11.2. Here are some updates of my statements:

* All means like renaming files or using -std=f2003 coincidentally fixed the
problem for a specific revision and a specific peace of code. This is no
general fix.

* I also got the error with 4.6.0-20100928 when I changed some lines of code.

* Putting all use statements in "proper order" fixes the problem for all
revisions, including 4.6.0-20100921. I noticed later, that I forgot to sort the
intrinsic module iso_fortran_env in the example. It is mentioned before kinds
in arguments_module and after kinds in common_module.

* Not putting use statements into "proper order" doesn't mean that the error
shows up, it randomly appears sometimes while you edit the code.

So I have to update use statements in all modules, when I change dependencies
in a fundamental module. That's really annoying, but it is a workaround for all
revisions so far. Still, this is not what I take to mean "works for me".


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