Re: __register_frame_info problem resolved?
J.H.M. Dassen \(Ray\) writes:
> On Tue, Dec 01, 1998 at 10:57:58 -0500, Ossama Othman wrote:
> > > That's a bug indeed:
> > > penguin ray 16:35 /tmp > dpkg --contents libstdc++2.9-dev_2.91.59-2_i386.deb | grep '\.so'
> > > lrwxrwxrwx root/root 0 1998-11-30 01:51 usr/lib/gcc-lib/i486-linux/egcs-2.91.59/libstdc++.so -> ../../../libstdc++-libc6.0-1.so.2
> > > This link isn't in ld's default search path.
>
> I just checked (g++ -v simple.cc), and g++ passes the appropriate -L to ld,
> so it works.
>
> > > As a workaround,
> > > cd /usr/lib ; ln -s libstdc++-libc6.0-1.so.2 libstdc++.so
> > >
> > > Matthias, can you fix this please?
>
> My apologies. It works.
Yes, because libstdc++2.9-dev_2.91.59-2 depends on g++-2.91.x and
this compiler searches in the correct directory. That dependency was
missing in 2.91.59-1.
> > Upgrading to the latest egcs C++ packages in Incoming (2.91.59-2)
> > corrected my "ld unable to find -lstdc++" problem, although the link for
> > libstdc++.so you mentioned in your e-mail isn't in /usr/lib. Should it be
> > there?
>
> It would be best if it were in there. Most build processes let g++ call the
> linker for them, but when they call `ld' directly, they'll fail without the
> link.
>
> If we have two distinct links, they could get out of sync though; IMO the
> best solution would be for one to be a link to the other.
I disagree, because the libstdc++ library is dependent on the g++
compiler and ld doesn't know anything about this dependency. Perhaps
an C++ expert could comment ...
Reply to: