From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Schwierzeck Date: Wed, 3 Oct 2012 17:21:48 +0200 Subject: [U-Boot] [PATCH 3/5] common: Add .u_boot_list into all linker files In-Reply-To: <201210031701.16900.marex@denx.de> References: <1348964274-12489-1-git-send-email-marex@denx.de> <1348964274-12489-4-git-send-email-marex@denx.de> <201210031701.16900.marex@denx.de> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 2012/10/3 Marek Vasut : > Dear Daniel Schwierzeck, > > [...] > >> this can't work because u-boot.lst is genereated in top-level directory >> but linking of standalone code happens in the according subdirectories. >> Thus the linker can't find u-boot.lst. >> >> Example for MIPS standalone: >> >> /opt/eldk-5.2.1/mips/sysroots/i686-eldk-linux/usr/bin/mips32-linux/mips-lin >> ux-ld.bfd -G 0 -static -n -nostdlib -EB -g -Ttext 0x80200000 -T mips.lds \ >> -o hello_world -e hello_world hello_world.o libstubs.o \ >> -L/opt/eldk-5.2.1/mips/sysroots/mips32- > linux/usr/lib/mips-linux/4.6.4 >> -lgcc >> /opt/eldk-5.2.1/mips/sysroots/i686-eldk-linux/usr/bin/mips32-linux/mips-li >> nux-ld.bfd: cannot open linker script file u-boot.lst: No such file or >> directory > > Do you have any suggestion? I recall compiling it for mips ... Do we really need u-boot.lst in standalone applications? I think there is no need for u_boot_cmd or DM. -- Best regards, Daniel