This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Unexpected File Name Too Long Error With #includes
- From: Ian Lance Taylor <ian at airs dot com>
- To: Rob Hatcherson <rob dot hatcherson at zedasoft dot com>
- Cc: gcc-help at gcc dot gnu dot org
- Date: 04 Oct 2005 14:32:16 -0700
- Subject: Re: Unexpected File Name Too Long Error With #includes
- References: <4342F356.8010409@zedasoft.com>
Rob Hatcherson <rob.hatcherson@zedasoft.com> writes:
> The problem occurs if I provide a part of this path via a -I option,
> and put the remainder inside quotes in the #include. So say I do this:
>
> gcc -E -I C:/d1/d2/d3/d4 blah.c
>
> ...with the source file looking notionally like this:
>
> #include "...lots more.../blah.h"
>
>
> By experimentation (with this particular file I'm having problems
> with, so this isn't a general observation) when the total length of
> the stuff inside the quotes in the #include statement reaches 82
> characters in length I get a "File name too long" error from the
> preprocessor. Yet as noted earlier I can include the entire path
> inline without a complaint.
What is the exact command line, and what is the exact error message?
Ian