[coreboot] Problem with objcopy: cannot generate coreboot.strip

[Jeffrey C. Jacobs]

Thanks for your reply, Myles!

Myles Watson wrote:
>
>
> On Thu, Jul 16, 2009 at 6:55 AM, Jeffrey C. Jacobs 
> <jacobs at itd.nrl.navy.mil <mailto:jacobs at itd.nrl.navy.mil>> wrote:
>
>     --------
>     gcc -m32 -nostdlib -nostartfiles -static -o linuxbios -T
>     ldscript.ld crt0.o
>     /usr/bin/ld: warning: dot moved backwards before `.text'
>     /usr/bin/ld: warning: dot moved backwards before `.id'
>     /usr/bin/ld: warning: dot moved backwards before `.text'
>     /usr/bin/ld: warning: dot moved backwards before `.id'
>     /usr/bin/ld: warning: dot moved backwards before `.text'
>     /usr/bin/ld: warning: dot moved backwards before `.id'
>
> I haven't seen these warnings.  Are they the cause?
Well, I just tried to build the Tyan S1846 board and got these warnings 
for CRT0:

/usr/bin/ld: warning: dot moved backwards before `.id'
/usr/bin/ld: warning: dot moved backwards before `.id'
/usr/bin/ld: warning: dot moved backwards before `.id'

So I guess that may be a red herring since...
>
>     nm -n linuxbios | sort > linuxbios.map
>     objcopy --gap-fill 0xff -R .note.gnu.build-id -O binary linuxbios
>     linuxbios.strip
>     objcopy: linuxbios.strip: Bad value
>     objcopy: linuxbios.strip: Bad value
>     make[1]: *** [linuxbios.strip] Error 1
>     make[1]: Leaving directory
>     `/home/jacobs/LinuxBIOS-v2-GRUB-PTR/targets/arcom/apollo/apollo/image'
>     make: *** [image/linuxbios.rom] Error 1
>
>
> I haven't seen anything like this myself.  Do all boards fail for you, 
> or is it just this one?  Abuild still passes all the boards for me.
... the Tyan S1846 DOES pass the objcopy step so it looks to be specific 
to my target (the arcom/apollo board).  The funny thing is, this was all 
working before I updated to the latest version (though I could never 
boot past the jump to boot loader step before).  I should also note in 
the strace I originally attached that objcopy literally tries to write 
like 4GB of 0xFF before dying if that helps.  In fact, it prints one Bad 
value before the massive write, and one after.  Also, to be clear, the 
strace I attached was for my build of the latest Coreboot, not from my 
old LinuxBIOS and that I get the same error for both the old and current 
edition.

Thanks again!

Jeffrey.