Re: The Dreaded "Missing Subunits"

[Mark Johnson <mark_h_johnson@raytheon.com>]

Peter Richtmyer wrote:
> 
> I love the Gnat compiler but...
> 
>    I dread this error message:
> 
>    "No code generated for file xxxx.2.ada (missing subunits)"
> 
> It means that I have a procedure or function declared "...is separate;"
> in package xxxx, but there is no matching separate.
Do you mean the separate doesn't exist or that it does not have the
"right filename"? I will assume the latter.

> A "legacy" package
> has a gazillion separates. They need changes, and the calling
> parameters get changed and don't match, or the routine name changes,
> or the separate filename isn't right, or whatever happens to get this
> message, and it is a real pain to figure out which "subunit" is missing.
> 
I doubt these are causes of the error message.

> Anybody have a solution? maybe a compile switch or ...?
> 
What we use for code we ported from a rational system is...

  pragma Source_File_Name (Spec_File_Name => "*.1.ada");
  pragma Source_File_Name (Body_File_Name => "*.2.ada");

These configuration pragmas should be in a file named gnat.adc (along
with any other pragmas you may want to apply to every compilation). This
is documented in both the GNAT User's Guide and Reference Manuals. In
the User's Guide, look for sections titled "Configuration Pragmas",
"Using Other File Names", and "Alternative File Naming Schemes". In the
Reference Manual, look for the "Implementation Defined Pragmas" section
and search for Source_File_Name.

If you have an old version of GNAT that doesn't allow star names in this
pragma - I suggest you get a newer version.

If you have a large system with lots of directories, I can make some
suggestions on organizing the build so it may work a little easier as
well (and leverage data from the Apex configuration files that you may
have).

I suggest you take the time to read the user's guide and reference
manual in their entirety. You will learn a lot about the GNAT product by
doing so.

  --Mark