On Sat, 5 Dec 1998, Peter Berlau wrote:
> Does the 2.8_2.90 not conflict with the 2.9_2.
> or can it coexistent and,
They coexist fine.
> who and from where did You install the
> g++ compiler and the gcc compiler
> assuming from `slink', than versions are
> egcs-1.1.1 pre-release #3 ??
> gcc
On Sat, Dec 05, 1998 at 03:10:44AM +0200, Janne Lof wrote:
>
> Problem solved!
>
> I upgraded to following packages and the problem went away.
>
> libstdc++2.8_2.90.29-2.deb
> libstdc++2.9_2.91.60-1_i386.deb
> libstdc++2.9-dev_2.91.60-1_i386.deb
>
Does the 2.8_2.90 not conflict with the 2.9_2.
Problem solved!
I upgraded to following packages and the problem went away.
libstdc++2.8_2.90.29-2.deb
libstdc++2.9_2.91.60-1_i386.deb
libstdc++2.9-dev_2.91.60-1_i386.deb
--
Janne Löf
Here's something someone posted a few days ago
--
Folks,
If you are getting the error
/usr/lib/libstdc++-libc6.0-1.so.2: undefined symbol: __register_frame_info
after upgrading to slink, please go through the mail below. Mitch's
solution worked for me.
I just updated debian (slink) via dselect, there was about 40MB of updated
stuff and I did not look very carefully what got upgraded (I know I should
have been more careful).
Now I get this error with many programs (with dselect for example):
dselect: error in loading shared libraries
/usr/lib/l
5 matches
Mail list logo