From owner-freebsd-questions@FreeBSD.ORG Mon May 5 10:06:55 2008 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91B7C1065671; Mon, 5 May 2008 10:06:55 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from snoogles.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 5FB088FC2C; Mon, 5 May 2008 10:06:55 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from localhost (localhost [127.0.0.1]) by snoogles.rachie.is-a-geek.net (Postfix) with ESMTP id 2EC5D1CC91; Mon, 5 May 2008 02:06:54 -0800 (AKDT) From: Mel To: freebsd-questions@freebsd.org Date: Mon, 5 May 2008 12:06:51 +0200 User-Agent: KMail/1.9.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805051206.52546.fbsd.questions@rachie.is-a-geek.net> Cc: questions@freebsd.org, Walt Pawley 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 10:06:55 -0000 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. -- Mel Problem with today's modular software: they start with the modules and never get to the software part.