[uClinux-dev] why empty.o?

Tom Walsh tom at cyberiansoftware.com
Tue Nov 13 11:45:37 EST 2001


> zhanglei wrote:
> 
> Dear all:
> 
> I have found two interesting lines below in
> /opt/uClinux/linux/arch/m68knommu/platform/68EZ328/Rules.make.
> 
> flash.s19: linux.bin arch/$(ARCH)/empty.o
>         $(CROSS_COMPILE)objcopy -v -R .text -R .data -R .bss
> --add-section=.fs=linux.bin --adjust-se
> ction-vma=.fs=$(FLASH_LOAD_ADDR) arch/$(ARCH)/empty.o flash.s19
> 
> romfs.s19: romfs.img arch/$(ARCH)/empty.o
>         $(CROSS_COMPILE)objcopy -v -R .text -R .data -R .bss
> --add-section=.fs=romfs.img --adjust-se
> ction-vma=.fs=$(ROMFS_LOAD_ADDR) arch/$(ARCH)/empty.o romfs.s19
>         $(CROSS_COMPILE)objcopy -O srec romfs.s19
> 
> 

Make can be "bitchy" at times...  Perhaps this is the easiest way to see
that these rules always run?

TomW

-- 
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net, http://cyberiansoftware.com
"Windows? No thanks, I have work to do..."
----------------------------------------------------
This message resent by the uclinux-dev at uclinux.org list server http://www.uClinux.org/



More information about the uClinux-dev mailing list