Re: objcopy vs absolute addresses

2013/3/30 Jeff Epler : > This is something to do with the ".note.gnu.build-id". > > Both of these alternatives give three identical object files: > > Removing this section in objcopy: > $OBJCOPY -R .note.gnu.build-id ... > > Or requesting that the linker not generate it in the first place >

Re: objcopy vs absolute addresses

This is something to do with the ".note.gnu.build-id". Both of these alternatives give three identical object files: Removing this section in objcopy: $OBJCOPY -R .note.gnu.build-id ... Or requesting that the linker not generate it in the first place $CC -nostdlib -Wl,--build-id=none ...

Re: objcopy vs absolute addresses

Actually, grub-legacy is buildable... Probably, some patches make it possible. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/call-q8zgtnsbp1rfsj_bkklwkkm2msjncvhi3v

Re: objcopy vs absolute addresses

2013/3/30 Игорь Пашев : > Hi, all. > > While trying to build GRUB on illumos [*-pc-solaris2.11], I've found that > for different absolute addresses (-Wl,-Ttext -Wl,) objcopy -O binary > produces different objects files, but it is expected to be the same. Building grub-legacy on Debian/amd64 fails