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

Bug#489114: marked as done (gcc-4.3: FTBFS: Bootstrap comparison failure!)



Your message dated Sat, 5 Jul 2008 10:46:51 +0200
with message-id <18543.13563.782572.554564@gargle.gargle.HOWL>
and subject line Re: Bug#489114: gcc-4.3: FTBFS: Bootstrap comparison failure!
has caused the Debian Bug report #489114,
regarding gcc-4.3: FTBFS: Bootstrap comparison failure!
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
489114: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489114
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-4.3
Version: 4.3.1-4
Severity: serious
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20080702 qa-ftbfs
Justification: FTBFS on i386

Hi,

During a rebuild of all packages in sid, your package failed to build on
i386.

Relevant part:
> make[5]: Entering directory `/build/user-gcc-4.3_4.3.1-4-amd64-rAo2YU/gcc-4.3-4.3.1-4/build'
> rm -f stage_current
> make[5]: Leaving directory `/build/user-gcc-4.3_4.3.1-4-amd64-rAo2YU/gcc-4.3-4.3.1-4/build'
> Comparing stages 2 and 3
> warning: ./cc1objplus-checksum.o differs
> warning: ./cc1obj-checksum.o differs
> warning: ./cc1-checksum.o differs
> warning: ./cc1plus-checksum.o differs
> Bootstrap comparison failure!
> ./sparseset.o differs
> make[4]: *** [compare] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2008/07/02

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment.  Internet was not accessible from the build systems.

-- 
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |



--- End Message ---
--- Begin Message ---
closing as invalid. Lucas, please stop reporting this non-issue for
all gcc related packages, if you do not reproduce it outside the grid
environment. this is *again* not reproducible, stealing me the time,
having to re-run the build.

  Matthias

Lucas Nussbaum writes:
> Package: gcc-4.3
> Version: 4.3.1-4
> Severity: serious
> User: debian-qa@lists.debian.org
> Usertags: qa-ftbfs-20080702 qa-ftbfs
> Justification: FTBFS on i386
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> i386.
> 
> Relevant part:
> > make[5]: Entering directory `/build/user-gcc-4.3_4.3.1-4-amd64-rAo2YU/gcc-4.3-4.3.1-4/build'
> > rm -f stage_current
> > make[5]: Leaving directory `/build/user-gcc-4.3_4.3.1-4-amd64-rAo2YU/gcc-4.3-4.3.1-4/build'
> > Comparing stages 2 and 3
> > warning: ./cc1objplus-checksum.o differs
> > warning: ./cc1obj-checksum.o differs
> > warning: ./cc1-checksum.o differs
> > warning: ./cc1plus-checksum.o differs
> > Bootstrap comparison failure!
> > ./sparseset.o differs
> > make[4]: *** [compare] Error 1
> 
> The full build log is available from:
>    http://people.debian.org/~lucas/logs/2008/07/02
> 
> A list of current common problems and possible solutions is available at 
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
> 
> About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
> of the Grid'5000 platform, using a clean chroot containing a sid i386
> environment.  Internet was not accessible from the build systems.
> 
> -- 
> | Lucas Nussbaum
> | lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
> | jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |


--- End Message ---

Reply to: