From owner-freebsd-current Fri Apr 30 11:48:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7141F15A26 for ; Fri, 30 Apr 1999 11:48:33 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id LAA95813; Fri, 30 Apr 1999 11:48:29 -0700 (PDT) (envelope-from obrien) Message-ID: <19990430114829.B95710@nuxi.com> Date: Fri, 30 Apr 1999 11:48:29 -0700 From: "David O'Brien" To: John Polstra , sprice@hiwaay.net Cc: current@FreeBSD.ORG Subject: Re: (FWD) Re: Progs linked against libstdc++ dead... Reply-To: obrien@NUXI.com References: <199904300552.WAA14825@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199904300552.WAA14825@vashon.polstra.com>; from John Polstra on Thu, Apr 29, 1999 at 10:52:50PM -0700 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > These are good questions, and I don't know enough yet about the issues > surrounding vtable thunks to answer them. I haven't had time to really dig into this yet. Hopefully Saturday. I'm about to revert the change until I can see what the problem is and what the upgrade issues will be. EGCS 1.2 *should* be out in the July/Aug time frame. Of course I will try to upgrade us to it (well 1.2.1 which I figure will quickly follow). The EGCS maintainers are pushing to get vtable thunks working properly for 1.2. Since the Linux config files specify DEFALUT_VTABLE_THUNKS=1, no one has posted a bug report related to them, there is an option to turn them off, and this *is* -CURRENT. I may just leave them turned on by default. Opinions? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message