it`s julie here

2005-05-23 Thread Julie Bullard
My name is Julie :) Most of the time I like to do something I've never done before.. so I decided to have my first website featuring me (pics and videos). My girlfriends want to join me to on my website. -) Verify your age and connect to my webcam today -) Come I want to share my life

Grand Theft Rolex

2005-05-23 Thread Enid
Get the Finest Rolex Watch Replica ! We only sell premium watches. There's no battery in these replicas just like the real ones since they charge themselves as you move. The second hand moves JUST like the real ones, too. These original watches sell in stores for thousands of dollars. We

Re: proposing a gcc-3.3 upload to testing-proposed-updates

2005-05-23 Thread Steve Langasek
On Mon, May 23, 2005 at 01:19:36AM +0200, Matthias Klose wrote: On Sat, May 14, 2005 at 10:52:23PM +0200, Matthias Klose wrote: Content-Description: message body text I'm proposing the following updates for gcc-3.3 for testing: gcc-3.3 (1:3.3.5-13) testing-proposed-updates; urgency=low

Good news men! All your problems with small penis and poor erections will become history!!!^

2005-05-23 Thread Maximilian
Wish you could be better? http://www.terima.net/ss/ Penis Growth Patches are here! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#290438: acknowledged by developer

2005-05-23 Thread Kevin B. McCarty
Falk Hueffner wrote: Hi, this seems to be the well-known exces precision problem of the i386, so closing. Hello, I (mildly) protest the closing of this bug. The bug is not in fact fixed -- just well-known. Even though it is due to a CPU issue rather than a compiler problem, unoptimized

Rolex Replica Pamela

2005-05-23 Thread Sidney Clark
REPLICASONLINE - WE NEVER COMPROMISE ON QUALITY Rolex replica is our speciality We guarantee lowest prices and highest quality We are the Direct manufacturers. For top quality rolex watchs pleas visit: http://www.ultimatetimepiece4u.net eave mwk mailmen il [2 -- To UNSUBSCRIBE,

Processed: Re: Bug#309210: gcc-4.0 miscompile PARI/GP on x86

2005-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: tags 309210 - moreinfo Bug#309210: gcc-4.0 miscompile PARI/GP on x86 Tags were: moreinfo Tags removed: moreinfo thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator,

Bug#309210: gcc-4.0 miscompile PARI/GP on x86

2005-05-23 Thread Bill Allombert
tags 309210 - moreinfo thanks On Sun, May 22, 2005 at 07:05:38PM +0200, Falk Hueffner wrote: tags 309210 + moreinfo thanks Hi, how can this problem be reproduced? Easily: 1) download the tarball mentionned in the bug report and untar it 2) do CC=gcc-4.0 ./Configure 3) do make bench

Bug#290438: acknowledged by developer

2005-05-23 Thread Falk Hueffner
Kevin B. McCarty [EMAIL PROTECTED] writes: Falk Hueffner wrote: this seems to be the well-known exces precision problem of the i386, so closing. I (mildly) protest the closing of this bug. The bug is not in fact fixed -- just well-known. Even though it is due to a CPU issue rather than

[Bug target/21721] New: [4.0 regression] fails to assemble, Use of p0 is not valid in this context

2005-05-23 Thread doko at debian dot org
4.0 CVS 20050522 on ia64-linux, binutils-2.15, glibc-2.3.5, works with 3.3.6 and 3.4.4 releases $ gcc -O2 -g -c writet1.i writet1.c: In function 'load_enc': writet1.c:348: warning: pointer targets in assignment differ in signedness writet1.c: In function 't1_open_fontfile': writet1.c:1000:

[Bug target/21721] [4.0 regression] fails to assemble, Use of p0 is not valid in this context

2005-05-23 Thread doko at debian dot org
--- Additional Comments From doko at debian dot org 2005-05-23 16:48 --- Created an attachment (id=8951) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8951action=view) preprocessed source -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21721 --- You are receiving this mail

[Bug target/21721] [4.0 regression] fails to assemble, Use of p0 is not valid in this context

2005-05-23 Thread doko at debian dot org
--- Additional Comments From doko at debian dot org 2005-05-23 16:49 --- Created an attachment (id=8952) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8952action=view) assembler file -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21721 --- You are receiving this mail

[Bug target/21721] [4.0 regression] fails to assemble, Use of p0 is not valid in this context

2005-05-23 Thread doko at debian dot org
-- What|Removed |Added Known to fail||3.3.6 3.4.4 Known to work||4.0.1

[Bug target/21721] [4.0 regression] fails to assemble, Use of p0 is not valid in this context

2005-05-23 Thread schwab at suse dot de
-- What|Removed |Added CC||schwab at suse dot de Known to fail|3.3.6 3.4.4 |4.0.1 Known to work|4.0.1

[Bug target/21721] [4.0 regression] fails to assemble, Use of p0 is not valid in this context

2005-05-23 Thread schwab at suse dot de
--- Additional Comments From schwab at suse dot de 2005-05-23 17:21 --- Seems to be fixed in 4.1. -- What|Removed |Added Known to work|3.3.6 3.4.4

Processing of gcc-4.0_4.0.0-8_i386.changes

2005-05-23 Thread Archive Administrator
gcc-4.0_4.0.0-8_i386.changes uploaded successfully to localhost along with the files: gcc-4.0_4.0.0-8.dsc gcc-4.0_4.0.0-8.diff.gz cpp-4.0-doc_4.0.0-8_all.deb libgcj6-common_4.0.0-8_all.deb libgcj-common_4.0.0-8_all.deb libgcj6-src_4.0.0-8_all.deb libstdc++6-4.0-doc_4.0.0-8_all.deb

gcc-4.0_4.0.0-8_i386.changes is NEW

2005-05-23 Thread Debian Installer
cpp-4.0-doc_4.0.0-8_all.deb to pool/main/g/gcc-4.0/cpp-4.0-doc_4.0.0-8_all.deb cpp-4.0_4.0.0-8_i386.deb to pool/main/g/gcc-4.0/cpp-4.0_4.0.0-8_i386.deb fastjar_4.0.0-8_i386.deb to pool/main/g/gcc-4.0/fastjar_4.0.0-8_i386.deb fixincludes_4.0.0-8_i386.deb to

Fixed in upload of gcc-4.0 4.0.0-8 to experimental

2005-05-23 Thread Matthias Klose
tag 305690 + fixed-in-experimental tag 308948 + fixed-in-experimental quit This message was generated automatically in response to an upload to the experimental distribution. The .changes file follows. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 23 May 2005 01:56:28

Processed: Fixed in upload of gcc-4.0 4.0.0-8 to experimental

2005-05-23 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: tag 305690 + fixed-in-experimental Bug#305690: gcc-4.0: Please change the Build-Depends Tags were: fixed-in-experimental patch Tags added: fixed-in-experimental tag 308948 + fixed-in-experimental Bug#308948: gcc-4.0: Please add Ada support for the

gcc-4.0_4.0.0-8_i386.changes ACCEPTED

2005-05-23 Thread Debian Installer
Accepted: cpp-4.0-doc_4.0.0-8_all.deb to pool/main/g/gcc-4.0/cpp-4.0-doc_4.0.0-8_all.deb cpp-4.0_4.0.0-8_i386.deb to pool/main/g/gcc-4.0/cpp-4.0_4.0.0-8_i386.deb fastjar_4.0.0-8_i386.deb to pool/main/g/gcc-4.0/fastjar_4.0.0-8_i386.deb fixincludes_4.0.0-8_i386.deb to

Bug#251149: Bug #251149: gcc wrapper for sparc is chronically broken

2005-05-23 Thread David S . Miller
From: [EMAIL PROTECTED] Date: Mon, 23 May 2005 13:24:18 -0700 The other alternative is to touch /etc/disable_64_gcc Sure, but in the mail you are specifically replying to I stated: Also, /etc/disable_64_gcc is a workaround and should not be there by default as it is now, especially on your

Bug#251149: Bug #251149: gcc wrapper for sparc is chronically broken

2005-05-23 Thread bcollins
The other alternative is to touch /etc/disable_64_gcc On Sat, May 21, 2005 at 04:05:21PM -0700, David S. Miller wrote: On Sat, 21 May 2005 14:06:52 +0200 Falk Hueffner [EMAIL PROTECTED] wrote: this bug has been open for quite some time as important. Can some sparc people please comment on

Bug#251149: Bug #251149: gcc wrapper for sparc is chronically broken

2005-05-23 Thread Ben Collins
You're right. Didn't get down that far. As far as I'm concerned, the default 64-bit is the right thing. But it's hard to convince long time users that a machine that is 99% 32-bit userspace, should compile 64-bit binaries by default, when 99% of the time, those same people are going to want

Bug#251149: Bug #251149: gcc wrapper for sparc is chronically broken

2005-05-23 Thread Ben Collins
On Mon, May 23, 2005 at 07:27:22PM -0700, David S.Miller wrote: From: Ben Collins [EMAIL PROTECTED] Date: Mon, 23 May 2005 20:21:57 -0400 But (and this but is for David), that means users can't simply do apt-get source foo; cd foo-1.1; dpkg-buildpackage and get the same build they got

Bug#310524: New upstream version 3.4.4 fixes 163 bugs

2005-05-23 Thread FX
package: gcc-3.4 New upstream version 3.4.4 fixes 163 bugs. List of problems fixed in 3.4.4 are at: http://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVEDresolution=FIXEDtarget_milestone=3.4.4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble?