Date: Mon, 20 Oct 2003 16:49:21 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Robert Collins <robertc@squid-cache.org> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: gnu/58099: g++ -fhuge-objects on ix86 coredumps upon use of std::ostringstream Message-ID: <20031020234921.GA61811@rot13.obsecurity.org> In-Reply-To: <1066693295.6189.125.camel@localhost> References: <200310170621.h9H6LmGr068865@freefall.freebsd.org> <1066644745.955.10.camel@localhost> <20031020184333.GA60464@rot13.obsecurity.org> <1066688170.6183.111.camel@localhost> <20031020233619.GB61627@rot13.obsecurity.org> <1066693295.6189.125.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
--6TrnltStXW4iwmi0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 21, 2003 at 09:41:35AM +1000, Robert Collins wrote: > On Tue, 2003-10-21 at 09:36, Kris Kennaway wrote: > > On Tue, Oct 21, 2003 at 08:16:10AM +1000, Robert Collins wrote: > > > On Tue, 2003-10-21 at 04:43, Kris Kennaway wrote: > > >=20 > > > > Which binary packages, the package for the gcc ports? Nothing spec= ial > > > > is done for package builds, beyond what is in the port. Can you be > > > > specific about why you think this is a port error? > > >=20 > > > Because every c++ library in the distribution needs to be built with = all > > > permutations of ABI breaking options. The libstdc++ library is just t= he > > > first one. If you don't want to face doing this, then having > > > -fhuge-objects always on is a reasonable workaround. > >=20 > > Won't this break compatibility with all existing users of C++ > > packages? That would be a deal-breaker. >=20 > The workaround would. Doing the 'right thing', building a libstdc++ with > -fhuge-objects, and editing the spec file to use it IFF -fhuge-objects > was passed to g++ won't break anything. Talk to kan@FreeBSD.org (maintainer of the base system gcc code). I'm not sure of your chances of getting two libstd++'s built - the likely answer is that if you want to compile ports with ABI-incompatible gcc options, you should also compile the base system (hence libstd++) with the same5D options. Kris --6TrnltStXW4iwmi0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/lHSAWry0BWjoQKURAp/jAJ0VwM6oWeLu3vcHLsw9RvfiDhydhQCfTLkq MTYAu0VlKvxl8Lp7hPZxIM0= =tlDl -----END PGP SIGNATURE----- --6TrnltStXW4iwmi0--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031020234921.GA61811>