--- Additional Comments From ebotcazou at gcc dot gnu dot org 2004-08-31
04:24 ---
Investigating.
--
What|Removed |Added
CC|ebotcazou at gcc dot gnu dot|
--- Additional Comments From ebotcazou at gcc dot gnu dot org 2004-08-31
04:23 ---
Confirmed on SPARC/Solaris 32-bit too.
--
What|Removed |Added
Status|UNCONFIRM
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
M
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
Processing commands for [EMAIL PROTECTED]:
> severity 268929 important
Bug#268929: libffi2-dev: [amd64] Wrong libdir='/usr/lib./lib64'
Severity set to `important'.
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(adm
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
/va
--- 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
---
--
What|Removed |Added
CC||ebotcazou at gcc dot gnu dot
||org
http://gcc.gnu.org/bugzilla/
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) {
StringBuf
26 matches
Mail list logo
