gnu/58099: g++ -fhuge-objects on ix86 coredumps upon use of std::ostringstream

[Kris Kennaway]

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:
> > > 
> > > > Which binary packages, the package for the gcc ports?  Nothing special
> > > > is done for package builds, beyond what is in the port.  Can you be
> > > > specific about why you think this is a port error?
> > > 
> > > Because every c++ library in the distribution needs to be built with all
> > > permutations of ABI breaking options. The libstdc++ library is just the
> > > first one. If you don't want to face doing this, then having
> > > -fhuge-objects always on is a reasonable workaround.
> > 
> > Won't this break compatibility with all existing users of C++
> > packages?  That would be a deal-breaker.
> 
> 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 at 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-bugs/attachments/20031020/f8c1c5a1/attachment.bin