On Thu, 4 Apr 2013, Augusto Mecking Caringi wrote:
On Thu, Apr 4, 2013 at 7:02 AM, Onur Cem Çelebi <occelebi@gmail.com> wrote:
Output is:
root@F15:~/ruclinux/uClinux-dist# make zImage make: *** No rule to make target `zImage'. Stop.
Maybe, this is the answer:
"Though zImage is a valid Makefile target for all the architectures we discussed in depth in Chapter 3, there are other Linux architectures for which it isn't valid."
http://books.google.com.br/books?id=xnFdWfJAK9wC&pg=PT188&lpg=PT188&dq=zImag...
the set of buildable targets is typically defined by the arch-specific makefile. if you look in the top-level Makefile of the kernel source tree, you'll see a target for building the generic "vmlinux" kernel image, but little more. you need to dig down into the arch-specific directory to see additional targets. for example, if you take a look at arch/arm/boot/Makefile, you'll see: targets := Image zImage xipImage bootpImage uImage ifeq ($(CONFIG_XIP_KERNEL),y) $(obj)/xipImage: vmlinux FORCE $(call if_changed,objcopy) @$(kecho) ' Kernel: $@ is ready (physical address: $(CONFIG_XIP_PHYS_ADDR))' $(obj)/Image $(obj)/zImage: FORCE @echo 'Kernel configured for XIP (CONFIG_XIP_KERNEL=y)' @echo 'Only the xipImage target is available in this case' @false else $(obj)/xipImage: FORCE @echo 'Kernel not configured for XIP (CONFIG_XIP_KERNEL!=y)' @false ... etc etc ... in short, all(?) architectures expect a starting point of a vmlinux, and they will define additional targets as they see fit. rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================