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.

I bumped into the description of the -v flag whilst perusing
the cpp info docs and did this ... after removing the ersatz
/usr/include/iconv.h mentioned above. Apparently these paths are
compiled in (???).

%cat > x
#include <iconv.h>
%cpp -v x
Using built-in specs.
Configured with: FreeBSD/i386 system compiler
Thread model: posix
gcc version 3.4.6 [FreeBSD] 20060305
 /usr/libexec/cc1 -E -quiet -v -D_LONGLONG x
ignoring duplicate directory "/usr/include"
#include "..." search starts here:
#include <...> search starts here:
End of search list.
# 1 "x"
# 1 "<built-in>"
# 1 "<command line>"
# 1 "x"
x:1:19: iconv.h: No such file or directory


Walter M. Pawley <[EMAIL PROTECTED]>
Wump Research & Company
676 River Bend Road, Roseburg, OR 97470
_______________________________________________ mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to