On Mon, Jul 15, 2013 at 19:26 +0800, tiger...@viatech.com.cn wrote:
>
> Hi, experts:
> I found no *.lst file produced in root directory after compiling uboot
> source code.
>
> In the Makefile in older version uboot souce code:
> ......
> uboot.bin: uboot
> $(OBJCOPY) ${OBJCFLAGS} -O binary $< $@
> $(OBJDUMP) -d -EL -h -M reg-names-raw --syms
> --full-contents -marm $< > uboot.lst
> ......
>
> I think uboot.lst is very useful .
Which "older version" would that have been?
A quick search shows that there has not been such a feature in
U-Boot as far as git can see (that's back to Nov 2002). Neither
has the binary gone under the 'uboot' or 'uboot.bin' names.
There used to be .lst files, but they held completely different
information than assembler listings. This isn't either what you
wanted.
What you cite is rather specific for an individual platform and
hightly unportable. The search suggests that you are either
referring to an ancient version (more than eleven years old) or a
version that is not "the U-Boot project".
You may invoke the objdump(1) tool any time you like. How often
is it actually that you need to read assembler instructions? And
isn't it that you'd rather want .i or .s files then from the
compiler, instead of 'objdump -d' output that shows a rather
different perspective?
virtually yours
Gerhard Sittig
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr. 5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: off...@denx.de
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
