Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 29 Apr 1999 22:52:50 -0700 (PDT)
From:      John Polstra <jdp@polstra.com>
To:        sprice@hiwaay.net
Cc:        current@freebsd.org
Subject:   Re: (FWD) Re: Progs linked against libstdc++ dead...
Message-ID:  <199904300552.WAA14825@vashon.polstra.com>
In-Reply-To: <Pine.OSF.4.10.9904291305480.2845-100000@fly.HiWAAY.net>

next in thread | previous in thread | raw e-mail | index | archive | help
In article <Pine.OSF.4.10.9904291305480.2845-100000@fly.HiWAAY.net>,
Steve Price  <sprice@hiwaay.net> wrote:

> Fair enough, but the problem that really concerns me is that
> all the C++ libraries (and the programs that use them) will have
> to be recompiled when we make the switch.  Is there a programatic
> way to tell which vtable implementation a library was compiled
> with?  The compile-time error message doesn't count.  Turning
> the new vtable implementation on at any time now or in the future
> is going to cause confusion.  I guess the real question is will
> turning it on by default now make for less problems than waiting
> a month or two and then flipping the switch?

These are good questions, and I don't know enough yet about the issues
surrounding vtable thunks to answer them.  We'll of course try to
avoid the need to recompile libraries, but if that turns out to be
impossible ... well, this is -current, after all. :-}

John
-- 
  John Polstra                                               jdp@polstra.com
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "Self-interest is the aphrodisiac of belief."           -- James V. DeLong


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?199904300552.WAA14825>