> Randolph Chung writes: > > In reference to a message from Matthias Klose, dated Mar 01: > > > Matthias Klose writes: > > > > AFAIK the transition from 3.2 to 3.3 requires recompilation of C++ > > > > code due to the changed exception handling (now DWARF2 based). As > > > > libstdc++ in 3.2 and 3.2 have the same soname, how to handle it? > > > > Currently 3.2 is in unstable only. Would you want to start the > > > > recompilation before 3.2 based binaries go to testing? > > > > > > > > The packaging for 3.3 can be found in the Debian CVS. > > > > > > You can get test packages from > > > http://ftp-master.debian.org/~doko/gcc-3.3/ > > > > well.... this is not looking good. after installing these in a freshly > > built sarge chroot, all c++ programs stop working (well, i've only tried > > two -- apt and fakeroot) > > You can find updated packages at > http://ftp-master.debian.org/~doko/gcc-3.3/hppa/ > checked building bash (fakeroot) and upgrading an unstable chroot (apt). > > > (btw, small packaging detail, but the libstdc++*-dev package above > > cannot be installed cleanly because it overwrites things in the current > > 3.2 package) > > There is still one conflict for libstdc++5-dev (<= 1:3.2.3-0pre3), so > please install libstdc++5-dev (1:3.2.3-0pre4) first.
Did you configure 3.3 using "--enable-sjlj-exceptions=yes"? That way the 3.3 C++ library should be compatible with the previous 3.3 library. The switch to dwarf2 can be delayed until the next debian release. Dave -- J. David Anglin [EMAIL PROTECTED] National Research Council of Canada (613) 990-0752 (FAX: 952-6605)