🚀 go-pugleaf

(Sorry the subject line isn't too helpful)

On sVr4 systems, I've found that it's not desirable to use the
BSD-compatibility library where it can be avoided, because it can be pretty
buggy.  I see from comments in the gcc documentation that I'm not alone in
this conclusion.  But sometimes there are a few isolated routines that it
makes sense to use.  And when this is done, usually the include files
(/usr/ucbinclude) are needed as well.

So here's the problem:

If I just say ``gcc -I/usr/ucbinclude'', I get the UCB include files
in preference to the regular ones.  So it's usually necessary to
force /usr/include to be looked in first, by doing ``gcc -I/usr/include
-I /usr/ucbinclude''.

With gcc2, however, this doesn't pick up the gcc includes files first,
so we have to add them to the soup as well.  But the naming scheme
for gcc2 includes a lot of specific information which I've got
no interest in including in my Makefiles.  For example, on this
machine, I'd have to do:

    -I/usr/local/lib/gcc-lib/m68k-atari-asv/2.2.2/include

Really, I don't want any of that information in the makefile.
So how can I make sure that include files are searched as
follows:

    gcc-include-dir iff using gcc
    /usr/include
    /usr/ucbinclude

In a mannner that's portable between different sVr4 machines,
and allows for using gcc or not, and doesn't require changing
the makefile for each machine and for each new gcc version.
What am I missing?

-- 
Mats Wichmann
Systems Software Consultant
alruna!mats@ossi.com (or mats@netcom.com)