Bug#710220: libstdc++6: 4.8.0-8 upgrade breaks system_clock

2013-05-29 Thread Tim Besard
Hi Matthias, > Please could you name the software where you did see this failure? I only spotted this regression in my own development code, so it seems that the impact is limited after all. Thanks, Tim -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscr

Bug#710240: stage1 gcc depends on libgcc-*-dev and gcc-VERSION-base

2013-05-29 Thread YunQiang Su
On Thu, May 30, 2013 at 12:05 AM, Matthias Klose wrote: > Am 29.05.2013 11:50, schrieb YunQiang Su: >> Package: gcc-4.8 >> >> When build gcc-4.8 using >> WITH_SYSROOT=/ DEB_STAGE=stage1 debuild -B -d >> >> the generated gcc-4.8-TRIPLE package depends on gcc-4.8-base >> and libgcc-4.8-dev-ARCH-cros

gdc-4.8_4.8.0-2_amd64.changes ACCEPTED into unstable

2013-05-29 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 29 May 2013 23:05:40 +0200 Source: gdc-4.8 Binary: gdc-4.8 libphobos-4.8-dev libphobos-4.8-dbg Architecture: source amd64 Version: 4.8.0-2 Distribution: unstable Urgency: low Maintainer: Debian GCC Maintainers Chang

Processing of gdc-4.8_4.8.0-2_amd64.changes

2013-05-29 Thread Debian FTP Masters
gdc-4.8_4.8.0-2_amd64.changes uploaded successfully to localhost along with the files: gdc-4.8_4.8.0-2.dsc gdc-4.8_4.8.0-2.diff.gz gdc-4.8_4.8.0-2_amd64.deb libphobos-4.8-dev_4.8.0-2_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSC

Bug#710220: libstdc++6: 4.8.0-8 upgrade breaks system_clock

2013-05-29 Thread Matthias Klose
Am 29.05.2013 16:09, schrieb Matthias Klose: > So first lets see which packages are affected, then decide how to address this > (currently searching the Ubuntu archive for these symbols, lacking the > resources > to do that for the Debian archive). You only see this in c++0x/c++11 mode, so > this

Bug#710266: marked as done (gcc-4.8: fails to build current git head kernel x86-64 architecture)

2013-05-29 Thread Debian Bug Tracking System
Your message dated Wed, 29 May 2013 23:05:02 +0200 with message-id <51a66d7e@debian.org> and subject line Re: Bug#710266: gcc-4.8: fails to build current git head kernel x86-64 architecture has caused the Debian Bug report #710266, regarding gcc-4.8: fails to build current git head kernel x86-

gcc-4.8_4.8.0-9_amd64.changes ACCEPTED into unstable

2013-05-29 Thread Debian FTP Masters
) libx32stdc++6 - GNU Standard C++ Library v3 (x32) libx32stdc++6-4.8-dbg - GNU Standard C++ Library v3 (debugging files) Closes: 710142 710224 Changes: gcc-4.8 (4.8.0-9) unstable; urgency=low . * Update to SVN 20130529 (r199410) from the gcc-4_8-branch. * Drop build dependency on automake, not

Processing of gcc-4.8_4.8.0-9_amd64.changes

2013-05-29 Thread Debian FTP Masters
gcc-4.8_4.8.0-9_amd64.changes uploaded successfully to localhost along with the files: gcc-4.8_4.8.0-9.dsc gcc-4.8_4.8.0-9.diff.gz gcc-4.8-source_4.8.0-9_all.deb libstdc++-4.8-doc_4.8.0-9_all.deb gcc-4.8-locales_4.8.0-9_all.deb gcc-4.8-base_4.8.0-9_amd64.deb libgcc1_4.8.0-9_amd64.deb

Bug#710224: marked as done (Should disable libatomic when DEB_STAGE is set)

2013-05-29 Thread Debian Bug Tracking System
rary (x32 debug symbols) libx32stdc++-4.8-dev - GNU Standard C++ Library v3 (development files) libx32stdc++6 - GNU Standard C++ Library v3 (x32) libx32stdc++6-4.8-dbg - GNU Standard C++ Library v3 (debugging files) Closes: 710142 710224 Changes: gcc-4.8 (4.8.0-9) unstable; urgency=low . *

Bug#710142: marked as done (FTBFS "Assembler messages: Error: expecting string instruction after `rep'")

2013-05-29 Thread Debian Bug Tracking System
nstable; urgency=low . * Update to SVN 20130529 (r199410) from the gcc-4_8-branch. * Drop build dependency on automake, not used anymore. * Build with binutils from unstable (the 4.8.0-8 package was accidentally built with binutils from experimental). Closes: #710142. * Explicity configur

Results for 4.8.0 (Debian 4.8.0-8) testsuite on sparc-unknown-linux-gnu

