From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To: <djgpp-workers AT delorie DOT com>
Cc: <eliz AT is DOT elta DOT co DOT il>
Subject: RE: gettext pretest available
Date: Mon, 12 Mar 2001 19:27:14 +0100
Message-ID: <CAEGKOHJKAAFPKOCLHDIGEHMCBAA.tim.van.holder@pandora.be>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-reply-to: <Pine.SUN.3.91.1010312162035.28582B-100000@is>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> I don't understand: the failure above seems to be a compile time failure
> (some of the header files are not found), not a run-time failure.  So how
> can EXEEXT be connected to this?  I'd suspect some snafu with -I switch
> passed (or which should have been passed) to the compiler.
Yes, but automake probably created a rule like

cake$(EXEEXT): cake.o
	$(GCC) -I blah $< -o $@

And since the dependency lists 'cake', make tries to build 'cake' and falls
back on the builtin 'make executable from object' rule, which would not
include the -I.