On Fri, 11 Dec 1998, Simon Burge wrote:

: > > Is there some magical enviroment var I need to set to /usr/pkg/include?
: > 
: > I found this with one or two packages and just put symlinks in /usr/lib and
: > /usr/include to point at the actual locations. This allowed the compiles to
: > proceed.

It sounds like improperly configured pkgs - perhaps the original poster can
enlighten as to which pkgs failed in particular?  Everything I've tried has
worked for me.

: Is it worth changing the gcc/egcs specs so that /usr/pkg/include (and
: perhaps /usr/X11R6/include?) get searched for includes, and the relevent
: lib directories for libraries?  One obvious problem is if someone
: changes ${LOCALBASE}.

Heh.

No.

That's what -I is for, and there was a very, very long thread about why
NetBSD's compiler does not search /usr/local/include by default.  Now that
we have a pkgsrc system, the reasoning is twofold:  we don't want to pick up
stuff unintentionally in /usr/local to compile pkgs.

: I guess it's a question of high tightly integrated we want the package
: (and X11?) stuff.  One of the things I liked about the "old way" X
: used to work on some systems was how it had the includes installed in
: /usr/include/X11 and not some separate sub-directory...

I like the old way, too, but the new way has its merits (like bundling
everything in one place ;).

-- 
-- Todd Vierling (Personal tv@pobox.com; Bus. todd_vierling@xn.xerox.com)