Accepted:
cpp-3.3-doc_3.3.2-0pre1_all.deb
to pool/main/g/gcc-3.3/cpp-3.3-doc_3.3.2-0pre1_all.deb
cpp-3.3_3.3.2-0pre1_i386.deb
to pool/main/g/gcc-3.3/cpp-3.3_3.3.2-0pre1_i386.deb
fastjar_3.3.2-0pre1_i386.deb
to pool/main/g/gcc-3.3/fastjar_3.3.2-0pre1_i386.deb
fixincludes_3.3.2-0pre1_i386.deb
Processing commands for [EMAIL PROTECTED]:
reassign 204391 libstdc++5
Bug#204391: octave: Segfault on bad function name
Bug reassigned from package `octave' to `libstdc++5'.
quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
PLEASE REPLY TO [EMAIL PROTECTED] ONLY, *NOT* [EMAIL PROTECTED]
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11927
--- Additional Comments From pinskia at gcc dot gnu dot org 2003-08-15
13:52 ---
I cannot reproduce this on the mainline (20030814) on powerpc-apple-darwin6.6,
are you
PLEASE REPLY TO [EMAIL PROTECTED] ONLY, *NOT* [EMAIL PROTECTED]
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11928
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
PLEASE REPLY TO [EMAIL PROTECTED] ONLY, *NOT* [EMAIL PROTECTED]
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11927
schwab at suse dot de changed:
What|Removed |Added
Nathanael Nerode writes:
Looking at config.gcc the TARGET_CPU_DEFAULT is
overwritten by the target_alias. Looking at i386.c:1038 the cpu string
(tuning) is set to the TARGET_DEFAULT, but the arch string remains at
i386. the correct way to tune for i686 and use insn for i486 seems to
be this
Your message dated Fri, 15 Aug 2003 19:21:29 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#201691: gnat-3.3: gnatchop don't use correct gcc
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
Is oo built with the jdk1.4?
ld is not stripped, so you could get a stacktrace.
Jim Watson writes:
Package: gcc-3.3
Version: 1:3.3.1-1
Severity: important
-- System Information:
Debian Release: testing/unstable
Architecture: sparc
Kernel: Linux sun 2.4.18 #1 SMP Mon Jan 27 14:07:39
Christian,
does this still occur, when fontconfig (and maybe libfreetype) gets
compiled with gcc-3.3.1-1?
Matthias
PLEASE REPLY TO [EMAIL PROTECTED] ONLY, *NOT* [EMAIL PROTECTED]
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11931
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Processing commands for [EMAIL PROTECTED]:
submitter 172031 [EMAIL PROTECTED]
Bug#172031: [PR libgcj/9077] gij is unable to run some programs in the NBIO
test suite
Changed Bug submitter from Kenneth Pronovici [EMAIL PROTECTED] to [EMAIL
PROTECTED]
submitter 158387 [EMAIL PROTECTED]
PLEASE REPLY TO [EMAIL PROTECTED] ONLY, *NOT* [EMAIL PROTECTED]
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11931
--- Additional Comments From jsm at polyomino dot org dot uk 2003-08-15
18:51 ---
Subject: Re: unjustified warning for C89 code using
HUGE_VAL
On Fri, 15 Aug 2003,
On Fri, Aug 15, 2003 at 07:57:27PM +0200, Matthias Klose wrote:
Christian,
does this still occur, when fontconfig (and maybe libfreetype) gets
compiled with gcc-3.3.1-1?
The current fontconfig (2.2.1-1) is installing fine, kdeedu, the package
that had the problem, has been built inthe
reassign 204391 octave
thanks
schwab at suse dot de writes:
PLEASE REPLY TO [EMAIL PROTECTED] ONLY, *NOT* [EMAIL PROTECTED]
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11927
schwab at suse dot de changed:
What|Removed |Added
Processing commands for [EMAIL PROTECTED]:
reassign 204391 octave
Bug#204391: [PR 11927] [powerpc] wrong code, buffer overflow?
Bug reassigned from package `libstdc++5' to `octave'.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
Your message dated Fri, 15 Aug 2003 21:41:35 +0200
with message-id [EMAIL PROTECTED]
and subject line m68k fontconfig update?
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
PLEASE REPLY TO [EMAIL PROTECTED] ONLY, *NOT* [EMAIL PROTECTED]
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=323
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
On Sat, 16 Aug 2003 03:59, Matthias Klose wrote:
Is oo built with the jdk1.4?
yes
[EMAIL PROTECTED]:/usr/local/oo_src/instsetoo$ java -version
java version 1.4.1
Java(TM) 2 Runtime Environment, Standard Edition (build Blackdown-1.4.1-01)
Java HotSpot(TM) Client VM (build Blackdown-1.4.1-01, mixed
LAST_UPDATED: Tue Aug 12 08:34:50 UTC 2003
Native configuration is i486-pc-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/tls/init-2.C (test for excess errors)
XPASS: g++.other/init5.C Execution test
=== g++ Summary ===
# of expected passes
LAST_UPDATED: Tue Aug 12 08:34:50 UTC 2003
Native configuration is ia64-unknown-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/eh/forced1.C execution test
FAIL: g++.dg/tls/init-2.C (test for excess errors)
FAIL: g++.eh/terminate2.C Execution test
XPASS:
LAST_UPDATED: Tue Aug 12 08:34:50 UTC 2003
Native configuration is hppa-unknown-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/compat/break/bitfield7 x_tst.o compile
UNRESOLVED: g++.dg/compat/break/bitfield7 x_tst.o-y_tst.o link
UNRESOLVED:
LAST_UPDATED: Tue Aug 12 08:34:50 UTC 2003
Native configuration is ia64-unknown-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/eh/forced1.C execution test
FAIL: g++.dg/tls/init-2.C (test for excess errors)
FAIL: g++.eh/terminate2.C Execution test
XPASS:
Package: gcj-3.3
Version: 3.3.2-0pre1
Severity: normal
Please remove the gcj-debian-policy patch. /usr/share/java/repository
should no longer be added to the class path according to the latest
version of the Java policy
(http://www.debian.org/doc/packaging-manuals/java-policy/). In fact,
this
Your message dated Fri, 15 Aug 2003 17:32:35 -0500
with message-id [EMAIL PROTECTED]
and subject line closing stupid bug
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
Hi,
On Sat, 16 Aug 2003 03:59, Matthias Klose wrote:
ld is not stripped, so you could get a stacktrace.
sorry but i will need someone to tell me how to do this.
I can change the makefiles and I know how i can copy this command line from
the log into a shell file and make it run,
but i do
Accepted:
gcc-snapshot_20030815-1.diff.gz
to pool/main/g/gcc-snapshot/gcc-snapshot_20030815-1.diff.gz
gcc-snapshot_20030815-1.dsc
to pool/main/g/gcc-snapshot/gcc-snapshot_20030815-1.dsc
gcc-snapshot_20030815-1_i386.deb
to pool/main/g/gcc-snapshot/gcc-snapshot_20030815-1_i386.deb
Your message dated Fri, 15 Aug 2003 22:47:45 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#203593: fixed in gcc-snapshot 20030815-1
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
Your message dated Fri, 15 Aug 2003 22:47:45 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#205294: fixed in gcc-snapshot 20030815-1
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
28 matches
Mail list logo
