[comp.sys.dec] g++ on a Decstation 3100

dglo@ADS.COM (Dave Glowacki) (04/24/91)

I've been asked to bring up g++ on our Decstation 3100 and I seem
to be ALMOST there.  I've grabbed the gcc-osf-1.9.2.14 and the
osf version of g++-1.37.2 from foobar.colorado.edu and gotten them
to compile.  When I try to compile libg++, it gets through a bunch of
files, but fails in String.cc with:
as0: Internal: String.cc, line 1: scNil to scNil
as0: Internal: String.cc, line 1: scNil to scNil

It fails with the same sort of error in BitSet, BitString, Fix, Fix16
and Fix24.

I obviously don't have something installed correctly, because __DTOR_LIST__
and __CTOR_LIST__ are undefined when I try to compile a minimal c++
program.  gnu/lib contains:

-rwxr-xr-x  1 dglo     gnu        116968 Apr 23 15:35 gcc-collect*
-rwxr-xr-x  1 dglo     gnu       1393280 Apr 23 15:35 gcc-cc1plus*
drwxrwxr-x  4 dglo     gnu           512 Apr 23 14:59 gcc-include/
-rwxr-xr-x  1 dglo     gnu        162460 Apr 23 14:59 gcc-cpp*
lrwxrwxr-x  1 dglo     gnu            11 Apr 23 14:59 gcc-as@ -> gcc-mips-as
-rwxr-xr-x  1 dglo     gnu         86108 Apr 23 14:59 gcc-mips-as*
-rwxr-xr-x  1 dglo     gnu         91268 Apr 23 14:59 gcc-mips-tdump*
-rwxr-xr-x  1 dglo     gnu        119620 Apr 23 14:59 gcc-mips-tfile*
-rwxr-xr-x  1 dglo     gnu         58174 Apr 23 14:59 gcc-gnulib*
-rwxr-xr-x  1 dglo     gnu       1659428 Apr 23 14:59 gcc-cc1*

Could someone please give a poor Sun dweeb some pointers?
--
Dave Glowacki          dglo@ads.com          Advanced Decision Systems

cs4n+@andrew.cmu.edu (Charles Humphrey Silvers) (04/26/91)

I had this problem too.  The actually error is that g++ is producing
.extern lines for variables actually declared in the same file.  My
solution I found was to either produce the assemble, remove the
spurious .extern's and assemble it myself, or to re-order the source
lines to put the declarations of the variables ahead of the extern's
for them (or something like that, I know that re-ordering the code
solved the problem).

I wish the MIPS assembler would be more forgiving about things like
this, or at least produce a more informative error message.

-Chuck