(Please CC me on replies as I am not subscribed to the list, thanks)
Hello,
I have a package (sdcc) which create a library called libutil.a during
its build process. Then this libraries is linked to several binaries
with -L.. -lutil.
There is also a libutil.a in /usr/lib provided libc6-dev. O
PLEASE REPLY TO [EMAIL PROTECTED] ONLY, *NOT* [EMAIL PROTECTED]
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11654
pinskia at physics dot uc dot edu changed:
What|Removed |Added
PLEASE REPLY TO [EMAIL PROTECTED] ONLY, *NOT* [EMAIL PROTECTED]
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11654
pinskia at physics dot uc dot edu changed:
What|Removed |Added
date||
--- Additional Comments From pinskia at physics dot uc dot edu 2003-07-24
02:33 ---
I can confirm this on the mainline (20030723).
emit_pending_bincls () at /home/gates/pinskia/src/gnu/gcc/src/gcc/dbxout.c:592
592 f = f->next;
(gdb) bt
PLEASE REPLY TO [EMAIL PROTECTED] ONLY, *NOT* [EMAIL PROTECTED]
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=323
pinskia at physics dot uc dot edu changed:
What|Removed |Added
PLEASE REPLY TO [EMAIL PROTECTED] ONLY, *NOT* [EMAIL PROTECTED]
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11654
Summary: gcc seg fault when using pre-compiled headers and -
gstabs
Product: gcc
Version: 3.4
Status: UNCONFIRMED
LAST_UPDATED: Tue Jul 22 06:27:21 UTC 2003
Native configuration is i386-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 Jul 22 22:33:04 UTC 2003
Native configuration is ia64-unknown-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/ext/packed2.C (test for excess errors)
FAIL: g++.dg/ext/pretty1.C scan-assembler top level
FAIL: g++.dg/ext/pretty2.C (test for excess err
LAST_UPDATED: Tue Jul 22 22:33:04 UTC 2003
Native configuration is i386-pc-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/eh/simd-2.C (test for excess errors)
WARNING: g++.dg/eh/simd-2.C compilation failed to produce executable
FAIL: g++.dg/ext/packed2.C (test for
LAST_UPDATED: Tue Jul 22 22:33:04 UTC 2003
Native configuration is hppa-unknown-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.dg/ext/packed2.C (test for excess errors)
FAIL: g++.dg/ext/pretty1.C scan-assembler top level
FAIL: g++.dg/ext/pretty2.C (test for excess err
>Submitter-Id: net
>Originator:M G Berberich
>Organization: FORWISS
>Confidential: no
>Synopsis: ice on __builtin_ia32_psllq
>Severity: serious
>Priority: low
>Category: c
>Class: ice-on-legal-code
>Release: 3.3 (Debian) (Debian testing/unstable)
>Environment:
System: Linux avaloon 2.
PLEASE REPLY TO [EMAIL PROTECTED] ONLY, *NOT* [EMAIL PROTECTED]
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10984
pinskia at physics dot uc dot edu changed:
What|Removed |Added
Processing commands for [EMAIL PROTECTED]:
> reassign 202587 colorgcc
Bug#202587: g++-3.3: g++ doesn't link libstdc++ by default
Bug reassigned from package `g++-3.3' to `colorgcc'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administr
reassign 202587 colorgcc
thanks
Alexander Kogan writes:
> Hi!
>
> I'm sorry, this bug is not in g++ but in colorgcc.
> Please, close this one and I'll post bug to colorgcc maintainer.
>
> --
> Alexander Kogan
> Institute of Applied Physics
> Russian Academy of Sciences
>
>
> --
> To UNSUBSCR
Your message dated Wed, 23 Jul 2003 07:30:10 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#202587: g++-3.3: g++ doesn't link libstdc++ by default
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
>Submitter-Id: net
>Originator:ken
>Organization: OpenOffice.org
>Confidential: no
>Synopsis: Failure to deal with using and private inheritance
>Severity: serious
>Priority:
>Category: c++
>Class: rejects-legal
>Release: 3.3.1 20030626 (Debian prerelease)
Hi!
I'm sorry, this bug is not in g++ but in colorgcc.
Please, close this one and I'll post bug to colorgcc maintainer.
--
Alexander Kogan
Institute of Applied Physics
Russian Academy of Sciences
Package: g++-3.3
Version: 1:3.3.1-0pre0
Severity: important
Hi!
g++ doesn't link libstdc++ by default.
[EMAIL PROTECTED]:~/tmp/3% cat main.cc
#include
int main()
{
std::cerr << std::endl;
}
[EMAIL PROTECTED]:~/tmp/3% g++ main.cc
/tmp/cc2z4Jba.o(.text+0x14): In function `main':
: undefined
Your message dated Wed, 23 Jul 2003 04:48:23 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#189365: fixed in gcc-3.3 1:3.3.1ds1-0rc1
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 i
Your message dated Wed, 23 Jul 2003 04:48:23 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#192296: fixed in gcc-3.3 1:3.3.1ds1-0rc1
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 i
Your message dated Wed, 23 Jul 2003 04:48:23 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#198269: fixed in gcc-3.3 1:3.3.1ds1-0rc1
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 i
Your message dated Wed, 23 Jul 2003 04:48:22 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#171699: fixed in gcc-3.3 1:3.3.1ds1-0rc1
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 i
Your message dated Wed, 23 Jul 2003 04:48:23 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#189059: fixed in gcc-3.3 1:3.3.1ds1-0rc1
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 i
Your message dated Wed, 23 Jul 2003 04:48:22 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#134197: fixed in gcc-3.3 1:3.3.1ds1-0rc1
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 i
Your message dated Wed, 23 Jul 2003 04:48:22 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#134197: fixed in gcc-3.3 1:3.3.1ds1-0rc1
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 i
Your message dated Wed, 23 Jul 2003 04:48:23 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#192296: fixed in gcc-3.3 1:3.3.1ds1-0rc1
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 i
Your message dated Wed, 23 Jul 2003 04:48:23 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#194391: fixed in gcc-3.3 1:3.3.1ds1-0rc1
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 i
Your message dated Wed, 23 Jul 2003 04:48:22 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#171699: fixed in gcc-3.3 1:3.3.1ds1-0rc1
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 i
Your message dated Wed, 23 Jul 2003 04:48:23 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#173475: fixed in gcc-3.3 1:3.3.1ds1-0rc1
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 i
Your message dated Wed, 23 Jul 2003 04:48:23 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#193830: fixed in gcc-3.3 1:3.3.1ds1-0rc1
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 i
Your message dated Wed, 23 Jul 2003 04:48:23 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#201882: fixed in gcc-3.3 1:3.3.1ds1-0rc1
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 i
Accepted:
cpp-3.3-doc_3.3.1-0rc1_all.deb
to pool/main/g/gcc-3.3/cpp-3.3-doc_3.3.1-0rc1_all.deb
cpp-3.3_3.3.1-0rc1_i386.deb
to pool/main/g/gcc-3.3/cpp-3.3_3.3.1-0rc1_i386.deb
fastjar_3.3.1-0rc1_i386.deb
to pool/main/g/gcc-3.3/fastjar_3.3.1-0rc1_i386.deb
fixincludes_3.3.1-0rc1_i386.deb
to po
Your message dated Wed, 23 Jul 2003 03:17:29 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#201823: fixed in gcc-snapshot 20030722-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 it i
Accepted:
gcc-snapshot_20030722-1.diff.gz
to pool/main/g/gcc-snapshot/gcc-snapshot_20030722-1.diff.gz
gcc-snapshot_20030722-1.dsc
to pool/main/g/gcc-snapshot/gcc-snapshot_20030722-1.dsc
gcc-snapshot_20030722-1_i386.deb
to pool/main/g/gcc-snapshot/gcc-snapshot_20030722-1_i386.deb
gcc-snapshot
Comments From pinskia at physics dot uc dot edu 2003-07-23
05:41 ---
I have reduced it down to 1113 lines for the mainline (20030723).
--- You are receiving this mail because: ---
You reported the bug, or are watching the reporter.
PLEASE REPLY TO [EMAIL PROTECTED] ONLY, *NOT* [EMAIL PROTECTED]
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11634
pinskia at physics dot uc dot edu changed:
What|Removed |Added
Attach
36 matches
Mail list logo
