Re: /usr/local [was: CPPFLAGS prob]

[Murray Cumming]

On Mon, 2004-06-14 at 08:31 -0700, Dan Kegel wrote:
> Russell Shaw wrote:
> > Hal Snyder wrote:
> > 
> >> Ralf Corsepius <address@hidden> writes:
> >>
> >>> BTW: Having to pass "/usr/local" almost always indicates a massively
> >>> mis-configured toolchain or configure script.
> >>
> >>
> >> Sorry if this is an F.A.Q. I see various ways of doing it but wonder,
> >> what is best practice?
> >>
> >> What are the recommended automake and autoconf mechanisms for setting
> >> appropriate search paths to supporting libs and headers that are
> >> themselves add-ons and not part of the OS release? It is not always
> >> /usr/local/lib and /usr/local/include, of course. On NetBSD it's
> >> /usr/pkg instead of /usr/local. On Solaris it can be /opt/sfw. Etc.
> > 
> > 
> > On gtk, pkg-config is used to give all the library paths and flags
> > for various packages.
> 
> I think one needs a separate copy of pkg-config for each toolchain
> you want to build things with.  (Or at least its data files.)

No, that makes no sense.

-- 
Murray Cumming
address@hidden
www.murrayc.com