2013-05-29 Thread Matthias Klose
LAST_UPDATED: Mon May 27 08:19:29 UTC 2013 (revision 199350) Target: sparc-linux-gnu gcc version 4.8.0 (Debian 4.8.0-8) Native configuration is sparc-unknown-linux-gnu === g++ tests === Running target unix === g++ Summary for unix === # of expected passes

Results for 4.8.0 (Debian 4.8.0-8) testsuite on powerpc-unknown-linux-gnu

2013-05-29 Thread Matthias Klose
LAST_UPDATED: Mon May 27 08:19:29 UTC 2013 (revision 199350) Target: powerpc-linux-gnu gcc version 4.8.0 (Debian 4.8.0-8) Native configuration is powerpc-unknown-linux-gnu === g++ tests === Running target unix === g++ Summary for unix === # of expected passes

Results for 4.8.0 (Debian 4.8.0-8) testsuite on x86_64-pc-kfreebsd-gnu

2013-05-29 Thread Matthias Klose
LAST_UPDATED: Mon May 27 08:19:29 UTC 2013 (revision 199350) Target: x86_64-kfreebsd-gnu gcc version 4.8.0 (Debian 4.8.0-8) Native configuration is x86_64-pc-kfreebsd-gnu === g++ tests === Running target unix === g++ Summary for unix === # of expected passes

Results for 4.8.0 (Debian 4.8.0-8) testsuite on x86_64-pc-linux-gnu

2013-05-29 Thread Matthias Klose
LAST_UPDATED: Mon May 27 08:19:29 UTC 2013 (revision 199350) Target: x86_64-linux-gnu gcc version 4.8.0 (Debian 4.8.0-8) Native configuration is x86_64-pc-linux-gnu === g++ tests === Running target unix === g++ Summary for unix === # of expected passes

Results for 4.8.0 (Debian 4.8.0-8) testsuite on i486-pc-linux-gnu

2013-05-29 Thread Matthias Klose
LAST_UPDATED: Mon May 27 08:19:29 UTC 2013 (revision 199350) Target: i486-linux-gnu gcc version 4.8.0 (Debian 4.8.0-8) Native configuration is i486-pc-linux-gnu === g++ tests === Running target unix === g++ Summary for unix === # of expected passes

Processed: Re: Bug#710142: FTBFS "Assembler messages: Error: expecting string instruction after `rep'"

2013-05-29 Thread Debian Bug Tracking System
Processing control commands: > severity -1 grave Bug #710142 [gcc-4.8] FTBFS "Assembler messages: Error: expecting string instruction after `rep'" Severity set to 'grave' from 'important' > block 701327 by -1 Bug #701327 [src:mwrap] mwrap: ftbfs with GCC-4.8 701327 was blocked by: 705485 701327 w

Bug#710142: FTBFS "Assembler messages: Error: expecting string instruction after `rep'"

2013-05-29 Thread Sébastien Villemot
Control: severity -1 grave Control: block 701327 by -1 Control: block 701329 by -1 Control: block 701270 by -1 Le mardi 28 mai 2013 à 17:35 +0200, Anton Gladky a écrit : > last update of gcc causes FTBFS (in this case, yade package): > > /tmp/ccNQ6K5n.s: Assembler messages: > /tmp/ccNQ6K5n.s:420

Bug#710240: stage1 gcc depends on libgcc-*-dev and gcc-VERSION-base

2013-05-29 Thread Matthias Klose
Am 29.05.2013 11:50, schrieb YunQiang Su: > Package: gcc-4.8 > > When build gcc-4.8 using > WITH_SYSROOT=/ DEB_STAGE=stage1 debuild -B -d > > the generated gcc-4.8-TRIPLE package depends on gcc-4.8-base > and libgcc-4.8-dev-ARCH-cross, while both of these 2 packages are > missing here. > > The a

Processed: reassign to lilo

2013-05-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 709818 lilo Bug #709818 [cpp-4.8] Error compiling lilo Bug reassigned from package 'cpp-4.8' to 'lilo'. No longer marked as found in versions gcc-4.8/4.8.0-7. Ignoring request to alter fixed versions of bug #709818 to the same values pre

Bug#710220: libstdc++6: 4.8.0-8 upgrade breaks system_clock

2013-05-29 Thread Matthias Klose
Am 29.05.2013 09:39, schrieb Tim Besard: > Package: libstdc++6 > Version: 4.8.0-8 > Severity: important > > Dear Maintainer, > > Attached test case gets the current system time using std::chrono and using > gettimeofday, both with millisecond precision. Using libstdc++6 version > 4.8.0-7, > this

Bug#710266: gcc-4.8: fails to build current git head kernel x86-64 architecture

