Bug#268991: gcj-3.4: simple program segfaults

2004-08-30 Thread David N. Welton
Package: gcj-3.4 Version: 3.4.1-4sarge1 Severity: important gcj-3.4 --main=hecl hecl.java @ashland [~/workshop/hecl] $ ./a.out Segmentation fault (core dumped) Maybe there is a bug in my code... import java.io.*; public class hecl { public static void main(String [] args) {

[Bug target/17180] [3.4 Regression] nearly all g77 tests fail on sparc-linux

2004-08-30 Thread ebotcazou at gcc dot gnu dot org
-- What|Removed |Added CC||ebotcazou at gcc dot gnu dot ||org

[Bug AWT/16121] gtk based awt peers: cast from pointer to integer of different size

2004-08-30 Thread fitzsim at redhat dot com
--- Additional Comments From fitzsim at redhat dot com 2004-08-30 18:41 --- If you still can't build the gui-branch, can you file a new report with details. I'm closing this, since the compiler warnings have been resolved. -- What|Removed |Added

Bug#269087: contains files in package libstdc++5-3.3-doc

2004-08-30 Thread Joe Drew
Package: libstdc++5 Version: 1:3.3.4-6sarge1.1 Severity: serious When upgrading from sarge to unstable, the following problem happens: Preparing to replace libstdc++5 1:3.3.4-6sarge1.1 (using /libstdc++5_1%3a3.3.4-9_i386.deb) ... Unpacking replacement libstdc++5 ... dpkg: error processing

Bug#268929: libffi2-dev: [amd64] Wrong libdir='/usr/lib./lib64'

2004-08-30 Thread Goswin von Brederlow
Hi, welcome to our little rolercoaster. Lowering the priority again. Steve Langasek verified this on sparc and said that the sparc sablevm package was build with the broken libffi2-dev package. But unlike the previous builds with '/usr/lib/.' or '/usr/lib/../lib64' this time libtool did not mess

Bug#268771: marked as done (package libstdc++5-3.3-dev upgrade bug)

2004-08-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Aug 2004 12:47:24 -0700 with message-id [EMAIL PROTECTED] and subject line Cannot upgrade gcc, g++ and libstd++5 - conflicting files in packages has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#268770: marked as done (package libg2c0 upgrade bug)

2004-08-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Aug 2004 12:47:24 -0700 with message-id [EMAIL PROTECTED] and subject line Cannot upgrade gcc, g++ and libstd++5 - conflicting files in packages has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#268769: marked as done (package gcc-3.3 upgrade bug)

2004-08-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Aug 2004 12:47:24 -0700 with message-id [EMAIL PROTECTED] and subject line Cannot upgrade gcc, g++ and libstd++5 - conflicting files in packages has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#268700: marked as done (same files in gcc-3.3 and gcc-3.3-base)

2004-08-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Aug 2004 12:47:24 -0700 with message-id [EMAIL PROTECTED] and subject line Cannot upgrade gcc, g++ and libstd++5 - conflicting files in packages has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#268653: marked as done (libg2c0: package upgrade fails)

2004-08-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Aug 2004 12:47:24 -0700 with message-id [EMAIL PROTECTED] and subject line Cannot upgrade gcc, g++ and libstd++5 - conflicting files in packages has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#268647: marked as done (Package overwrite file in other package.)

2004-08-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Aug 2004 12:47:24 -0700 with message-id [EMAIL PROTECTED] and subject line Cannot upgrade gcc, g++ and libstd++5 - conflicting files in packages has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#268644: marked as done (File exist in other package.)

2004-08-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Aug 2004 12:47:24 -0700 with message-id [EMAIL PROTECTED] and subject line Cannot upgrade gcc, g++ and libstd++5 - conflicting files in packages has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#268641: marked as done (Files placed at gcc place.)

2004-08-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Aug 2004 12:47:24 -0700 with message-id [EMAIL PROTECTED] and subject line Cannot upgrade gcc, g++ and libstd++5 - conflicting files in packages has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#268476: marked as done (gcc-3.3-base (1:3.3.4-6sarge1.1) conflicts with others gcc-3.3-... packages)

2004-08-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Aug 2004 12:47:24 -0700 with message-id [EMAIL PROTECTED] and subject line Cannot upgrade gcc, g++ and libstd++5 - conflicting files in packages has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#268338: marked as done (Cannot upgrade gcc, g++ and libstd++5 - conflicting files in packages.)

2004-08-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Aug 2004 12:47:24 -0700 with message-id [EMAIL PROTECTED] and subject line Cannot upgrade gcc, g++ and libstd++5 - conflicting files in packages has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#268806: marked as done (gcc package doesn't install)

2004-08-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Aug 2004 12:47:24 -0700 with message-id [EMAIL PROTECTED] and subject line Cannot upgrade gcc, g++ and libstd++5 - conflicting files in packages has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#268768: marked as done (package g++-3.3 upgrade bug)

2004-08-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Aug 2004 12:47:24 -0700 with message-id [EMAIL PROTECTED] and subject line Cannot upgrade gcc, g++ and libstd++5 - conflicting files in packages has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#268577: marked as done (Installation errors for gcc-3.3 (1:3.3.4-6sarge1.1) packages in Debian testing)

2004-08-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Aug 2004 12:47:24 -0700 with message-id [EMAIL PROTECTED] and subject line Cannot upgrade gcc, g++ and libstd++5 - conflicting files in packages has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#268473: marked as done (g++-3.3 will not update to 1:3.3.4-6sarge1.1)

2004-08-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Aug 2004 12:47:24 -0700 with message-id [EMAIL PROTECTED] and subject line Cannot upgrade gcc, g++ and libstd++5 - conflicting files in packages has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#268581: marked as done (libstdc++5: upgrade of GCC and G++ packages requires --force-overwrite both on sarge1.1 and Sid)

2004-08-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Aug 2004 12:47:24 -0700 with message-id [EMAIL PROTECTED] and subject line Cannot upgrade gcc, g++ and libstd++5 - conflicting files in packages has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#268645: marked as done (Try to overwrite file in other package.)

2004-08-30 Thread Debian Bug Tracking System
Your message dated Mon, 30 Aug 2004 12:47:24 -0700 with message-id [EMAIL PROTECTED] and subject line Cannot upgrade gcc, g++ and libstd++5 - conflicting files in packages has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

updates

2004-08-30 Thread lacko
Adobe Acrobat 6.0 Professional - 100 Adobe Acrobat 6.0 Professional - 100 Windows 2000 Server - 50 Adobe Photoshop cs - 80 Microsoft Office XP Professional - 100 Adobe InDesign CS - 100 Corel Draw Graphics Suite 11 - 120 Borland Delphi 7 Professional - 70 Microsoft Office XP Professional - 100