Bug#209152: is it you? kellie here

2007-02-10 Thread kellie
Hi It`s kellie again. Will you ever contact me? I made those nude pictures especially for you and I wont write to you again! If you wanna see them just drop me a line at: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PRO

[Bug rtl-optimization/29329] [4.1 regression] internal consistency failure

2007-02-10 Thread ebotcazou at gcc dot gnu dot org
-- Bug 29329 depends on bug 25514, which changed state. Bug 25514 Summary: [4.0 regression] internal consistency failure http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25514 What|Old Value |New Value

Re: D support (gdc) and gdc -- D front end for GCC (Was: reassign to gcc-4.1)

2007-02-10 Thread Matthias Klose
Ludovic Brenta writes: > [EMAIL PROTECTED] (Debian Bug Tracking System) writes: > > Processing commands for [EMAIL PROTECTED]: > > > >> reassign 312367 gcc-4.1 > > Bug#312367: gcc-4.0: D support (gdc) > > Bug#317983: RFP: gdc -- D Front End for GCC > > Bug reassigned from package `gcc-4.0' to `gcc-

Re: D support (gdc) and gdc -- D front end for GCC (Was: reassign to gcc-4.1)

2007-02-10 Thread Ludovic Brenta
[EMAIL PROTECTED] (Debian Bug Tracking System) writes: > Processing commands for [EMAIL PROTECTED]: > >> reassign 312367 gcc-4.1 > Bug#312367: gcc-4.0: D support (gdc) > Bug#317983: RFP: gdc -- D Front End for GCC > Bug reassigned from package `gcc-4.0' to `gcc-4.1'. Doesn't that assume that we'll

Bug#329845: marked as done (csound: FTBFS on ARM)

2007-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2007 14:25:29 +0100 with message-id <[EMAIL PROTECTED]> and subject line csound build failure fixed in gcc-4.1 has caused the attached Bug report 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 y

Bug#357900: marked as done (gcc-4.0: Please detect and warn about 2 argument mode() called with O_CREAT)

2007-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2007 14:00:32 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#357900: gcc-4.0: Please detect and warn about 2 argument mode() called with O_CREAT has caused the attached Bug report to be marked as done. This means that you claim that the problem has b

Processed: Re: Bug#357900: gcc-4.0: Please detect and warn about 2 argument mode() called with O_CREAT

2007-02-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > tags 357900 + wontfix Bug#357900: gcc-4.0: Please detect and warn about 2 argument mode() called with O_CREAT Tags were: upstream Tags added: wontfix > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking sy

Processed: reassign gcc report

2007-02-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > reassign 355621 gcc-4.1 Bug#355621: gcc-4.0: hidden symbol `__gcov_init' is referenced by DSO Bug reassigned from package `gcc-4.0' to `gcc-4.1'. > found 355621 4.1.1-9 Bug#355621: gcc-4.0: hidden symbol `__gcov_init' is referenced by DSO Bug marked as

Processed: Re: gcc-4.0: arm-linux cross build mistakenly invokes native assembler

2007-02-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > tags 376427 + wontfix Bug#376427: gcc-4.0: arm-linux cross build mistakenly invokes native assembler There were no tags set. Tags added: wontfix > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system a

Processed: reassign to gcc-4.1

2007-02-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > reassign 312367 gcc-4.1 Bug#312367: gcc-4.0: D support (gdc) Bug#317983: RFP: gdc -- D Front End for GCC Bug reassigned from package `gcc-4.0' to `gcc-4.1'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug track

Bug#366204: marked as done (gcc-4.0: dangling symlinks)

2007-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2007 13:47:59 +0100 with message-id <[EMAIL PROTECTED]> and subject line gcc-4.0: dangling symlinks has caused the attached Bug report 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 respons

Bug#376427: marked as done (gcc-4.0: arm-linux cross build mistakenly invokes native assembler)

2007-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2007 14:10:26 +0100 with message-id <[EMAIL PROTECTED]> and subject line gcc-4.0: arm-linux cross build mistakenly invokes native assembler has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#349268: marked as done (gcc-4.0: ICE building clisp on amd64.)

2007-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2007 14:13:31 +0100 with message-id <[EMAIL PROTECTED]> and subject line gcc-4.0: ICE building clisp on amd64. has caused the attached Bug report 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

Bug#378628: marked as done (gcc-4.0: GCC 4.0.3 miscompile debugging information)

2007-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2007 13:44:22 +0100 with message-id <[EMAIL PROTECTED]> and subject line gcc-4.0: GCC 4.0.3 miscompile debugging information has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the ca

Processed: Re: Bug#376468: Should use xargs --no-run-if-empty

2007-02-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > tags 376468 + wontfix Bug#376468: Should use xargs --no-run-if-empty There were no tags set. Tags added: wontfix > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Deb

Bug#325739: marked as done (gcc-4.0: Segfault with gcc4 (and above) when using LD_PRELOAD)

2007-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2007 13:34:47 +0100 with message-id <[EMAIL PROTECTED]> and subject line Segfault with gcc4 (and above) when using LD_PRELOAD has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the c

Processed (with 1 errors): forwarded gcc report

2007-02-10 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > forwarded 345587 http://gcc.gnu.org/PR28314 Bug#345587: [PR28314] cpp: x86/powerpc inconsistency for the __linux macro Noted your statement that Bug has been forwarded to http://gcc.gnu.org/PR28314. > reassign 345587 cpp Bug#345587: [PR28314] cpp: x86/

Bug#376468: marked as done (Should use xargs --no-run-if-empty)

2007-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2007 13:49:43 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#376468: Should use xargs --no-run-if-empty has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it