On Thu, Feb 10, 2000 at 06:55:53PM -0500, Donn Miller wrote:
> Just curious as to what the advantages are of having libstdc++ separated
> from gcc.
How is libstdc++ separated from g++? I'm not really understanding what
you are trying to get across.
> From what I recall on www.gnu.org, they said g++ 2.95.2 will have
> libstdc++ integrated into gcc/g++ itself.
In to the distribution tarball and maintained by the same people, rather
than as a separated product -- certainly one does not put the contents of
a library tha all things need to link against inside the compiler so
only it gets to use the library.
> It seems to causing some problems on FreeBSD, like my aforementioned
> post on compiling kdesupport-current.
Can you remind us in what those are?
> (See my previous mail about libstdc++ and gcc that I made a while
> back.)
Would be easier to have included them hear -- I get many 100's of emails
daily and certainly cannot remember the details in all of them.
> I saw someone on here that had the same problem. He said that the errors
> went away when he forced static linking to libstdc++.a. (He moved
> /usr/lib/libstdc++.so.3 to a temp directory.)
I really don't know which email you are referring to -- but are you sure
you aren't having problems because you have a mix of old "thunks" C++
libs&binaries and new non-thunks C++ libs&binaries?
--
-- David ([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
