public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wen-chien Jesse Sung <jesse@cola.voip.idv.tw>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] fix for "make doesn't know how to make target in examples/"
Date: Mon, 10 Jul 2006 21:45:28 +0800	[thread overview]
Message-ID: <44B259F8.8090902@cola.voip.idv.tw> (raw)
In-Reply-To: <20060710125147.92C13353B07@atlas.denx.de>

Wolfgang Denk wrote:
>> A test with the attached Makefile:
>> $ touch 1.src
>> $ make
>> make: *** No rule to make target `1.out', needed by `all'.  Stop.
> 
> This Makefile is not equivlent to what we use in the U-Boot code.
> 
>> all:	1.out
> 
> The "examples/Makefile" is different; it corresponds to:
> 
> 	all:	1.out 1
> 
> ...and this works fine for me with make 3.81

Hi,

I modify the testing Makefile (attached).

$ make
make: *** No rule to make target `1.out', needed by `all'.  Stop.

And then I replace "all: 1.out 1" with "all: 1 1.out", it works.

The sequence of the prerequisites affect the result for me, and that's
what the patch does: place $(TARGET) before $(SREC) and $(BIN). Besides,
it removes the duplicated entries,
SREC = foo.srec
BIN = foo.bin foo
now becomes
SREC = foo.srec
only.

I'm just curious about the difference of make's behavior. :)

-- 
Best Regards,
Wen-chien Jesse Sung
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Makefile
Url: http://lists.denx.de/pipermail/u-boot/attachments/20060710/053781a2/attachment.txt 

  reply	other threads:[~2006-07-10 13:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-10  7:45 [U-Boot-Users] [PATCH] fix for "make doesn't know how to make target in examples/" Wen-chien Jesse Sung
2006-07-10  8:14 ` Wolfgang Denk
2006-07-10  9:27   ` Wen-chien Jesse Sung
2006-07-10 10:28     ` Andreas Schweigstill
2006-07-10 12:51     ` Wolfgang Denk
2006-07-10 13:45       ` Wen-chien Jesse Sung [this message]
2006-07-10 16:41         ` Wolfgang Denk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44B259F8.8090902@cola.voip.idv.tw \
    --to=jesse@cola.voip.idv.tw \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox