From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4712 invoked by alias); 5 Oct 2005 03:20:08 -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 4689 invoked by uid 22791); 5 Oct 2005 03:20:06 -0000 Received: from yosemite.airs.com (HELO yosemite.airs.com) (205.217.158.180) by sourceware.org (qpsmtpd/0.30-dev) with SMTP; Wed, 05 Oct 2005 03:20:06 +0000 Received: (qmail 29776 invoked by uid 10); 5 Oct 2005 03:20:05 -0000 Received: (qmail 26477 invoked by uid 500); 5 Oct 2005 03:19:58 -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> <43430620.3080002@zedasoft.com> From: Ian Lance Taylor Date: Wed, 05 Oct 2005 03:20:00 -0000 In-Reply-To: <43430620.3080002@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/msg00025.txt.bz2 Rob Hatcherson writes: > In my sort-of trivial test case - which is just a file that #include's > the offending file - the command line is this for both the case that > works and the case that doesn't: > > g++ -E \ > -IC:/WorkAreas/BuildOutput/ZedaSoft/Java/CBA/Domain/Physical/Plugin/Entity/F16/1.4.0/native/include > \ > blah.cpp > > > If the only thing in blah.cpp is this: > > #include > "com/zedasoft/cba/plugin/entity/platform/air/fighter/f16/view/cockpit/hud/f16hudcore/F16Hud.h" > > Then I get this result: > > blah.cpp:3:104: > com/zedasoft/cba/plugin/entity/platform/air/fighter/f16/view/cockpit/hud/f16hudcore/F16Hud.h: > File name too long > # 1 "blah.cpp" > # 1 "" > # 1 "" > # 1 "blah.cpp" Thanks. As far as I can see, this error is happening because the open system call failed and set errno to some value. When strerror was called on that value, it returned "File name too long". Presumably the errno value is ENAMETOOLONG. You might try running gcc with the -v option to see what the last directory in the search path is, since it is presumably when using that directory that ENAMETOOLONG is returned. Otherwise I don't have any suggestions other than running it in the debugger to see what the actual failing name is. Ian