From:	"Stephen Wade" <maitrek AT austarmetro DOT com DOT au>
Newsgroups:	comp.os.msdos.djgpp
References:	<3e350912$1 AT news DOT comindico DOT com DOT au> <b13eov$2qc$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE>
Subject:	Re: Going insane with Make
Lines:	70
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 5.00.2615.200
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2615.200
X-Original-NNTP-Posting-Host:	203.221.55.249
Message-ID:	<3e357331$1@news.comindico.com.au>
X-Original-Trace:	28 Jan 2003 04:58:09 +1000, 203.221.55.249
Date:	Mon, 27 Jan 2003 17:58:14 GMT
NNTP-Posting-Host:	203.194.27.1
X-Complaints-To:	abuse AT comindico DOT com DOT au
X-Trace:	news.optus.net.au 1043690294 203.194.27.1 (Tue, 28 Jan 2003 04:58:14 EST)
NNTP-Posting-Date:	Tue, 28 Jan 2003 04:58:14 EST
Organization:	Comindico Australia - reports relating to abuse should be sent to abuse AT comindico DOT com DOT au
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

I discovered that when you are using makefiles in a directory (or a sub-dir)
of the \dev\ directory, it tends to get a bit crazy.

However, as you pointed out, my makefile was a mess anyway, I cleaned that
up and now it runs fine, cheers!

Pity I'm such a newbie :(

Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de> wrote in message
news:b13eov$2qc$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE...
> Stephen Wade <maitrek AT austarmetro DOT com DOT au> wrote:
> > This is my frist attempt at using a makefile, and every time i run
"make"
> > from the MS-DOS prompt in windows 98 in a directory which contains this
> > makefile
>
> Your makefile has several potential or guaranteed problems.
>
> > (called 'makefile')
> > #------------------
> > vpath %.c ..\src
>               ^----- use / here, if possible.
>
> The DJGPP port tries to allow backslashes, but in case of doubt,
> forward slashes will work better.  The original Unix Make syntax is
> not very friendly to backslashes as directory separators.
>
> (Same for drive letters).
>
> > vpath %.h ..\src
>
> > CC=gcc.exe
>
> > vexle : vexle.o vbe3.o mouse.o
> >  cc -o vexle vexle.o vbe3.o mouse.o
>
> Drop all these "cc" lines.  They won't work, for three reasons:
>
> 1) You indented them with only a space.  Unix Makefile syntax insists on
> a literal <TAB> character.
>
> 2) 'cc' is not the name of the compiler.  write $(CC), or just 'gcc',
>    instead.
>
> 3) If you provide the commands to be run, with all their arguments, Make
>    can't properly carry out the automatic filename substitutions governed
>    by your "vpath" directives above.
>
> > I get the output
> > "make.exe: *** No targets specified and no makefile found.  Stop."
>
> > Why is it saying this? As far as I can tell I have a valid target,
>
> You didn't *name* one, on the "make" command line, is what this
> message means.
>
> > and the makefile is *definitely* there (I'm not that dumb - or am i
> > :) )
>
> Just to be sure: check that "dir makefile" really does list the file
> as just "makefile", _Not_ "makefile.txt" or some other Windows
> silliness that you wouldn't see in the default settings of Explorer.
>
> Never trust what Explorer shows you unless you changed the relevant
> settings yourself.
> --
> Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
> Even if all the snow were burnt, ashes would remain.

- Raw text -