Subject: Re: pkg-src build problems.
To: None <tech-toolchain@netbsd.org>
From: Simon Burge <simonb@supp.cpr.itg.telstra.com.au>
List: netbsd-help
Date: 12/11/1998 09:55:50
------- Blind-Carbon-Copy

From: Simon Burge <simonb@telstra.com.au>
To: tech-toolchain@netbsd.org
Subject: Re: pkg-src build problems. 
In-Reply-To: <367042C3.5B2BCC61@largesalad.co.uk> 
Date: Fri, 11 Dec 1998 09:55:50 +1100

[[ Moved to tech-toolchain and Bcc'd to netbsd-help ]]

On Thu, 10 Dec 1998 21:53:08 +0000  Dave Millen wrote:

> Matt Knopp wrote:
> 
> > So, I assume that the packages in pkgsrc have all compiled for
> > someone, and so I figure I am missing something obvious. Anything
> > I try to build that uses the png/jpep/tiff libs often never finds
> > the include files. I've confired that all of the .h files configure
> > looks for are in /usr/pkg/include, and the matching lib files are
> > in /usr/pkg/lib as they should be.
> >
> > 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.

Just an idea (that will probably get shot down in flames)...

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}.

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...

Simon.

------- End of Blind-Carbon-Copy