Date: Sat, 29 Jan 2000 05:46:43 -0800 From: "David O'Brien" <obrien@FreeBSD.ORG> To: "Louis A. Mamakos" <louie@TransSys.COM> Cc: current@FreeBSD.ORG Subject: Re: new C++ compiler changes Message-ID: <20000129054643.A66201@dragon.nuxi.com> In-Reply-To: <200001290419.XAA06638@whizzo.transsys.com>; from louie@TransSys.COM on Fri, Jan 28, 2000 at 11:19:37PM -0500 References: <200001290007.TAA05379@whizzo.transsys.com> <20000128173700.A24289@dragon.nuxi.com> <200001290419.XAA06638@whizzo.transsys.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 to 4.0 either way. Both "g++-2.95.2 -fno-vtable-thunks" and "g++-2.95.2 -fvtable-thunks" are incompatible C++ platforms from G++ 2.7.x. People wishing to use C++ programs compiled on FreeBSD 3.x need to install the ``compat3x'' distribution to get the libstdc++.so.? compatibility library. For ports those same people will have to keep their 3.x compiled C++ libs (in /usr/local/lib & /usr/X11R6/lib) around how ever they like. Again, this requirement would be the same with or w/o the C++ ABI change I just made. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000129054643.A66201>