ALERT: don't make 1.36.1 with SOS defined

Thread View: gnu.g++.bug

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by rfg Thu, 07 Dec 1989 19:46

#689

Author: rfg
Date: Thu, 07 Dec 1989 19:46

20 lines
1171 bytes

Based on past experience, I had been in the habit of always making g++
with both ESKIT and SOS defined (in the Makefile).

I have just learned that having SOS defined can be disasterous.  If you
have it defined, you will *not* be able to successfully compile libg++.

The problem becomes apparent immediately when you are compiling AllocQueue.cc
from libg++ (the first file in src/).

The problem comes from the initializer for the member "nodes" on line 28
of AllocQueue.cc.  This initializer includes a "new" expression.

Apparently, if SOS was defined whne you compiled cplus-init.c, then the
routine called build_new() in cplus-init.c returns a bogus value on or
about line 2521 in cplus-init.c.

All hell breaks loose after that.

// rfg

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads