Matthias Klose [EMAIL PROTECTED] writes:
Please could you point me to the invariant-section material? Tried to
find it, but maybe it's too late here in Europe and I'm not awake :-(
cd gcc/doc
grep Invariant *.texi
cpp.texi:This manual contains no Invariant Sections. The Front-Cover Texts are
Martin v. =?iso-8859-15?q?L=F6wis?= writes:
Matthias Klose [EMAIL PROTECTED] writes:
Please could you point me to the invariant-section material? Tried to
find it, but maybe it's too late here in Europe and I'm not awake :-(
cd gcc/doc
grep Invariant *.texi
cpp.texi:This manual
Package: g++-3.3
Version: 1:3.3-2
Severity: normal
g++-3.3 fails to compile the following code (which would compile with
previous g++ versions):
$ cat in_class_class.cc
class Foo {
template class T struct InFoo;
};
template
struct Foo::InFooint {
// ...
};
$ g++ -c in_class_class.cc
Package: libgcc1
Version: 1:3.2.3-0pre6
Severity: critical
actions taken:
apt-get remove jade
this required, at this time, the installation / upgrade of libgcc1
and the installation / upgrade of tetex.
gcc 3.3 and cpp 3.3 was NOT required as part of that installation / upgrade.
once
Number: 10858 Category: c++ Synopsis: bogus compiler failure while
compiling Boost.Python Confidential: no Severity: serious Priority:
medium Responsible: unassigned State: open Class: rejects-legal
Submitter-Id: net Arrival-Date: Mon May 19 11:56:00 UTC 2003
Closed-Date: Last-Modified:
On Mon, 2003-05-19 at 01:39, Martin v. Löwis wrote:
cpp.texi:This manual contains no Invariant Sections. The Front-Cover Texts
are
[...]
So cpp.texi is free documentation; the others contain invariant sections.
-legal isn't too happy with front or back cover texts, either.
Never seen this upgrade behaviour. Was libgcc1 installed before
libstdc++5? If not, please could you explictely install libgcc1 and
then libstdc++5?
Adding a pre-dpends on libgcc1 in libstdc++5 may help here, but this
would not catch binaries depending on new symbols in libgcc1, and not
depending
hi,
i've read the web page about how to upgrade to the 3.3 via cvs.
did that, it worked fine, ( i think).
i'm looking for a web page that shows what to do afterwards in order to
finish the upgrade process.
regards,
michael
Processing commands for [EMAIL PROTECTED]:
reassign 192296 octave-forge
Bug#192296: octave-forge_2003.04.28-3(hppa/unstable):
Bug reassigned from package `gcc-3.2' to `octave-forge'.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
9 matches
Mail list logo
