--- Comment #73 from pcarlini at suse dot de 2005-10-24 09:14 ---
(In reply to comment #72)
why is it pointless? just because it doesn't work on some target architectures
doesn't mean it doesn't work on most main archs.
Are you really, really, sure that without patching the
Package: gcc-4.0
Version: 4.0.2-2
Severity: minor
In $(man gcc), I the following two problems:
-Wunused-function
...
non\-inline static function is unused. This warning is enabled by
^^^
-M Instead of outputting the result of preprocessing, output a rule
Package: java-gcj-compat
Version: 1.0.41-1
Severity: grave
Justification: renders package unusable
Hi,
trying /usr/lib/jvm/java-gcj/bin/java gives me:
error spawning gij
Running with strace shows that the java binary assumes an
unversioned gij binary in /usr/bin
execve(/usr/bin/gij, [./java],
Your message dated Mon, 24 Oct 2005 15:17:26 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#327254: fixed in gcc-4.0 4.0.2-3
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 message dated Mon, 24 Oct 2005 15:17:26 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#333951: fixed in gcc-4.0 4.0.2-3
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 message dated Mon, 24 Oct 2005 15:17:26 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#333954: fixed in gcc-4.0 4.0.2-3
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 message dated Mon, 24 Oct 2005 15:17:26 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#333952: fixed in gcc-4.0 4.0.2-3
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 message dated Mon, 24 Oct 2005 15:17:26 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#334296: fixed in gcc-4.0 4.0.2-3
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
gcc-4.0_4.0.2-3_i386.changes uploaded successfully to localhost
along with the files:
gcc-4.0_4.0.2-3.dsc
gcc-4.0_4.0.2-3.diff.gz
cpp-4.0-doc_4.0.2-3_all.deb
libgcj6-common_4.0.2-3_all.deb
libgcj-common_4.0.2-3_all.deb
libgcj6-src_4.0.2-3_all.deb
libstdc++6-4.0-doc_4.0.2-3_all.deb
Your message dated Mon, 24 Oct 2005 15:17:26 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#325545: fixed in gcc-4.0 4.0.2-3
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 message dated Mon, 24 Oct 2005 15:17:26 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#329840: fixed in gcc-4.0 4.0.2-3
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 message dated Mon, 24 Oct 2005 15:17:26 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#330099: fixed in gcc-4.0 4.0.2-3
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 message dated Mon, 24 Oct 2005 15:17:26 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#318932: fixed in gcc-4.0 4.0.2-3
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
gcc-4.0_4.0.2-3_powerpc.changes uploaded successfully to localhost
along with the files:
gcc-4.0-base_4.0.2-3_powerpc.deb
libgcc1_4.0.2-3_powerpc.deb
lib64gcc1_4.0.2-3_powerpc.deb
cpp-4.0_4.0.2-3_powerpc.deb
protoize_4.0.2-3_powerpc.deb
fixincludes_4.0.2-3_powerpc.deb
Accepted:
cpp-4.0-doc_4.0.2-3_all.deb
to pool/main/g/gcc-4.0/cpp-4.0-doc_4.0.2-3_all.deb
cpp-4.0_4.0.2-3_i386.deb
to pool/main/g/gcc-4.0/cpp-4.0_4.0.2-3_i386.deb
fastjar_4.0.2-3_i386.deb
to pool/main/g/gcc-4.0/fastjar_4.0.2-3_i386.deb
fixincludes_4.0.2-3_i386.deb
to
Accepted:
cpp-4.0_4.0.2-3_powerpc.deb
to pool/main/g/gcc-4.0/cpp-4.0_4.0.2-3_powerpc.deb
fastjar_4.0.2-3_powerpc.deb
to pool/main/g/gcc-4.0/fastjar_4.0.2-3_powerpc.deb
fixincludes_4.0.2-3_powerpc.deb
to pool/main/g/gcc-4.0/fixincludes_4.0.2-3_powerpc.deb
g++-4.0_4.0.2-3_powerpc.deb
to
Package: java-gcj-compat-dev
Version: 1.0.41-1
Severity: important
s/ecj-boostrap-gcj/ecj-bootstrap-gcj/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
java-gcj-compat_1.0.41-2_i386.changes uploaded successfully to localhost
along with the files:
java-gcj-compat_1.0.41-2.dsc
java-gcj-compat_1.0.41-2.diff.gz
java-gcj-compat-dev_1.0.41-2_i386.deb
java-gcj-compat_1.0.41-2_i386.deb
Greetings,
Your Debian queue daemon
--
To
Your message dated Mon, 24 Oct 2005 17:02:07 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#335570: fixed in java-gcj-compat 1.0.41-2
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
Your message dated Mon, 24 Oct 2005 17:02:07 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#335610: fixed in java-gcj-compat 1.0.41-2
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
Accepted:
java-gcj-compat-dev_1.0.41-2_i386.deb
to pool/main/j/java-gcj-compat/java-gcj-compat-dev_1.0.41-2_i386.deb
java-gcj-compat_1.0.41-2.diff.gz
to pool/main/j/java-gcj-compat/java-gcj-compat_1.0.41-2.diff.gz
java-gcj-compat_1.0.41-2.dsc
to
=?GB2312?B?qJZulXSCq4NUg0ODZ4F6?=
To: [EMAIL PROTECTED]
Content-Type: text/plain;charset=EUC
Reply-To: [EMAIL PROTECTED]
Date: Tue, 25 Oct 2005 11:24:37 +0800
X-Priority: 3
X-Mailer: FoxMail 4.0 beta 2 [cn]
[PR]
22 matches
Mail list logo
