<div dir="ltr"><div><div>Thanks to all but my special thanks go to Robert. I've edited linux-2.6/arch/nios2/Makefile and get it work ! <br><br></div>Cheers,<br></div>Cem<br><div class="gmail_extra"><br><br><div class="gmail_quote">
2013/4/4 Robert P. J. Day <span dir="ltr"><<a href="mailto:rpjday@crashcourse.ca" target="_blank">rpjday@crashcourse.ca</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div>On Thu, 4 Apr 2013, Augusto Mecking Caringi wrote:<br>
<br>
> On Thu, Apr 4, 2013 at 7:02 AM, Onur Cem Çelebi <<a href="mailto:occelebi@gmail.com" target="_blank">occelebi@gmail.com</a>> wrote:<br>
> ><br>
> > Output is:<br>
> ><br>
> > root@F15:~/ruclinux/uClinux-dist# make zImage<br>
> > make: *** No rule to make target `zImage'. Stop.<br>
><br>
> Maybe, this is the answer:<br>
><br>
> "Though zImage is a valid Makefile target for all the architectures we<br>
> discussed in depth in Chapter 3, there are other Linux architectures<br>
> for which it isn't valid."<br>
><br>
> <a href="http://books.google.com.br/books?id=xnFdWfJAK9wC&pg=PT188&lpg=PT188&dq=zImage+is+a+valid+Makefile+target+for+all+the+architectures+we+discussed+in&source=bl&ots=GFTLM7_665&sig=77Oi5e_TmkXME_5du3H5GdqPw4c&hl=pt-BR&sa=X&ei=xZ5dUeqqIY3x0wH4x4D4Cw&ved=0CD0Q6AEwAQ#v=onepage&q&f=false" target="_blank">http://books.google.com.br/books?id=xnFdWfJAK9wC&pg=PT188&lpg=PT188&dq=zImage+is+a+valid+Makefile+target+for+all+the+architectures+we+discussed+in&source=bl&ots=GFTLM7_665&sig=77Oi5e_TmkXME_5du3H5GdqPw4c&hl=pt-BR&sa=X&ei=xZ5dUeqqIY3x0wH4x4D4Cw&ved=0CD0Q6AEwAQ#v=onepage&q&f=false</a><br>
<br>
</div></div> the set of buildable targets is typically defined by the<br>
arch-specific makefile. if you look in the top-level Makefile of the<br>
kernel source tree, you'll see a target for building the generic<br>
"vmlinux" kernel image, but little more.<br>
<br>
you need to dig down into the arch-specific directory to see<br>
additional targets. for example, if you take a look at<br>
arch/arm/boot/Makefile, you'll see:<br>
<br>
targets := Image zImage xipImage bootpImage uImage<br>
<br>
ifeq ($(CONFIG_XIP_KERNEL),y)<br>
<br>
$(obj)/xipImage: vmlinux FORCE<br>
$(call if_changed,objcopy)<br>
@$(kecho) ' Kernel: $@ is ready (physical address:<br>
$(CONFIG_XIP_PHYS_ADDR))'<br>
<br>
$(obj)/Image $(obj)/zImage: FORCE<br>
@echo 'Kernel configured for XIP (CONFIG_XIP_KERNEL=y)'<br>
@echo 'Only the xipImage target is available in this case'<br>
@false<br>
<br>
else<br>
<br>
$(obj)/xipImage: FORCE<br>
@echo 'Kernel not configured for XIP (CONFIG_XIP_KERNEL!=y)'<br>
@false<br>
... etc etc ...<br>
<br>
in short, all(?) architectures expect a starting point of a vmlinux,<br>
and they will define additional targets as they see fit.<br>
<br>
rday<br>
<span><font color="#888888"><br>
--<br>
<br>
========================================================================<br>
Robert P. J. Day Ottawa, Ontario, CANADA<br>
<a href="http://crashcourse.ca" target="_blank">http://crashcourse.ca</a><br>
<br>
Twitter: <a href="http://twitter.com/rpjday" target="_blank">http://twitter.com/rpjday</a><br>
LinkedIn: <a href="http://ca.linkedin.com/in/rpjday" target="_blank">http://ca.linkedin.com/in/rpjday</a><br>
========================================================================</font></span></blockquote></div><br></div></div>