[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#493650: try rebuilding with gcc-4.4



On 27/09/10 10:52, Brendon Green wrote:
What's the easiest way I can get gcc 4.3.1 (packaged or not) into Ubuntu Lucid, so I may use it to verify the bug?

Okay, I figured out how to install multiple GCC's (astoundingly easy) and, more importantly, how to convince "make" to use them.

Interestingly, I have not managed a clean compile with any compiler version I tried.

The compilers marked "pass" below successfully compiled "sched.o", then later aborted with a message similar to:

make ARCH=um SUBARCH=i386 HOSTCC=gcc-4.1 CC=gcc-4.1
...
  LD      init/built-in.o
  LD      .tmp_vmlinux1
/usr/lib/gcc/i486-linux-gnu/4.1.3/../../../../lib/libc.a(elf-init.o): In function `__libc_csu_irel':
(.text+0xe5): undefined reference to `__rel_iplt_end'
/usr/lib/gcc/i486-linux-gnu/4.1.3/../../../../lib/libc.a(elf-init.o): In function `__libc_csu_irel':
(.text+0xec): undefined reference to `__rel_iplt_start'
/usr/lib/gcc/i486-linux-gnu/4.1.3/../../../../lib/libc.a(elf-init.o): In function `__libc_csu_irel':
(.text+0xfd): undefined reference to `__rel_iplt_start'
/usr/lib/gcc/i486-linux-gnu/4.1.3/../../../../lib/libc.a(elf-init.o): In function `__libc_csu_irel':
(.text+0x106): undefined reference to `__rel_iplt_start'
/usr/lib/gcc/i486-linux-gnu/4.1.3/../../../../lib/libc.a(elf-init.o): In function `__libc_csu_irel':
(.text+0x113): undefined reference to `__rel_iplt_start'
/usr/lib/gcc/i486-linux-gnu/4.1.3/../../../../lib/libc.a(elf-init.o): In function `__libc_csu_irel':
(.text+0x11b): undefined reference to `__rel_iplt_start'
collect2: ld returned 1 exit status
  KSYM    .tmp_kallsyms1.S
nm: '.tmp_vmlinux1': No such file
No valid symbol.
make: *** [.tmp_kallsyms1.S] Error 1

Tested versions of GCC (from various Debian stable, testing, unstable, experimental/Ubuntu lucid repositories):

pass  4.1.2-27ubuntu1
pass  4.2.4-6
FAIL  4.3.2-1.1
FAIL  4.3.4-10ubuntu1
FAIL  4.3.5-2
pass  4.4.3-4ubuntu5
pass  4.5.1-8


Regards,
Brendon Green




Reply to: