gzrt version 0.5-1 failed to build on amd64 with GCC-4.6/oneiric
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gzrt (Debian) |
Fix Released
|
Unknown
|
|||
gzrt (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Oneiric |
Fix Released
|
High
|
Unassigned |
Bug Description
gzrt version 0.5-1 failed to build on amd64 with GCC-4.6/oneiric
Link to failed build: https:/
Details about the rebuild:
https:/
Direct link to the build log: https:/
This log snippet might be of interest, since it triggered the matcher 'Purging chroot-autobuild'.
Excerpt 837 lines into the build log:
cc -g -O2 -Wall -D_LARGEFILE_SOURCE -D_FILE_
gzrecover.c: In function 'main':
gzrecover.c:335:21: warning: format '%d' expects argument of type 'int', but argument 3 has type 'size_t' [-Wformat]
/tmp/ccUtGYS9.o: In function `init_zlib':
/build/
/tmp/ccUtGYS9.o: In function `main':
/build/
/build/
/build/
/build/
collect2: ld returned 1 exit status
make[1]: *** [gzrecover] Error 1
make[1]: Leaving directory `/build/
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
*******
Build finished at 20110423-0902
FAILED [dpkg-buildpackage died]
Purging chroot-
Related branches
Changed in gzrt (Ubuntu): | |
importance: | Undecided → High |
Changed in gzrt (Ubuntu): | |
milestone: | none → oneiric-alpha-3 |
Changed in gzrt (Debian): | |
status: | Unknown → New |
Changed in gzrt (Debian): | |
status: | New → Fix Released |
This builds fine on Debian with GCC 4.6, what is Ubuntu doing differently to make it fail?