Processed: fixed 400031 in 4.1.1ds2-22

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.6 > fixed 400031 4.1.1ds2-22 Bug#400031: gcc-4.1: Enable -pthread for GNU/Hurd Bug marked as fixed in version 4.1.1ds2-22. > End of message, stopping processing here. Please contact me

Processed: fixed 401585 in 4.1.1ds2-22

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.6 > fixed 401585 4.1.1ds2-22 Bug#401585: [m68k] ICE: in reload, at reload1.c:1079 Bug marked as fixed in version 4.1.1ds2-22. > End of message, stopping processing here. Please contact

Processed: notfound 373937 in 4.1.1-5

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.6 > notfound 373937 4.1.1-5 Bug#373937: libstdc++6: codecvt locale facet is broken Bug marked as not found in version 4.1.1-5. (By the way, this Bug is currently marked as done.) > End o

Bug#431608: Some statistics

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matthias Klose schrieb: > Torsten Marek writes: >> compiling parts of python-qt4 yields the following results: >> >> g++ 4.1.3: 13,71s user 0,26s sys >> gcc-snapshot: 1m59,38s user 0,69s sys > > thanks, the report is forwarded. Would it be possible to

Bug#431608: Some statistics

Torsten Marek writes: > compiling parts of python-qt4 yields the following results: > > g++ 4.1.3: 13,71s user 0,26s sys > gcc-snapshot: 1m59,38s user 0,69s sys thanks, the report is forwarded. Would it be possible to let sip-qt* to use g++-4.1 explicitely? -- To UNSUBSCRIBE, email to [EMAIL P

Bug#431608: Some statistics

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, compiling parts of python-qt4 yields the following results: g++ 4.1.3: 13,71s user 0,26s sys gcc-snapshot: 1m59,38s user 0,69s sys The preprocessed source code used above is rather large, please get it from here: http://diotavelli.net/files/sip

Bug#433539: GCC Spec File for Profiling

reopen 433539 thanks Hello! On Sat, Jul 14, 2007 at 10:49:13AM -0400, Michael Casadevall wrote: > After some trail and error as well as reading up how static binaries work > and the difference between gcrt0 and gcrt1, I was able to fix the profiling > bug with a GCC spec file: Are you sure yo

Processed: Re: GCC Spec File for Profiling

Processing commands for [EMAIL PROTECTED]: > reopen 433539 Bug#433539: gcc-4.1: profiling support on hurd 'reopen' may be inappropriate when a bug has been closed with a version; you may need to use 'found' to remove fixed versions. Bug reopened, originator not changed. > thanks Stopping processi

[bts-link] source package gcc-4.1

# # bts-link upstream status pull for source package gcc-4.1 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #390693 # * http://gcc.gnu.org/PR27880 # * remote status changed: REOPENED -> NEW usertags 390693 - status-R

Processed: [bts-link] source package gcc-4.1

Processing commands for [EMAIL PROTECTED]: > # > # bts-link upstream status pull for source package gcc-4.1 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). > # remote status report f

[bts-link] source package gcc-4.2

# # bts-link upstream status pull for source package gcc-4.2 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #425608 # * http://gcc.gnu.org/PR32072 # * remote status changed: (?) -> RESOLVED # * remote resolution cha

Processed: [bts-link] source package gcc-4.2

Processing commands for [EMAIL PROTECTED]: > # > # bts-link upstream status pull for source package gcc-4.2 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). > # remote status report f

Bug#406550: www.kaka.hw.hu

www.kaka.hw.hu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]