🚀 go-pugleaf

Hello,
I'm in kind of a perverse situation, but I thought I'd try for help anyway.
I'm running GCC 2.1, which was compiled on a NeXT 2.1 system, on my Next 3.0  
(beta) system.  It appears to work pretty well.  I could not get GCC 2.2 to  
compile on my system, but that's another story.

I am trying to compile lib++2.2 (I couldn't find 2.1).  Are there any  
particular problems known to occur if you try to compile lib2.2 with a 2.1  
system?

For a number of files, I seem to get this 'DTOR_LIST' symbol defined, which  
results in:
pundit% g++ streambuf.C  
ld: streambuf.o symbol 137 (___DTOR_LIST__) has unknown n_type field (0x16)
collect: /bin/ld returned 1 exit status
This happens to any libraries that include this module as well.

The relevant files which have this odd symbol are:
   Rational.cc Regex.cc String.cc fmtq.cc ioob.cc  AND streambuf.C
Everything else is fine.

The only files which EXPLICITLY mention DTOR_LIST are init_main.c and other  
things which include 'dldefs.h'.  They are not compiled at all. Since dldefs.h  
is not part of the distribution, there is no way to compile them.  Is there any  
correlation?

Could someone explain to me what is going on?  Am I doing something horribly  
perverse that causes this?  Would using gcc 2.2.2 get rid of this?  Does  
anybody know exactly what DTOR_LIST is even there for?

Thanks in advance,

- Ernie P.

--
Ernest N. Prabhakar                  Caltech High Energy Physics
Member, League for Programming Freedom (league@prep.ai.mit.edu)
CaJUN President        NeXTMail:ernest@pundit.cithep.caltech.edu
"...and ourselves, your servants for Jesus sake." - II Cor 4:5b
#import <std/disclaimer.h>