From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5025 invoked by alias); 4 Oct 2005 21:32:26 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 5004 invoked by uid 22791); 4 Oct 2005 21:32:24 -0000 Received: from yosemite.airs.com (HELO yosemite.airs.com) (205.217.158.180) by sourceware.org (qpsmtpd/0.30-dev) with SMTP; Tue, 04 Oct 2005 21:32:24 +0000 Received: (qmail 24891 invoked by uid 10); 4 Oct 2005 21:32:23 -0000 Received: (qmail 14880 invoked by uid 500); 4 Oct 2005 21:32:16 -0000 Mail-Followup-To: gcc-help@gcc.gnu.org, rob.hatcherson@zedasoft.com To: Rob Hatcherson Cc: gcc-help@gcc.gnu.org Subject: Re: Unexpected File Name Too Long Error With #includes References: <4342F356.8010409@zedasoft.com> From: Ian Lance Taylor Date: Tue, 04 Oct 2005 21:32:00 -0000 In-Reply-To: <4342F356.8010409@zedasoft.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2005-10/txt/msg00020.txt.bz2 Rob Hatcherson 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