2013-05-29 Thread Arthur Marsh
Package: gcc-4.8 Version: 4.8.0-8 Followup-For: Bug #710266 I tried building the kernel with: MAKEFLAGS="CC=gcc-4.8 LD=ld.gold CFLAGS=-save-temps=obj" \ make-kpkg --config menuconfig --initrd linux-image which finished with: CC arch/x86/boot/compressed/misc.o /tmp/ccP2VYLr.s: Assembler m

gdc-4.8_4.8.0-1_amd64.changes ACCEPTED into unstable, unstable

2013-05-29 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 12 May 2013 21:21:56 +0200 Source: gdc-4.8 Binary: gdc-4.8 libphobos-4.8-dev libphobos-4.8-dbg Architecture: source amd64 Version: 4.8.0-1 Distribution: unstable Urgency: low Maintainer: Debian GCC Maintainers Chang

Processed: Re: Bug#710266: gcc-4.8: fails to build current git head kernel x86-64 architecture

2013-05-29 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + moreinfo Bug #710266 [gcc-4.8] gcc-4.8: fails to build current git head kernel x86-64 architecture Added tag(s) moreinfo. -- 710266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710266 Debian Bug Tracking System Contact ow...@bugs.debian.org with pro

Bug#710266: gcc-4.8: fails to build current git head kernel x86-64 architecture

2013-05-29 Thread Matthias Klose
Control: tags -1 + moreinfo thanks Am 29.05.2013 14:13, schrieb Arthur Marsh: > After the last gcc-4.8 update, building the 3.10-rc3 and later kernel > for x86-64 (optimised for Opteron/Athlon64 architecture) failed: > > /tmp/cc1gDLm4.s: Assembler messages: > /tmp/cc1gDLm4.s:43: Error: expecting

Bug#710142: FTBFS "Assembler messages: Error: expecting string instruction after `rep'"

2013-05-29 Thread Matthias Klose
Control: tags -1 + moreinfo thanks Am 28.05.2013 17:53, schrieb Basile Starynkevitch: > On Tue, May 28, 2013 at 05:35:38PM +0200, Anton Gladky wrote: >> Package: gcc-4.8 >> Version: 4.8.0-8 >> Severity: important >> >> Dear Maintainer, >> last update of gcc causes FTBFS (in this case, yade package

Processed: Re: Bug#710142: FTBFS "Assembler messages: Error: expecting string instruction after `rep'"

2013-05-29 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + moreinfo Bug #710142 [gcc-4.8] FTBFS "Assembler messages: Error: expecting string instruction after `rep'" Added tag(s) moreinfo. -- 710142: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710142 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#710266: gcc-4.8: fails to build current git head kernel x86-64 architecture

2013-05-29 Thread Arthur Marsh
Package: gcc-4.8 Version: 4.8.0-8 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action?

Bug#710240: stage1 gcc depends on libgcc-*-dev and gcc-VERSION-base

2013-05-29 Thread YunQiang Su
Package: gcc-4.8 When build gcc-4.8 using WITH_SYSROOT=/ DEB_STAGE=stage1 debuild -B -d the generated gcc-4.8-TRIPLE package depends on gcc-4.8-base and libgcc-4.8-dev-ARCH-cross, while both of these 2 packages are missing here. The attached patch disable it depends on these 2 packages if they a

Bug#710142: Confirm

2013-05-29 Thread Benjamin Eikel
Hello, I see this bug, too (e.g., when compiling KDevelop or LLVM). After a downgrade to 4.8.0-7 from testing, the bug is gone. Kind regards Benjamin -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org A

Bug#710224: Should disable libatomic when DEB_STAGE is set

2013-05-29 Thread YunQiang Su
Package: gcc-4.8 When DEB_STAGE is defined, with_libatomic is set no, while there is no '--disable-libatomic' In debian/rules2 (about line 150). It will make stage1 failed to build. I get this error by echo 'mips64el' > debian/target; WITH_SYSROOT=/ DEB_STAGE=stage1 debuild -B -- YunQiang Su

Bug#710220:

2013-05-29 Thread Tim Besard
This also seems to apply to already-compiled binaries, e.g. if I compile the aforementioned testcase with libstdc++6 version 4.8.0-7, which results in correct output, and then upgrade libstdc++6 to version 4.8.0-8, re-running the testcase without recompilation results in faulty output. So since th

Bug#710220: libstdc++6: 4.8.0-8 upgrade breaks system_clock

2013-05-29 Thread Tim Besard
Package: libstdc++6 Version: 4.8.0-8 Severity: important Dear Maintainer, Attached test case gets the current system time using std::chrono and using gettimeofday, both with millisecond precision. Using libstdc++6 version 4.8.0-7, this code works properly, both timestamps being identical. However