Re: C++ library broken

Daniel Jacobowitz [EMAIL PROTECTED] writes: On Wed, Nov 13, 2002 at 06:41:24PM -0800, Brian Nelson wrote: Alex Romosan [EMAIL PROTECTED] writes: Brian Nelson [EMAIL PROTECTED] writes: apt-get: error while loading shared libraries: libstdc++-libc6.2-2.so.3: cannot open shared object

Processed: reassign 168871 to perl, gcc

Processing commands for [EMAIL PROTECTED]: reassign 168871 perl, gcc Bug#168871: mhonarc segfaults on attached mbox; upstream says it's not theirs :) Bug reassigned from package `mhonarc' to `perl, gcc'. End of message, stopping processing here. Please contact me if you need assistance.

gcc-2.95_2.95.4.ds14-15_i386.changes ACCEPTED

Accepted: chill-2.95_2.95.4-15_i386.deb to pool/main/g/gcc-2.95/chill-2.95_2.95.4-15_i386.deb cpp-2.95-doc_2.95.4-15_all.deb to pool/main/g/gcc-2.95/cpp-2.95-doc_2.95.4-15_all.deb cpp-2.95_2.95.4-15_i386.deb to pool/main/g/gcc-2.95/cpp-2.95_2.95.4-15_i386.deb g++-2.95_2.95.4-15_i386.deb

Bug#169033: marked as done (libstdc++2.10-glibc2.2 is breakint apt-get, reportbug and probably lots of other things)

Your message dated Thu, 14 Nov 2002 05:02:32 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#168991: fixed in gcc-2.95 2.95.4.ds14-15 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

Bug#168991: marked as done (libstdc++2.10-glibc2.2: latest unstable upgrade has broken symlink)

Your message dated Thu, 14 Nov 2002 05:02:32 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#168991: fixed in gcc-2.95 2.95.4.ds14-15 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

Bug#168998: marked as done (libstdc++2.10-glibc2.2: Upgrading totally hoses system)

Your message dated Thu, 14 Nov 2002 05:02:32 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#168991: fixed in gcc-2.95 2.95.4.ds14-15 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

Bug#169013: marked as done (base: typo in libstdc++libc6.2-2.so.3 library name breaks dependencies)

Your message dated Thu, 14 Nov 2002 05:02:32 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#168991: fixed in gcc-2.95 2.95.4.ds14-15 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

Bug#169032: marked as done (libstdc++2.10-glibc2.2: C++ library naming breaks apt-get)

Your message dated Thu, 14 Nov 2002 05:02:32 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#168991: fixed in gcc-2.95 2.95.4.ds14-15 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

Bug#169036: marked as done (libstdc++2.10-glibc2.2: Provides wrong symlink; breaks apt-get)

Your message dated Thu, 14 Nov 2002 05:02:32 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#168991: fixed in gcc-2.95 2.95.4.ds14-15 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

Bug#148529: ada/6911: Sin and Cos returns bad result or exception

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-traildatabase=gccpr=6911 Hi I have'nt a clue where this mail is going so bare with me (I'm a newbie to gcc ;-) I've noticed the same bug with 3.1 and 3.2 on RedHat PC-Intel. I couldn't find a solution in the database so I'm posting my

[Fwd: Fix for serious bug in glibc packages (libstdc++-libc6.2-2.so.3)]

I think this should probably have gone to you folks... -- When you get to the heart, use a knife and fork. - From instructions on how to eat an artichoke. ---BeginMessage--- Hello. I just did an apt-get upgrade, which updated libstdc++ and a bunch of other packages. After the upgrade apt-get

Bug#169101: cluttered .diff.gz

Package: gcc-3.2 Version: 3.2.1ds5-0pre6 Severity: minor I was just reviewing the .diff.gz to prove a point (Debian diverges significantly from upstream! Does not! Does too! Does not!) and I noticed several files were present in CVS conflict version; ie: +++

libstdc++glibc2.2 broken in Sid

Hi, Seems the libstdc++glibc2.2 in Sid is broken atm, there seems to be a typo in the library name? lrwxrwxrwx1 root root 23 Nov 14 21:47 /usr/lib/libstdc++-libc6.2-2.so.3 - libstdc++libc6.2-2.so.3 Note the dash in the first filename, it's not in the library filename

Processed: Re: Bug#169139: Problem with libstdc++-libc6 [ with how-to-fix ]

Processing commands for [EMAIL PROTECTED]: reassign 169139 gcc-2.95 Bug#169139: Problem with libstdc++-libc6 [ with how-to-fix ] Bug reassigned from package `libstdc++-libc' to `gcc-2.95'. reassign 169140 gcc-2.95 Bug#169140: Problem with libstdc++-libc6 [ with how-to-fix ] Bug reassigned from

Bug#169161: libstdc++5: Questionable type usage in mangled names

Package: libstdc++5 Version: 1:3.2.1-0pre6 Severity: normal Tags: upstream Underlying types are used when creating the mangled name of symbols in C++. In libstdc++, many symbols contains the type mbstate_t. As encoded in the mangled name, the underlying type, __mbstate_t is used. When unmangled,

Processed: Re: Bug#169161: libstdc++5: Questionable type usage in mangled names

Processing commands for [EMAIL PROTECTED]: forwarded 169161 [EMAIL PROTECTED] Bug#169161: libstdc++5: Questionable type usage in mangled names Noted your statement that Bug has been forwarded to [EMAIL PROTECTED] thanks Stopping processing here. Please contact me if you need assistance.

Bug#169161: libstdc++5: Questionable type usage in mangled names

forwarded 169161 [EMAIL PROTECTED] thanks This should presumably be reported to GCC rather than to us... Libstdc++ folks, please maintain the CC's. Any thoughts? On Thu, Nov 14, 2002 at 09:13:37PM -0500, Stuart Anderson wrote: Package: libstdc++5 Version: 1:3.2.1-0pre6 Severity: normal