While trying to build gcc 3.4.3 on a RHEL5/i386 system in a chroot we see
> Comparing stage2 and stage3 of the compiler
> gmake[1]: Entering directory `/opt/build/gcc-3.4.3-objdir3/gcc'
> [...]
> Bootstrap comparison failure!
> ./alloc-pool.o differs
> ./bb-reorder.o differs
> ./bt-load.o differs
> [...]
The list of object files can differ, and the differences are not visible with
disassembling with objdump (see below). It looks like the differences are from
the padding space between the aligned sections. What could be wrong?
If the build is done outside the chroot then the comparison succeeds. We have
already tried to map everything outside/inside the chroot (including /proc,
/dev etc) but sysfs and binfmt_misc. Does the gcc stage 2/3 build make any use
of these?
Thanks!
[EMAIL PROTECTED] ~]#
file1=/opt/build/gcc-3.4.3-objdir3/gcc/stage2/alloc-pool.o;
file2=/opt/build/gcc-3.4.3-objdir3/gcc/alloc-pool.o
[EMAIL PROTECTED] ~]# cmp -l $file1 $file2
2714 75 262
2715 312 57
2716 10 12
[EMAIL PROTECTED] ~]# objdump -Dxzs --prefix-addresses $file1 > /tmp/c-1
[EMAIL PROTECTED] ~]# objdump -Dxzs --prefix-addresses $file2 > /tmp/c-2
[EMAIL PROTECTED] ~]# diff -ud /tmp/c-1 /tmp/c-2
--- /tmp/c-1 2007-08-14 12:31:37.000000000 -0500
+++ /tmp/c-2 2007-08-14 12:31:42.000000000 -0500
@@ -1,6 +1,6 @@
-/opt/build/gcc-3.4.3-objdir3/gcc/stage2/alloc-pool.o: file format
elf32-i386
-/opt/build/gcc-3.4.3-objdir3/gcc/stage2/alloc-pool.o
+/opt/build/gcc-3.4.3-objdir3/gcc/alloc-pool.o: file format elf32-i386
+/opt/build/gcc-3.4.3-objdir3/gcc/alloc-pool.o
architecture: i386, flags 0x00000011:
HAS_RELOC, HAS_SYMS
start address 0x00000000
--
Summary: Bootstrap comparison failure between stage2/3 but no
objdump differences
Product: gcc
Version: 3.4.3
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: Axel dot Thimm at ATrpms dot net
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33070
