change behavior of elfos.h slightly

[Chris G. Demetriou]

law@cygnus.com (Jeffrey A Law) writes:
> [ ... discussion about how to override standard definitions with
>   system-specific ones. ... ]
> The style that we're trying to wean ports from is having one .h file
> include some other .h file by instead listing them explicitly in the
> desired order in configure.in.
> [ ... ]

So, do I understand correctly that the general desigre is to move from
the current mish-mash of includes in many architectures, to code like:


#include "generic_hdr.h"
#include "specific_overrides.h"

(where generic_hdr.h spells lots of things out unconditionally)

rather than:

#include "specific_parameters.h"
#include "generic_hdr.h"

(where generic_hdr.h is structured such that it can be parameterized
by definitions defined before it's included.


(Each seems compatible with the notion of including multiple headers
in a configure-generated tm.h, but the former seems to require much
more of a maintenance headache over time, and much more duplication of
code.  Just want to understand so that any changes that _I_ make don't
start to push things in the wrong direction.)



cgd