This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: string class (almost there!)
- To: Jason Merrill <jason at cygnus dot com>
- Subject: Re: string class (almost there!)
- From: Mark Mitchell <mmitchell at usa dot net>
- Date: Sun, 7 Dec 1997 20:32:57 GMT
- Cc: jspeter at roanoke dot infi dot net (Jim Peterson), egcs-bugs at cygnus dot com
- References: <199712071820.NAA25146.cygnus.egcs.bugs@twinkle.bevc.blacksburg.va.us><u9pvn865vi.fsf@yorick.cygnus.com>
- Reply-To: mmitchell at usa dot net
>>>>> "Jason" == Jason Merrill <jason@cygnus.com> writes:
>>>>> Jim Peterson <jspeter@roanoke.infi.net> writes:
>> I think only the first question really pertains to this mailing
>> list. The remaining questions really just demonstrate the
>> borders of my ignorance in this area. I would truly appreciate
>> anyone taking the effort to help me push back these borders
>> (and, for that matter, also with the issue of why there's a
>> libstdc++.so.27.2.8 _and_ a libstdc++.so.2.7.2.8 on my system,
>> what the difference is, and which, if either, I could safely
>> remove).
Jason> No libstdc++.so.2.8.0? You should remove both of them.
Jason> You're probably getting one of those, which would be why
Jason> you're having problems.
Not so fast! :-) Those libstdc++'s may well be provided by the
system, and there may well be binaries linked against them. For
example, on my RedHat 5.0 system, I have:
/usr/i486-linux-libc5/lib/libstdc++.so.27.1.4
and
/usr/lib/libstdc++.so.2.7.2.8
Both of these came with the distribution, and there are some
executables that require them.
Jason> Jason
--
Mark Mitchell mmitchell@usa.net
Stanford University http://www.stanford.edu