From: Ian Lance Taylor <ian@airs.com>
To: Rob Hatcherson <rob.hatcherson@zedasoft.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Unexpected File Name Too Long Error With #includes
Date: Tue, 04 Oct 2005 21:32:00 -0000 [thread overview]
Message-ID: <m3hdbx9den.fsf@gossamer.airs.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2005-10-04 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 21:25 Rob Hatcherson
2005-10-04 21:32 ` Ian Lance Taylor [this message]
2005-10-04 22:45 ` Rob Hatcherson
2005-10-05 3:20 ` Ian Lance Taylor
2005-10-05 14:05 ` Rob Hatcherson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3hdbx9den.fsf@gossamer.airs.com \
--to=ian@airs.com \
--cc=gcc-help@gcc.gnu.org \
--cc=rob.hatcherson@zedasoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).