[Bug ld/12066] New: cannot move location counter backwards (from 00000000000067e0 to 0000000000000000)

[marcin dot juszkiewicz at linaro dot org]

Today I tried to compile coreboot and seabios for one of my boards. It failed 
under Ubuntu so I tried Debian chroot.

It compiled fine under Debian so I tried to find out where is a problem. 
Matthias Klose pointed me at binutils and it was proper hint.

Current (2.20.51.20100925-1) version in Debian/experimental had same problem as 
Ubuntu one (2.20.51.20100908-0ubuntu2). So I fetched few 
versions from snapshot.debian.org and started testing.

Last good version was 2.20.51.20100527-1 - both project compiled without 
problems.

coreboot (svn://coreboot.org/coreboot/address@hidden) failure:

gcc -m32 -Wa,--divide -fno-stack-protector -Wl,--build-id=none -nostdlib 
-nostartfiles -static -o build/coreboot_ram -Lbuild -T 
src/arch/i386/coreboot_ram.ld build/coreboot_ram.o
src/arch/i386/coreboot_ram.ld:143 cannot move location counter backwards (from 
0000000000118000 to 0000000000004000)
collect2: ld returned 1 exit status
make: *** [build/coreboot_ram] Error 1

seabios (94dc9c49c283cd576c25692d17567035557a2505 revision) failure:

  Linking out/rom16.o
ld -T out/romlayout16.lds out/code16.o -o out/rom16.o
out/romlayout16.lds:429 cannot move location counter backwards (from 
00000000000067e0 to 0000000000000000)
make: *** [out/rom16.o] Error 1

-- 
           Summary: cannot move location counter backwards (from
                    00000000000067e0 to 0000000000000000)
           Product: binutils
           Version: 2.21 (HEAD)
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ld
        AssignedTo: unassigned at sources dot redhat dot com
        ReportedBy: marcin dot juszkiewicz at linaro dot org
                CC: bug-binutils at gnu dot org
  GCC host triplet: x86_64-linux-gnu
GCC target triplet: i586-linux-gnu


http://sourceware.org/bugzilla/show_bug.cgi?id=12066

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.