> On Tue, Oct 30, 2001 at 10:34:31PM +0100, Christoph Egger wrote: > | > Christoph Egger wrote: > | > > | > > | > >>a quick shot in the dark: you are calling 'make' recursively, while > you > | > >>*should* call $(MAKE) instead (which always has the correct value). > | > >> > | > > > | > > Yes, in the Makefile. But not on the shell... > | > > | > > | > right, and it appears it is the Makefile which calls 'make', not > $(MAKE) > | > which would be 'gmake'... > | > | I don't know, if 'gmake' is the right one to call. I just did 'trial and > | error', because the usual 'make' command doesn't exist there. In the > | Makefile (created by configure), I can find lines where $(MAKE) is used, > but > | there is NO line like this: > | > | MAKE=make > | > | So I can't figure out, what the value of $(MAKE) is. > > echo 'def:\n\techo $(MAKE)' > test.makefile > gmake -f test.makefile > > > That is, put an 'echo' command in a target and run make so that that > target is executed. I believe that $(MAKE) is set automatically so > that you don't have to worry about it.
It seems I have to worry. :( Your test.makefile returns ----------------------------- echo gmake ----------------------------- therefore $(MAKE) is gmake. But why tries gmake to call "make" then when I wanna compile libgii, although this doesn't exist? -- CU, Christoph Egger E-Mail: [EMAIL PROTECTED] GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net
