I'm having a little problem with compiling programs. It seems that gcc does not search /usr/local/include for headers by default; I have to specify -I/usr/local/include. It seems to me that it should. So: Should gcc be searching /usr/local/include by default? If yes: where do I look to try to fix this problem? I'm not sure why I'm thinking it should; I seem to remember it doing so before. But maybe I'm imagining things. Thanks! - Michael
On Mon, Jan 30, 2006 at 07:56:55PM -0600, Michael Ekstrand wrote:> I'm having a little problem with compiling programs. > > It seems that gcc does not search /usr/local/include for headers by > default; I have to specify -I/usr/local/include. It seems to me that it > should. > > So: > > Should gcc be searching /usr/local/include by default?No, if you want to look for third-party headers you need to point the compiler there yourself. Kris -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20060130/0d533a38/attachment.bin
What is the main difference between them, in brief? I only use /usr/include and I've never used /usr/local/include. thanks, pongthep> On Mon, Jan 30, 2006 at 07:56:55PM -0600, Michael Ekstrand wrote: > > I'm having a little problem with compiling programs. > > > > It seems that gcc does not search /usr/local/include for headers by > > default; I have to specify -I/usr/local/include. It seems to me that it > > should. > > > > So: > > > > Should gcc be searching /usr/local/include by default? > > No, if you want to look for third-party headers you need to point the > compiler there yourself. > > Kris