From: "Juan Manuel Guerrero" <ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De>
Organization: Darmstadt University of Technology
To: djgpp-workers AT delorie DOT com
Date: Mon, 12 Mar 2001 21:32:19 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: RE: gettext pretest available
CC: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, Bruno Haible <haible AT ilog DOT fr>,
        Tim Van Holder <tim DOT van DOT holder AT pandora DOT be>
In-reply-to: <CAEGKOHJKAAFPKOCLHDIGEHMCBAA.tim.van.holder@pandora.be>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1010312162035 DOT 28582B-100000 AT is>
X-mailer: Pegasus Mail for Windows (v2.54DE)
Message-ID: <46C34D17FBB@HRZ1.hrz.tu-darmstadt.de>
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

On Mon, 12 Mar 2001 19:27:14 +0100, Tim Van Holder wrote:
> > 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.
That is the point. The $(EXEEXT) must explicetily given or a default rule will be
used that will not DTRT.
This can be seen by running the command
  make -d

Anyway, the patch I have submitted will fix this bug.

Regards,
Guerrero, Juan Manuel