Date: Fri, 6 Sep 2002 09:58:54 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Akinori MUSHA <knu@iDaemons.org> Cc: Alexander Kabaev <kan@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/gnu/lib/libstdc++ Makefile Message-ID: <20020906165854.GA72608@xor.obsecurity.org> In-Reply-To: <86k7lz2hkp.wl@archon.local.idaemons.org> References: <200209012121.g81LLvjg032412@freefall.freebsd.org> <86k7lz2hkp.wl@archon.local.idaemons.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Sat, Sep 07, 2002 at 01:44:54AM +0900, Akinori MUSHA wrote: > At Sun, 1 Sep 2002 14:21:57 -0700 (PDT), > Alexander Kabaev wrote: > > kan 2002/09/01 14:21:57 PDT > > > > Modified files: > > gnu/lib/libstdc++ Makefile > > Log: > > Connect new files added with GCC 3.2.1 import to the build. > > > > Approved by: obrien > > Now that ABI compatibility has been lost, shouldn't SHLIB_MAJOR be > bumped? We don't worry about breaking ABI compat in -current (it's happened before in the development cycle). SHLIB_MAJOR is only bumped when we break compat with -STABLE. > Are compat4x/3x/22 still supposed to work for C++ programs? For 4.x/3.x/2.2 C++ programs, yes. Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9eN7OWry0BWjoQKURApuhAKDJmY02QvNMNmeaM5vMXa20xMOoPQCg14lB QU63JLW5UKghTnf2KxmQl3g= =wOXR -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020906165854.GA72608>