Read: You are approved
Hello Account #6883000, Your application was approved. You are eligible for $500,000 with a 3.7 % rate. Please confirm your information here: http://america-re-finances.com/2/index/mal/gwenda We look forward to hearing from you. Regards, calv caroljea, Senior Account Manager CFP Financial Group r*mv. -> http://america-re-finances.com/rem.php
Internal Compiler error initializing a struct
>Submitter-Id: net
>Originator:Ganesan Rajagopal
>Confidential: no
>Synopsis: Internal Compiler error initializing a struct
>Severity: serious
>Priority: medium
>Category: c
>Class: ice-on-legal-code
>Release: 3.3.5 (Debian 1:3.3.5-5) (Debian testing/unstable)
>Environment:
System: Linux grajagop-lnx 2.6.10-1-686 #1 Tue Jan 18 04:34:19 EST 2005 i686
GNU/Linux
Architecture: i686
host: i486-pc-linux-gnu
build: i486-pc-linux-gnu
target: i486-pc-linux-gnu
configured with: ../src/configure -v
--enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr
--mandir=/usr/share/man --infodir=/usr/share/info
--with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --with-system-zlib
--enable-nls --without-included-gettext --enable-__cxa_atexit
--enable-clocale=gnu --enable-debug --enable-java-gc=boehm
--enable-java-awt=xlib --enable-objc-gc i486-linux
>Description:
ice.cpp:8: internal compiler error: in tree_low_cst, at tree.c:3315
The problem happens with gcc-3.3 also.
>How-To-Repeat:
Compiling the following code reproduces the problem:
struct ice {
int a;
char *argv[];
} ice_array[] = {
{ 1, { "this causes internal compiler error", 0 } }
}
>Fix:
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RE: Question- Unknown checking account charges
I have just become aware that my credit card has been billed for months by your company. I have no idea what this is for since I have never been on your web site and I am in the middle of examining many such charges over the past six to eight months. It has become obvious to me that someone has gotten my computer information and has been charging various items and services to my card. I have has to change my debit card four times over the last several months, didn't do any good! I must find out what your charges are for and why my account has been charged for the last several months. Please contact me since this is an urgent matter. I am disabled and on a fixed income so must fix this problem as soon as possible. If there is a phone number that I could speak to someone directly, your providing it would be very helpful. My email address is: [EMAIL PROTECTED] An immediate response would be most appreciated, Carol Ann Kodalak
[Bug libgcj/19934] [4.0 regression] [alpha-linux] bootstrap error linking libgcj
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-15 17:24 --- The fix was applied so closing. -- What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED Target Milestone|--- |4.0.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19934 --- You are receiving this mail because: --- You reported the bug, or are watching the reporter. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[Bug libgcj/19934] [4.0 regression] [alpha-linux] bootstrap error linking libgcj
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-15 17:25 --- By the way here is the changelog: * Makefile.am (libgcj_la_SOURCES): Move all sources ... (libgcj0_convenience_la_SOURCES): ... here. (libgcj_la_LIBADD): Add libgcj0_convenience.la. (libgcj_la_DEPENDENCIES): Include libgcj_la_LIBADD. * Makefile.in: Regenerate. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19934 --- You are receiving this mail because: --- You reported the bug, or are watching the reporter. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#288191: marked as done (make-tpkg: source unpacking script bugged)
Your message dated Tue, 15 Feb 2005 21:01:20 +0200 (EET) with message-id <[EMAIL PROTECTED]> and subject line indeed fixed 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 responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 30 Dec 2004 18:54:58 + >From [EMAIL PROTECTED] Thu Dec 30 10:54:57 2004 Return-path: <[EMAIL PROTECTED]> Received: from korppi.suomicommunications.com [217.119.36.25] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Ck5Rp-0008E8-00; Thu, 30 Dec 2004 10:54:57 -0800 Received: from route.intranet (gw-5.suomicom.fi [217.30.187.5]) by korppi.suomicommunications.com (8.12.11/8.12.11/Debian-5) with ESMTP id iBUItRrL029858; Thu, 30 Dec 2004 20:55:27 +0200 Received: from omena.intranet ([172.16.1.14] ident=q-funk) by route.intranet with smtp (Exim 3.36 #1 (Debian)) id 1Ck5Rd-0003Vg-00; Thu, 30 Dec 2004 20:54:45 +0200 Received: by omena.intranet (sSMTP sendmail emulation); Thu, 30 Dec 2004 20:54:44 +0200 From: "Martin-Eric Racine" <[EMAIL PROTECTED]> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: make-tpkg: source unpacking script bugged X-Mailer: reportbug 3.2 Date: Thu, 30 Dec 2004 20:54:43 +0200 Message-Id: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: toolchain-source Version: 3.4-3 Severity: normal As seen below, there is a typo which could impair package operation: 8X- <[EMAIL PROTECTED]:/usr/src>$ cd /usr/src/; tpkg-make hppa-linux Target: hppa-linux Maintainer: Martin-Eric Racine Email-Address : [EMAIL PROTECTED] Toolchain : 3.4-3 binutils: 2.15 gcc : 3.4.3 gdb : toolchain-source-gdb not installed : # unpack gcc tarball mkdir stamps if [ -d /usr/src/gcc-hppa-linux-3.4.3/src ]; then \ echo >&2 "Source directory /usr/src/gcc-hppa-linux-3.4.3/src exists. Delete by hand"; \ false; \ fi rm -rf gcc-3.4.3 case gcc-3.4.3.tar.bz2 in \ *.bz2) tar -x --bzip2 -f gcc-3.4.3.tar.bz2;; \ *.gz) tar -x --gzip -f gcc-3.4.3.tar.bz2;; \ *) false; \ esac 8X- The case for *.gz should not just call --gzip, it should also wnat to unpack a filename ending in *.gz but here it tries to search for a possible *.bz2 even in this case. -- System Information: Debian Release: 3.1 Architecture: powerpc (ppc) Kernel: Linux 2.6.10-imac Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages toolchain-source depends on: ii devscripts2.8.5 Scripts to make the life of a Debi ii dpkg-awk 1.0.1 Gawk script to parse /var/lib/dpkg ii dpkg-cross1.20 Tools for cross compiling Debian p ii m41.4.2-1a macro processing language ii wget 1.9.1-8retrieves files from the web -- no debconf information --- Received: (at 288191-done) by bugs.debian.org; 15 Feb 2005 19:01:21 + >From [EMAIL PROTECTED] Tue Feb 15 11:01:21 2005 Return-path: <[EMAIL PROTECTED]> Received: from hal.fishpool.fi (hal.pp.fishpool.fi) [213.157.66.81] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1D17wn-00050X-00; Tue, 15 Feb 2005 11:01:21 -0800 Received: from q-funk (helo=localhost) by hal.pp.fishpool.fi with local-esmtp (Exim 3.35 #1 (Debian)) id 1D17wm-0005nw-00 for <[EMAIL PROTECTED]>; Tue, 15 Feb 2005 21:01:20 +0200 Date: Tue, 15 Feb 2005 21:01:20 +0200 (EET) From: =?iso-8859-1?Q?Martin-=C9ric_Racine?= <[EMAIL PROTECTED]> X-Sender: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: indeed fixed Message-ID: <[EMAIL PROTECTED]> X-Archive: encrypt MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: Martin-Eric Racine <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-2.0 required=4.0 tests=BAYES_01 autolearn=no
Bug#295457: gcc-snapshot: FTBFS on amd64: /usr/include/pthread.h:655: error: array type has incomplete element type
Package: gcc-snapshot Version: 20050212-1 Hi, The package failed to build with the following error on amd64: ./xgcc -B./ -B/usr/lib/gcc-snapshot/x86_64-linux-gnu/bin/ -isystem /usr/lib/gcc-snapshot/x86_64-linux-gnu/include -isystem /usr/lib/gcc-snapshot/x86_64-linux-gnu/sys-include -L/usr/src/gcc-snapshot-20050212/build/gcc/../ld -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I. -I../../src/gcc -I../../src/gcc/. -I../../src/gcc/../include -I../../src/gcc/../libcpp/include -fvisibility=hidden -DHIDE_EXPORTS -fexceptions -c ../../src/gcc/unwind-dw2.c -o libgcc/./unwind-dw2.o In file included from ../../src/gcc/gthr-posix.h:43, from ./gthr-default.h:1, from ../../src/gcc/gthr.h:114, from ../../src/gcc/unwind-dw2.c:42: /usr/include/pthread.h:655: error: array type has incomplete element type make[5]: *** [libgcc/./unwind-dw2.o] Error 1 /usr/include/pthread.h line 654-655 say: struct __jmp_buf_tag; extern int __sigsetjmp (struct __jmp_buf_tag __env[1], int __savemask) __THROW; Note that on amd64 we do not have linuxthread and only have NPTL so we have an other pthread.h than the other arches. struct __jmp_buf_tag is defined in and if I include that it builds fine. I don't see sigsetjmp being used in the preprocessed unwind-dw2.c file. The following 2 lines also generate the same error message: struct x; int y(struct x z[1]); Other versions of the compiler like 3.3 and 3.4 do not generate that error on functions that aren't used. I think what glibc is doing there is wrong, and if you agree, can you please clone and reassign this to glibc? Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#295326: gcc-3.3: Request the ability to write a static library archive
Justin Pryzby <[EMAIL PROTECTED]> writes:
> I'd love to be able to create a static library archive with a
> command like gcc -o libfoo.a -c {a,b,c,d}.c.
Why? What would be the advantage over using ar rc?
--
Falk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#295326: gcc-3.3: Request the ability to write a static library archive
On Wed, Feb 16, 2005 at 12:29:10AM +0100, Falk Hueffner wrote:
> Justin Pryzby <[EMAIL PROTECTED]> writes:
>
> > I'd love to be able to create a static library archive with a
> > command like gcc -o libfoo.a -c {a,b,c,d}.c.
>
> Why? What would be the advantage over using ar rc?
gcc acts as a frontend to cpp, g77, ld, etc, so it seems like it
should be able to do the same with ar. It would simplify the creation
of pic/nonpic libraries, as you could use one makefile rule
duplicated:
libfoo.so:
gcc -o $@ -shared $(CFLAGS) $(LDFLAGS) $(LDLIBS)
libfoo.a:
gcc -o $@ -fPIC $(CFLAGS) $(LDFLAGS) $(LDLIBS)
There's probably even a way to write that in one line.
Justin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#203212: A better economy for all
Today is a new day for your residence. With levels at their headline-making historic lows, our programs are better now than ever before. Even if you've recently closed on a property, now is the time to check your numbers. Our advisors are here to help you decide your options. In fact, did you know that a 30 year fixed program may not always be the best option? There are other ways to do it, and we would like to tell you about it. Find out what all your neighbors are talking about: http://www.mortslow.com/index.php?refid=vik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
