[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
/usr/local [was: CPPFLAGS prob]
From: |
Hal Snyder |
Subject: |
/usr/local [was: CPPFLAGS prob] |
Date: |
Mon, 14 Jun 2004 09:53:14 -0500 |
User-agent: |
Gnus/5.090017 (Oort Gnus v0.17) Emacs/21.2 (berkeley-unix) |
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.
- CPPFLAGS prob, Patrick Welche, 2004/06/04
- Re: CPPFLAGS prob, Ralf Corsepius, 2004/06/04
- Re: CPPFLAGS prob, Patrick Welche, 2004/06/04
- /usr/local [was: CPPFLAGS prob],
Hal Snyder <=
- Re: /usr/local [was: CPPFLAGS prob], Russell Shaw, 2004/06/14
- Re: /usr/local [was: CPPFLAGS prob], Dan Kegel, 2004/06/14
- Re: /usr/local [was: CPPFLAGS prob], Russell Shaw, 2004/06/14
- Re: /usr/local [was: CPPFLAGS prob], Murray Cumming, 2004/06/17
- Re: /usr/local [was: CPPFLAGS prob], Dan Kegel, 2004/06/17
- Re: /usr/local [was: CPPFLAGS prob], Russell Shaw, 2004/06/17
- Re: /usr/local [was: CPPFLAGS prob], Dan Kegel, 2004/06/17
- Re: /usr/local [was: CPPFLAGS prob], Paul Jarc, 2004/06/17
- Re: /usr/local [was: CPPFLAGS prob], Paul Jarc, 2004/06/17
- Re: /usr/local [was: CPPFLAGS prob], Dan Kegel, 2004/06/17