Re: Extremely long build times

There is another thing we forgot to mention that could prove to be relevant. There are times when the compilation is aborted after a few minutes with a strange error message: 'Program or unit x recursively uses itself'. This can happen on many different units, perhaps once every 20 builds or so. We simply rebuild and the compiler does not complain again. A search with Google didn't produce anything definite on that matter.

Regards,
Nikos & Stavros
.

Relevant Pages

  • Re: gfortran, g95, and dual-core
    ... either speed of compilation or speed of execution? ... Many, many things matter. ... That's why cache is ... Is this apt to make a big difference (factor of 2 in execution speed) when comparing different Intel-compatible chips in a given price range? ...
    (comp.lang.fortran)
  • Re: Strange behaviour with constants, when multiple projects on the same code
    ... should differ only in target device and Conditional Compilation Constants.I ... have defined WINCE constant in WinCE project and PPC constant in PPC ... The problem is that no matter which project I try to build, ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Standard C and math library
    ... since the magic words used for compilation and linking are external to the standard, ... In addition, unlike today where it's mostly embedded systems where memory footprint matters at that level of granularity, it once *did* matter -- particularly at the time the convention was adopted. ... I know history in this case:) Anyway the standard C99 is far too young to be affected by math coprocessors and DX/SX distinction. ...
    (comp.lang.c)
  • Re: What is the benefit of USE, ONLY(!)
    ... order to speed up compilation in early implementations of DVF. ... my position on this is one of accepting that multiple style choices are ... reasonable on this matter. ... and they don't convince me). ...
    (comp.lang.fortran)
  • Re: RH7.2 Troubles Installing BroadCom BCM5700 NetXtreme on HP D530
    ... if it's only a matter of version ... because the error appears in compilation ... Otherwise, the hardware is detected: ...
    (linux.redhat)