From owner-freebsd-questions@FreeBSD.ORG Mon May 5 18:40:53 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A382106566C for ; Mon, 5 May 2008 18:40:53 +0000 (UTC) (envelope-from walt@wump.org) Received: from mta11.charter.net (mta11.charter.net [216.33.127.80]) by mx1.freebsd.org (Postfix) with ESMTP id B68928FC17 for ; Mon, 5 May 2008 18:40:52 +0000 (UTC) (envelope-from walt@wump.org) Received: from aarprv06.charter.net ([10.20.200.76]) by mta11.charter.net (InterMail vM.7.08.03.00 201-2186-126-20070710) with ESMTP id <20080505184042.GVYA5653.mta11.charter.net@aarprv06.charter.net>; Mon, 5 May 2008 14:40:42 -0400 Received: from [10.0.0.10] (really [68.116.98.9]) by aarprv06.charter.net with ESMTP id <20080505184041.RLVA3194.aarprv06.charter.net@[10.0.0.10]>; Mon, 5 May 2008 14:40:41 -0400 Mime-Version: 1.0 Message-Id: In-Reply-To: <200805051206.52546.fbsd.questions@rachie.is-a-geek.net> References: <200805051206.52546.fbsd.questions@rachie.is-a-geek.net> Date: Mon, 5 May 2008 11:42:23 -0700 To: freebsd-questions@freebsd.org From: Walt Pawley Content-Type: text/plain; charset="us-ascii" X-Chzlrs: 0 Cc: Mel Subject: Re: What is CPP's real default include path? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 May 2008 18:40:53 -0000 At 12:06 PM +0200 5/5/08, Mel wrote: >On Monday 05 May 2008 10:12:05 Walt Pawley wrote: >> I've been fiddling with compiling nzbget-0.4.0 on a 6.3 system. >> My initial efforts failed the configuration process for not >> finding iconv.h. This, despite /usr/local/include/iconv.h being >> present and supposedly in the include search path if the info >> documentation can be believed. >> >> Just to see if I could learn something, I copied the >> /usr/local/include/iconv.h to /usr/include/ and tried again. >> After this, the configuration process completed and the >> application seemed to "make" and "make install" just fine. >> >> Is there some way to ascertain what the set of default include >> paths actually is? > >Even though cc has a million options, there's none that I know that prints the >system include path (not even in -dumpspecs). However, in practice you can >assume it's /usr/include. > >To make configure scripts believe you have something installed, it's not a >good idea to copy headers. >Look for a --with-iconv=/usr/local option and failing that, change CFLAGS and >LDFLAGS in the environment when configuring. Admonition understood - I was just experimenting and wanted the file to be in a specific place without any uncertainty about just what various "look over there" options actually do. The reason for such a mind set is that actual behavior of cpp seems to differ from its documentation, to wit: info cpp :: Header Files::Search Path reads: GCC looks in several different places for headers. On a normal Unix system, if you do not instruct it otherwise, it will look for headers requested with `#include ' in: /usr/local/include LIBDIR/gcc/TARGET/VERSION/include /usr/TARGET/include /usr/include I'm either missing something very fundamental (which I doubt not at all) or this should be a somewhat serious problem. There are 4944 header files in /usr/local/include/ branch on this system that should be accessible by default but, if my experience with nzbget is any guide, do not seem to be. -- Walter M. Pawley Wump Research & Company 676 River Bend Road, Roseburg, OR 97470 541-672-8975