rename it libstdc++.so.1. Then you just have to modify your executable
so that it looks for libstdc++.so.1 instead of libstdc++.so.3
Why not just reinstall the problematic executables?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the
rename it libstdc++.so.1. Then you just have to modify your executable
so that it looks for libstdc++.so.1 instead of libstdc++.so.3
Why not just reinstall the problematic executables?
Yeap, we do that quite often in Linux 8)
Cheers
--
Amancio Hasty
[EMAIL PROTECTED]
To
On Fri, Jan 28, 2000 at 07:07:39PM -0500, Louis A. Mamakos wrote:
Is it possible to bump the revision of libstdc++ (and perhaps others) so
that existing programs can continue to function?
Nope. This is -CURRENT and this type of thing happens. And with a
RELEASE about to happen, I
On Fri, Jan 28, 2000 at 11:19:37PM -0500, Louis A. Mamakos wrote:
Well, OK, I can deal with this myself. I'm just concerned about the
folks who will eventually upgrade from 3.4 to 4.0, and have their
C++ programs stop working.
There will be the same problem WRT C++ when upgrading from 3.4
Louis A Mamakos writes:
I just put a new -current on my test machine, and watched a bunch of stuff
fall over and die due to the new C++ implementation.
Is it possible to bump the revision of libstdc++ (and perhaps others) so
that existing programs can continue to function? I fear I
On Fri, Jan 28, 2000 at 07:07:39PM -0500, Louis A. Mamakos wrote:
Is it possible to bump the revision of libstdc++ (and perhaps others) so
that existing programs can continue to function?
Nope. This is -CURRENT and this type of thing happens. And with a
RELEASE about to happen, I don't want
On Fri, Jan 28, 2000 at 07:07:39PM -0500, Louis A. Mamakos wrote:
Is it possible to bump the revision of libstdc++ (and perhaps others) so
that existing programs can continue to function?
Nope. This is -CURRENT and this type of thing happens. And with a
RELEASE about to happen, I don't
